admin@glassfish.java.net

JMS - connection refused on 7676 when domain uses 6767

From: Márcio Geovani Jasinski <marciogj_at_gmail.com>
Date: Thu, 2 Jun 2011 18:25:01 -0300

Hi everyone,

We have an application (J2EE) which is JMS based. In order to isolate it
from other applications – we always set up a new domain with following port
configuration:

ADMIN_PORT=4949

JMX_PORT=6868

JMS_PORT=6767

HTTP_PORT=8585

HTTPS_PORT=1818

ORB_PORT=7300

ORBS_PORT=8302

ORBM_PORT=9302

It turns out that sometimes I see JMS component trying to connect on JMS
default port (7676) instead of configured one (6767):

[#|2011-05-23T11:48:29.917-0300|INFO|sun-appserver2.1|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;|MQJMSRA_RA1101:
SJSMQ JMS Resource Adapter starting...|#]
[#|2011-05-23T11:48:29.964-0300|INFO|sun-appserver2.1|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;|MQJMSRA_LB1101:
Looking for Broker Running at:localhost:6767|#]

[#|2011-05-23T11:49:44.529-0300|WARNING|sun-appserver2.1|javax.jms|_ThreadID=23;_ThreadName=p:
thread-pool-1; w:
4;_RequestID=138cb0fe-ad3f-42c1-a11f-88d16c111043;|[C4003]: Error occurred
on connection creation [localhost:7676]. - cause: java.net.ConnectException:
Connection refused: connect|#]
[#|2011-05-23T11:49:50.576-0300|WARNING|sun-appserver2.1|javax.jms|_ThreadID=23;_ThreadName=p:
thread-pool-1; w:
4;_RequestID=138cb0fe-ad3f-42c1-a11f-88d16c111043;|[C4003]: Error occurred
on connection creation [localhost:7676]. - cause: java.net.ConnectException:
Connection refused: connect|#]
[#|2011-05-23T11:49:56.482-0300|WARNING|sun-appserver2.1|javax.jms|_ThreadID=23;_ThreadName=p:
thread-pool-1; w:
4;_RequestID=138cb0fe-ad3f-42c1-a11f-88d16c111043;|[C4003]: Error occurred
on connection creation [localhost:7676]. - cause: java.net.ConnectException:
Connection refused: connect|#]

Sometimes there are many messages like that in a row (Log file is attached).

I´m wondering if this something internal from Glassfish or something that
application does – like a producer which is being initialized with wrong
attibuttes.
Even within this error appearing our application communicate with other
part.

Anyone already had similar situation?
Thanks in advance,
-- 
Márcio Geovani Jasinski
Blumenau, Santa Catarina
Fone: +55 47 9653 4899