registerReverse Connections failed after migration to a new server

We have been advised that everything will work as is on the new server by just copying the folders to the new server. Well we were able to get the IS running but when trying to register a reverse connection we got an error message as follows:

2006-10-20 15:03:17 EST java.lang.reflect.InvocationTargetException:com/wm/app/b2b/server/comm/ServerSocketLink
2006-10-20 15:04:31 EST com.wm.app.tn.err.EXMLException: <EXMLException>
   <ErrorCode>TRNSERV.000025.000190</ErrorCode>
   <Info>Error encountered invoking service wm.tn.security:getSecurity</Info>
   <OriginalException>
      <JavaClass>java.lang.ClassCastException</JavaClass>
      <Message>com.wm.data.BasicIDataCodable</Message>
      <StackTrace>java.lang.ClassCastException: com.wm.data.BasicIDataCodable
    at com.wm.app.tn.db.SecurityOps.getSecurityDataById(SecurityOps.java:196)
    at com.wm.app.tn.security.SecurityStore.getSecurityDataById(SecurityStore.java:329)
    at com.wm.app.tn.security.SecurityStore.getSecurityDataById(SecurityStore.java:305)
    at com.wm.app.tn.security.SecurityStore.getSignCertificateSet(SecurityStore.java:718)
    at com.wm.app.tn.security.SecurityStore.getSignCertificateSet(SecurityStore.java:678)
    at com.wm.app.tn.security.SignCertificateSet.<init>(SignCertificateSet.java:44)
    at wm.tn.security.getSecurity(security.java:384)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java(Compiled Code))
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java(Compiled Code))
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:480)
    at com.wm.app.b2b.server.HTTPInvokeHandler.process(HTTPInvokeHandler.java:168)
    at com.wm.app.b2b.server.HTTPDispatch.run(HTTPDispatch.java:457)
    at com.wm.util.pool.PooledThread.run(PooledThread.java(Compiled Code))
    at java.lang.Thread.run(Thread.java:513)
</StackTrace>
   </OriginalException>
   <Action></Action>
   <Level>0</Level>
</EXMLException>
    at com.wm.app.tn.err.EXMLException.fromResource(EXMLException.java:42)
    at wm.tn.security.getSecurity(security.java:458)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java(Compiled Code))
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java(Compiled Code))
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:480)
    at com.wm.app.b2b.server.HTTPInvokeHandler.process(HTTPInvokeHandler.java:168)
    at com.wm.app.b2b.server.HTTPDispatch.run(HTTPDispatch.java:457)
    at com.wm.util.pool.PooledThread.run(PooledThread.java(Compiled Code))
    at java.lang.Thread.run(Thread.java:513)

The RI server has not changed and we have made sure that the registered port is open to the new server. Can any guru out there shed some light on this please?

Thanks and regards

I have resolved the problem after extensive reverse engineering. At the end of the day the failure occured in invoking javax.crypto services and this lead me to suspect JVM issue. We were running JRE 1.3.1 in the new server (which was recommended for IS 4.6) but JRE 1.3.0 in the old server. I switched back to an older version of JVM and the problem disappeared.

My guess is that this wasn’t a JVM version issue, but a certificate installation issue? It might be worth pursuing.