Cache Coordination issue [message #659547] |
Mon, 14 March 2011 10:35  |
Eclipse User |
|
|
|
Hey guys, I have a question about cache coordination with Glassfish 3.1
I setup a Cluster in GF3.1 and enabled CacheCoordination on it. To make sure things were really working I wrote some JMeter tests, and in a very controlled environment it is, but I keep getting these log on the Broker
[14/Mar/2011:15:12:44 CET] [B1065]: Accepting: guest@127.0.0.1:1038->jms:1030. Count: service=1 broker=1
[14/Mar/2011:15:12:53 CET] [B1065]: Accepting: guest@127.0.0.1:1045->jms:1030. Count: service=2 broker=2
[14/Mar/2011:15:12:53 CET] [B1065]: Accepting: guest@127.0.0.1:1047->jms:1030. Count: service=3 broker=3
[14/Mar/2011:15:17:11 CET] [B1065]: Accepting: guest@127.0.0.1:1841->jms:1030. Count: service=4 broker=4
[14/Mar/2011:15:17:11 CET] [B1065]: Accepting: guest@127.0.0.1:1847->jms:1030. Count: service=5 broker=5
[14/Mar/2011:15:17:11 CET] [B1065]: Accepting: guest@127.0.0.1:1852->jms:1030. Count: service=6 broker=6
[14/Mar/2011:15:17:11 CET] [B1065]: Accepting: guest@127.0.0.1:1859->jms:1030. Count: service=7 broker=7
[14/Mar/2011:15:17:11 CET] [B1065]: Accepting: guest@127.0.0.1:1861->jms:1030. Count: service=8 broker=8
[14/Mar/2011:15:17:11 CET] [B1065]: Accepting: guest@127.0.0.1:1863->jms:1030. Count: service=9 broker=9
[14/Mar/2011:15:17:11 CET] [B1065]: Accepting: guest@127.0.0.1:1865->jms:1030. Count: service=10 broker=10
[14/Mar/2011:15:17:11 CET] [B1065]: Accepting: guest@127.0.0.1:1867->jms:1030. Count: service=11 broker=11
[14/Mar/2011:15:17:44 CET] [B1066]: Closing: guest@127.0.0.1:1047->jms:1030 because "[B0059]: Client closed the connection". Count: service=0 broker=9
[14/Mar/2011:15:17:44 CET] [B1066]: Closing: guest@127.0.0.1:1045->jms:1030 because "[B0059]: Client closed the connection". Count: service=0 broker=9
[14/Mar/2011:15:22:44 CET] [B1066]: Closing: guest@127.0.0.1:1865->jms:1030 because "[B0059]: Client closed the connection". Count: service=0 broker=8
[14/Mar/2011:15:22:44 CET] [B1066]: Closing: guest@127.0.0.1:1863->jms:1030 because "[B0059]: Client closed the connection". Count: service=0 broker=7
[14/Mar/2011:15:22:44 CET] [B1066]: Closing: guest@127.0.0.1:1867->jms:1030 because "[B0059]: Client closed the connection". Count: service=0 broker=6
[14/Mar/2011:15:27:44 CET] [B1066]: Closing: guest@127.0.0.1:1847->jms:1030 because "[B0059]: Client closed the connection". Count: service=0 broker=5
[14/Mar/2011:15:27:44 CET] [B1066]: Closing: guest@127.0.0.1:1852->jms:1030 because "[B0059]: Client closed the connection". Count: service=0 broker=4
[14/Mar/2011:15:27:44 CET] [B1066]: Closing: guest@127.0.0.1:1859->jms:1030 because "[B0059]: Client closed the connection". Count: service=0 broker=3
[14/Mar/2011:15:27:44 CET] [B1066]: Closing: guest@127.0.0.1:1861->jms:1030 because "[B0059]: Client closed the connection". Count: service=0 broker=2
Maybe it's ok, or maybe I should be posting this question on OpenMQ forums, but if anyone that have experienced this before can give me a light I will be very pleased.
|
|
|
|
|
|
|
Re: Cache Coordination issue [message #753654 is a reply to message #753539] |
Fri, 28 October 2011 04:20   |
Eclipse User |
|
|
|
Hi Rudi,
many thanks for the quick response. My persistence.xml was similar; plus I had also created a physical destination.
Anyway, using your settings, I still get a JNDI lookup error upon deployment:
$ asadmin deploy --target matchpoint-test --name BonusAppServer ~hank/BonusAppServer-1.2-SNAPSHOT.war
Exception [EclipseLink-22106] (Eclipse Persistence Services - 2.3.0.v20110604-r9504): org.eclipse.persistence.exceptions.RemoteCommandManagerException
Exception Description: Could not create external JMS connection with Topic CacheCoordinationTopic, Topic Factory CacheCoordinationFactory, and Context properties {dedicated.connection=true}
Internal Exception: Exception [EclipseLink-22103] (Eclipse Persistence Services - 2.3.0.v20110604-r9504): org.eclipse.persistence.exceptions.RemoteCommandManagerException
Exception Description: Could not look up remote connection under name CacheCoordinationFactory with URL null
Internal Exception: javax.naming.NamingException: Lookup failed for 'CacheCoordinationFactory' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory.url.pkgs=com.sun.enterprise.naming, dedicated.connection=true} [Root exception is javax.naming.NameNotFoundException: CacheCoordinationFactory not found]
Command deploy completed with warnings.
I can see Topic and ConnectionFactory under 'asadmin list-jms-resources', but not under 'asadmin list-jndi-resources' (not sure if that's an issue).
Thank you for your help!
Cheers,
Henning
|
|
|
|
Powered by
FUDForum. Page generated in 0.51995 seconds