I use DBReplicatior 2.2.4 - Postgresql 8.2
I have succesfully created publication and subscription and data was send corectly, but when connection between publisher and subscriber was crashed - replication not working (not starting corectly)
I have an error :
Problem in synchronizing data due to -- 'Z-a pozycja w ResultSet, mo¬e m
usisz wywo-aŠ next.'.
at org.postgresql.jdbc2.AbstractJdbc2ResultSet.checkResultSet(AbstractJd
bc2ResultSet.java:2575)
at org.postgresql.jdbc2.AbstractJdbc2ResultSet.getObject(AbstractJdbc2Re
sultSet.java:2414)
at org.postgresql.jdbc2.AbstractJdbc2ResultSet.getObject(AbstractJdbc2Re
sultSet.java:2438)
at org.dbreplicator.replication.xml.SyncXMLCreator.makeUpdateElement(Syn
cXMLCreator.java:576)
at org.dbreplicator.replication.xml.SyncXMLCreator.createXMLFile(SyncXML
Creator.java:169)
at org.dbreplicator.replication.Publication.createXMLForClient(Publicati
on.java:817)
at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
66)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
.java:707)
at java.lang.Thread.run(Thread.java:595)
How to fix replication after connection break ?
Thanks for your help
Tomek
If I read this correctly...
you have two problems. The first is related to the resultset not being positioned properly, and the second is how to restart the process when the connection breaks?
The first is most likely related to the jdbc jar file you're using. Make sure it's the 'postgresql-jdbc-8.2' and not the 'pg80b1.308' or any designed for an earlier release of postgres.
For the second, the linux subscriber daemon checks the tcp socket and reconnects automatically when a connection with the publisher is broken, but if you're running the gui, you've got no such luck. You'll have to restart manually.
Hope that helps.