users@glassfish.java.net

Re: Writing a JMS client for a Message Queue Broker Cluster ...

From: <forums_at_java.net>
Date: Mon, 24 Jun 2013 04:28:49 -0500 (CDT)

Hello David I have performed the steps you have mentioned: 1) "Cluster >
gfcluster > Instances": both instances "Running", with a green check mark. 2)
"Cluster > gfcluster > JMS Physical Destinations": ERROR -> "Unable to list
JMS Destinations. Please ensure that the Message Queue Brokers are running."
3) These are the newly added log messages after step 2: *Domain log:*
T09:32:41.371+0000|SEVERE|glassfish3.1.2|org.glassfish.admingui|_ThreadID=247;_ThreadName=Thread-2;|RestResponse.getResponse()
gives FAILURE. endpoint =
'https://localhost:4848/management/domain/clusters/cluster/gfcluster/list-jmsdest';
attrs = '{}'|#] *Instance 1 log:*
[#|2013-06-24T09:32:39.032+0000|INFO|glassfish3.1.2|javax.enterprise.resource.jms.com.sun.enterprise.connectors.jms.system|_ThreadID=46;_ThreadName=Thread-2;|JMS010:
ADDRESSLIST in setJmsServiceProvider:
mq://172.16.2.20:27676/,mq://172.16.2.21:27676/|#]
[#|2013-06-24T09:32:39.032+0000|INFO|glassfish3.1.2|javax.enterprise.resource.jms.com.sun.enterprise.connectors.jms.system|_ThreadID=46;_ThreadName=Thread-2;|JMS08:
JMS Service Connection URL is :
mq://172.16.2.20:27676/,mq://172.16.2.21:27676/|#]
[#|2013-06-24T09:32:39.132+0000|INFO|glassfish3.1.2|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=46;_ThreadName=Thread-2;|MQJMSRA_RA1101:
GlassFish MQ JMS Resource Adapter: Version: 4.5.2 Patch 1 (Build 3-d)
Compile: Thu Jun 7 10:46:15 PDT 2012|#]
[#|2013-06-24T09:32:39.138+0000|INFO|glassfish3.1.2|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=46;_ThreadName=Thread-2;|MQJMSRA_RA1101:
GlassFish MQ JMS Resource Adapter starting: broker is EMBEDDED, connection
mode is TCP|#]
[#|2013-06-24T09:32:40.437+0000|INFO|glassfish3.1.2|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=46;_ThreadName=Thread-2;|MQJMSRA_RA1101:
GlassFish MQ JMS Resource Adapter Started:EMBEDDED|#] *Instance 2 log:*
[#|2013-06-24T09:32:36.786+0000|INFO|glassfish3.1.2|javax.enterprise.resource.jms.com.sun.enterprise.connectors.jms.system|_ThreadID=46;_ThreadName=Thread-2;|JMS010:
ADDRESSLIST in setJmsServiceProvider:
mq://172.16.2.21:27676/,mq://172.16.2.20:27676/|#]
[#|2013-06-24T09:32:36.787+0000|INFO|glassfish3.1.2|javax.enterprise.resource.jms.com.sun.enterprise.connectors.jms.system|_ThreadID=46;_ThreadName=Thread-2;|JMS08:
JMS Service Connection URL is :
mq://172.16.2.21:27676/,mq://172.16.2.20:27676/|#]
[#|2013-06-24T09:32:36.926+0000|INFO|glassfish3.1.2|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=46;_ThreadName=Thread-2;|MQJMSRA_RA1101:
GlassFish MQ JMS Resource Adapter: Version: 4.5.2 Patch 1 (Build 3-d)
Compile: Thu Jun 7 10:46:15 PDT 2012|#]
[#|2013-06-24T09:32:36.926+0000|INFO|glassfish3.1.2|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=46;_ThreadName=Thread-2;|MQJMSRA_RA1101:
GlassFish MQ JMS Resource Adapter starting: broker is EMBEDDED, connection
mode is TCP|#]
[#|2013-06-24T09:32:38.849+0000|INFO|glassfish3.1.2|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=46;_ThreadName=Thread-2;|MQJMSRA_RA1101:
GlassFish MQ JMS Resource Adapter Started:EMBEDDED|#] I hope you can see
something in these messages that helps. Please remember: My entire setup
might well be in contradiction with how Jelastic meant to configure both
nodes (virtual machines). Maybe they cannot even exchange messages due to
some security restriction. BTW: This a suspicious message I see /before/step
2, after starting the cluster:
[#|2013-06-24T09:24:40.226+0000|WARNING|glassfish3.1.2|ShoalLogger|_ThreadID=22;_ThreadName=Thread-2;|GMS1063:
missed GroupStartupComplete message. Timed out group startup after 240
secs|#]

--
[Message sent by forum member 'kappert']
View Post: http://forums.java.net/node/897020