Per cronjob a scheduled task "pgprepctl scan 240" is periodically run on each cluster member to check for replication differences on remote cluster members.
This replication task causes a Java Exception on the remote server.
An example debug log taken from the remote cluster member on which the Java Exception "java.lang.Integer cannot be cast to java.lang.String" occurs.
2013/06/24 13:39:48 +01:00 DEBUG pgp/cluster[2002]: LinkHandler.Receiver: received SCAN_REQUEST, length 37
2013/06/24 13:39:48 +01:00 DEBUG pgp/cluster[2002]: Internal error
EXCEPTION STACK TRACE:
java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.String
at com.pgp.ovid.rep.daemon.TableQuerier.obj2stream(TableQuerier.java:828)
at com.pgp.ovid.rep.daemon.TableQuerier.writeScanKey(TableQuerier.java:479)
at com.pgp.ovid.rep.daemon.TableQuerier.writeScan(TableQuerier.java:442)
at com.pgp.ovid.rep.daemon.ChangeCache.writeScanResponse(ChangeCache.java:753)
at com.pgp.ovid.rep.daemon.RepWorker.handleScanRequest(RepWorker.java:823)
at com.pgp.ovid.rep.daemon.RepWorker.run(RepWorker.java:356)
2013/06/24 13:39:48 +01:00 DEBUG pgp/cluster[2002]: [LINK] stream lost Socket[addr=/127.0.0.1,port=45880,localport=4433]
TLS connection errors on the cluster member originating the scan might be triggered by the connection being unexpectedly shut down on the remote server.
Defect in replication code.
Upgrade to Symantec Encryption Server version 3.3.0 MP2.
The release notes mention:
"Resolved an issue with Symantec Encryption Management Server so that the nightly SCAN operation no longer generates exception stack traces when updating or inserting due to a database foreign key constraint violation. All user data are now replicated to the other cluster members. [3198384]"
Applies To
Symantec Encryption Server 3.0 MP5, 3.3.0 or 3.3.0 MP1