[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [eclipselink-users] RMI Cache Coordination Exceptions
|
Title: RE: [eclipselink-users] RMI Cache Coordination Exceptions
Hi Gordon,
So when you say 'system' you mean application server, correct?
Is a reccomended path then, if I have say 5 tomcat servers running my application, on 5 different machines, I should have them all point to the same location (eg tomcat 1)? Or do you reccomend I would have a sixth machine that would act as a central broadcast point? Would that mean that all of my applications would be requesting objects off of the sixth machine, or that would just serve as the launching point for RMI notifications (eg I have chosen cache coordination - invalidate) that all servers would subscribe to?
Thanks!
Tony
From: eclipselink-users-bounces@xxxxxxxxxxx on behalf of Gordon Yorke
Sent: Wed 12/5/2007 4:45 PM
To: EclipseLink User Discussions
Subject: RE: [eclipselink-users] RMI Cache Coordination Exceptions
Hello Tony,
The URL configured for cache coordination should point to the location where this system should register its listener using IP or resolvable system name _not_ localhost. 'localhost' is seen in a lot of examples but only works when all running systems are on the same hardware.
With RMI Cache Coordination the topology you choose for the registries is up to you but generally the recommended approach is to start a registry on each system. Having to specify the IP of the local machine in each system's config can be painful so EclipseLink offers a special URL format that will cause EclipseLink to autodetect the local IP of this system. Change 'cm.setUrl("rmi://localhost:8881");' to 'cm.setUrl("rmi://$HOST:8881");'
Alternatively you could have a single registry hosted on a single system and have all of your systems point to that registry requiring you to specify only one URL.
The second thing to know is that there has been a bug fix in the cache coordination code. During the migration the RMI stubs that had existed in the original EclipseLink code were renamed but not regenerated. These stubs were incorrect and would result in an Unmarshal exception. That has now been fixed and the changes will be in Milestone 2 due out tonight.
Upgrading to the new milestone download and changing the url to use the $HOST token should resolve you coordination problems.
--Gordon
-----Original Message-----
From: eclipselink-users-bounces@xxxxxxxxxxx
[mailto:eclipselink-users-bounces@xxxxxxxxxxx]On Behalf Of Vespa,
Anthony J
Sent: Wednesday, December 05, 2007 3:36 PM
To: EclipseLink User Discussions
Subject: RE: [eclipselink-users] RMI Cache Coordination Exceptions
Just wondering if there was any more info on this?
-----Original Message-----
From: eclipselink-users-bounces@xxxxxxxxxxx
[mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of Doug Clarke
Sent: Sunday, December 02, 2007 3:32 PM
To: EclipseLink User Discussions
Subject: RE: [eclipselink-users] RMI Cache Coordination Exceptions
Tony,
I believe I am now seeing the same or at least very similar exception in
my test case. I will walk through it with the developers on Monday and
see if we can get to the bottom of things. Hopefully this is just a
minor issue that we can quickly patch for you.
Doug
-----Original Message-----
From: eclipselink-users-bounces@xxxxxxxxxxx
[mailto:eclipselink-users-bounces@xxxxxxxxxxx]On Behalf Of Vespa,
Anthony J
Sent: Friday, November 30, 2007 12:43 PM
To: EclipseLink User Discussions
Subject: [eclipselink-users] RMI Cache Coordination Exceptions
I'm still getting exceptions trying to get RMI coordinated caching to
work. It makes the DB call ok but about 4-5 seconds after it blows up
as below:
[EPS Warning]: 2007.11.30
11:02:16.972--ServerSession(31985466)--Thread(Thread[Thread-8,5,main])--
Local Exception Stack:
Exception [EclipseLink-22102] (Eclipse Persistence Services - 1.0M1
(Build 20071105)):
org.eclipse.persistence.exceptions.RemoteCommandManagerException
Exception Description: Could not post connection in local naming service
under name rmi://localhost:8881/13598682
Internal Exception: java.rmi.ConnectIOException: error during JRMP
connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
at
org.eclipse.persistence.exceptions.RemoteCommandManagerException.errorBi
ndingConnection(RemoteCommandManagerException.java:84)
at
org.eclipse.persistence.sessions.coordination.rmi.RMITransportManager.cr
eateLocalConnectionInRegistry(RMITransportManager.java:157)
at
org.eclipse.persistence.sessions.coordination.rmi.RMITransportManager.cr
eateLocalConnection(RMITransportManager.java:110)
at
org.eclipse.persistence.sessions.coordination.DiscoveryManager.run(Disco
veryManager.java:194)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.rmi.ConnectIOException: error during JRMP connection
establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:273)
at
sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
at sun.rmi.registry.RegistryImpl_Stub.rebind(Unknown Source)
at java.rmi.Naming.rebind(Naming.java:160)
at
org.eclipse.persistence.sessions.coordination.rmi.RMITransportManager.cr
eateLocalConnectionInRegistry(RMITransportManager.java:154)
... 3 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at
java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at
java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at java.io.DataInputStream.readByte(DataInputStream.java:241)
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:215)
... 8 more
Exception in thread "Thread-8" Local Exception Stack:
Exception [EclipseLink-22102] (Eclipse Persistence Services - 1.0M1
(Build 20071105)):
org.eclipse.persistence.exceptions.RemoteCommandManagerException
Exception Description: Could not post connection in local naming service
under name rmi://localhost:8881/13598682
Internal Exception: java.rmi.ConnectIOException: error during JRMP
connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
at
org.eclipse.persistence.exceptions.RemoteCommandManagerException.errorBi
ndingConnection(RemoteCommandManagerException.java:84)
at
org.eclipse.persistence.sessions.coordination.rmi.RMITransportManager.cr
eateLocalConnectionInRegistry(RMITransportManager.java:157)
at
org.eclipse.persistence.sessions.coordination.rmi.RMITransportManager.cr
eateLocalConnection(RMITransportManager.java:110)
at
org.eclipse.persistence.sessions.coordination.DiscoveryManager.run(Disco
veryManager.java:194)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.rmi.ConnectIOException: error during JRMP connection
establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:273)
at
sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
at sun.rmi.registry.RegistryImpl_Stub.rebind(Unknown Source)
at java.rmi.Naming.rebind(Naming.java:160)
at
org.eclipse.persistence.sessions.coordination.rmi.RMITransportManager.cr
eateLocalConnectionInRegistry(RMITransportManager.java:154)
... 3 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at
java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at
java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at java.io.DataInputStream.readByte(DataInputStream.java:241)
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:215)
... 8 more
[EPS Warning]: 2007.11.30
11:03:17.594--ServerSession(31985466)--Thread(Thread[Finalizer,8,system]
)--Local Exception Stack:
Exception [EclipseLink-22107] (Eclipse Persistence Services - 1.0M1
(Build 20071105)):
org.eclipse.persistence.exceptions.RemoteCommandManagerException
Exception Description: Could not remove local connection in local naming
service under name rmi://localhost:8881/13598682
Internal Exception: java.rmi.ConnectIOException: error during JRMP
connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
at
org.eclipse.persistence.exceptions.RemoteCommandManagerException.errorUn
bindingLocalConnection(RemoteCommandManagerException.java:137)
at
org.eclipse.persistence.sessions.coordination.rmi.RMITransportManager.re
moveLocalConnection(RMITransportManager.java:234)
at
org.eclipse.persistence.sessions.coordination.TransportManager.discardCo
nnections(TransportManager.java:432)
at
org.eclipse.persistence.sessions.coordination.RemoteCommandManager.shutd
own(RemoteCommandManager.java:179)
at
org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.logout(Dat
abaseSessionImpl.java:718)
at
org.eclipse.persistence.sessions.server.ServerSession.logout(ServerSessi
on.java:625)
at
org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.removeSessio
nFromGlobalSessionManager(EntityManagerSetupImpl.java:138)
at
org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.undeploy(Ent
ityManagerSetupImpl.java:1286)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.close(Enti
tyManagerFactoryImpl.java:83)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.finalize(E
ntityManagerFactoryImpl.java:137)
at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
at
java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)
Caused by: java.rmi.ConnectIOException: error during JRMP connection
establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:273)
at
sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
at sun.rmi.registry.RegistryImpl_Stub.unbind(Unknown Source)
at java.rmi.Naming.unbind(Naming.java:135)
at
org.eclipse.persistence.sessions.coordination.rmi.RMITransportManager.re
moveLocalConnection(RMITransportManager.java:226)
... 12 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at
java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at
java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at java.io.DataInputStream.readByte(DataInputStream.java:241)
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:215)
... 17 more
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users