| Re: [eclipselink-users] eclipselink-users Digest, Vol 97, Issue 1 |
|
Hi Anvay, I assume that you are deploying to There is a complete working example available in How To Configure Cache Coordination With RMI on WebLogic Server (Doc ID 1394706.1) https://support.oracle.com/epmos/faces/DocContentDisplay?id=1394706.1 I assume that you are deploying to a WebLogic 12.1.3 cluster because of the reported version of EclipseLInk. The RMI example uses the following persistence.xml <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="pu"> <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> <jta-data-source>jdbc/toplinkDS</jta-data-source> <properties> <property name="eclipselink.logging.timestamp" value="true" /> <property name="eclipselink.logging.thread" value="true" /> <property name="eclipselink.logging.session" value="true" /> <property name="eclipselink.logging.exceptions" value="true" /> <property name="eclipselink.target-server" value="WebLogic_10" /> <property name="eclipselink.logging.level" value="ALL" /> <property name="eclipselink.logging.logger" value="ServerLogger" /> <!-- The session customizer is required with EclipseLink < 2.2 only, e.g. WebLogic Server 10.3.0 - 10.3.5. --> <!-- <property name="eclipselink.session.customizer" value="oracle.support.model.eclipselink.RMISessionCustomizerWLS"/> --> <property name="eclipselink.cache.coordination.protocol" value="rmi" /> <property name="eclipselink.cache.coordination.propagate-asynchronously" value="false" /> </properties> </persistence-unit> </persistence> Best regards, Reinhard Girstenbrei On 09/02/2015 06:00 PM,
eclipselink-users-request@xxxxxxxxxxx wrote:
Send eclipselink-users mailing list submissions to eclipselink-users@xxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit https://dev.eclipse.org/mailman/listinfo/eclipselink-users or, via email, send a message with subject or body 'help' to eclipselink-users-request@xxxxxxxxxxx You can reach the person managing the list at eclipselink-users-owner@xxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of eclipselink-users digest..." Today's Topics: 1. Help requested to solve RemoteCommandManagerException (due to : javax.naming.NameNotFoundException trying to resolve remote connection) (Anvay Kolhatkar) ---------------------------------------------------------------------- Message: 1 Date: Tue, 1 Sep 2015 21:11:06 +0000 From: Anvay Kolhatkar <anvay.kolhatkar@xxxxxxxxxxxx> To: "eclipselink-users@xxxxxxxxxxx" <eclipselink-users@xxxxxxxxxxx> Subject: [eclipselink-users] Help requested to solve RemoteCommandManagerException (due to : javax.naming.NameNotFoundException trying to resolve remote connection) Message-ID: <BLUPR0701MB1602B65ED208FCA6C2F7DB6D946A0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset="us-ascii" 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 This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the material from any computer. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dev.eclipse.org/mailman/private/eclipselink-users/attachments/20150901/e4049fc3/attachment.html> ------------------------------ _______________________________________________ eclipselink-users mailing list eclipselink-users@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/eclipselink-users End of eclipselink-users Digest, Vol 97, Issue 1 ************************************************ --
 Reinhard Girstenbrei | Senior Principal Technical Support Engineer Phone: +49 89 1430 2318 | Fax: +49 89 1430 2318 | Mobile: +49 177 594 1318 | VOIP: +49 89 1430 2318 Oracle Support ORACLE Deutschland B.V. & Co. KG | Riesstr.25 | 80992 Munich ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Geschäftsführer: Jürgen Kunz Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher 
Oracle is committed to developing practices and
products that help protect the environment
|