| [eclipselink-users] Help requested to solve RemoteCommandManagerException (due to : javax.naming.NameNotFoundException trying to resolve remote connection) |
|
I am facing issues with enabling cache coordination when deploying the application in a WebLogic cluster of 2 servers.
I see following exception in the logs of the server that starts up first, but I see this only when second server is coming up.
After both servers are up, I can see that the object 31135874-1f3e-4782-8970-111fd73e292f
is resolved in the failing server’s JNDI tree as “weblogic.rmi.internal.LeasedRemoteRef - hostID:
'486168901753773084S:anvay-local1.srv.com:[8103,8103,-1,-1,-1,-1,-1]:ncp8_cluster:srv1', oid: '290', channel: 'null'” I almost feel that that RemoteCommandManager is trying to initialize by trying to resolve the remote connection too soon. The remote server with ID 486168901753773084S has not been even registered and shown to be registered just after the
error below (highlighted). ####<Sep 1, 2015 1:48:22 PM PDT> <Warning> <EclipseLink> <LT-AKOLHATKAR> <srv2> <pool-8-thread-1> <<anonymous>> <> <> <1441140502297> <BEA-2005000> <2015-09-01 13:48:22.281--ServerSession(12739890)--Exception [EclipseLink-22103] (Eclipse
Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.RemoteCommandManagerException Exception Description: Could not look up remote connection
under name 31135874-1f3e-4782-8970-111fd73e292f with URL null Internal Exception: javax.naming.NameNotFoundException: Unable to resolve
'31135874-1f3e-4782-8970-111fd73e292f'. Resolved ''; remaining name '31135874-1f3e-4782-8970-111fd73e292f'>
####<Sep 1, 2015 1:48:24 PM PDT> <Info> <J2EE> <LT-AKOLHATKAR> <srv2> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1441140504138> <BEA-160151> <Registered library Extension-Name:
bea_wls_async_response (JAR).> ####<Sep 1, 2015 1:48:51 PM PDT> <Notice> <WebLogicServer> <LT-AKOLHATKAR> <srv2> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1441140531131> <BEA-000365> <Server state changed
to ADMIN.> ####<Sep 1, 2015 1:48:51 PM PDT> <Info> <Cluster> <LT-AKOLHATKAR> <srv2> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1441140531352> <BEA-000111> <Adding
srv1 with ID 486168901753773084S:anvay-local1.srv.com:[8103,8103,-1,-1,-1,-1,-1]:ncp8_cluster:srv1 to cluster: cluster1 view.>
####<Sep 1, 2015 1:48:51 PM PDT> <Info> <Cluster> <LT-AKOLHATKAR> <srv2> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1441140531367> <BEA-000128> <Updating 486168901753773084S:anvay-local1.srv.com:[8103,8103,-1,-1,-1,-1,-1]:ncp8_cluster:srv1
in the cluster.> ####<Sep 1, 2015 1:48:51 PM PDT> <Notice> <WebLogicServer> <LT-AKOLHATKAR> <srv2> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1441140531414> <BEA-000365> <Server state changed
to RESUMING.> ####<Sep 1, 2015 1:48:51 PM PDT> <Info> <Server> <LT-AKOLHATKAR> <srv2> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1441140531445> <BEA-002610> <Dynamic Listener Service initialized.> The persistence.xml has following line: <property name="eclipselink.cache.coordination.protocol" value="rmi"/> I also tried with <property name="eclipselink.cache.coordination.protocol" value="rmi-iiop"/> and tried to add following, but it didn’t work and gave the same result as above.
<property name="eclipselink.cache.coordination.remove-connection-on-error" value="true"/> <property name="eclipselink.cache.coordination.rmi.announcement-delay" value="2000"/>
<property name="eclipselink.cache.coordination.propagate-asynchronously" value="false"/> Is there any configuration in WebLogic console that I need to do, to make it work?
Any suggestion on troubleshooting is appreciated greatly! Regards, Anvay |