Thanks so much for your response. Unfortunately we did check all those things
but no luck. Do you have any other suggestions what could be going on here?
We've made sure that all the versions of ruby and the gems are the same on
both servers.
Here is a bit of info from the data/activemq.log
When the server that works connects to ActiveMQ, I see the following in the
log (server name has been changed):
2014-01-17 08:46:03,599 | DEBUG | Stomp Inactivity Monitor read check
interval: 0ms, write check interval: 0ms |
org.apache.activemq.transport.stomp.StompInactivityMonitor | ActiveMQ
Transport: tcp:///192.168.106.2:34807@61613
2014-01-17 08:46:03,600 | DEBUG | Stomp Connect heartbeat conf RW[0,0] |
org.apache.activemq.transport.stomp.ProtocolConverter | ActiveMQ Transport:
tcp:///192.168.106.2:34807@61613
2014-01-17 08:46:03,601 | DEBUG | Setting up new connection id:
ID:servername.host-54089-1389976644747-2:7, address:
tcp://192.168.106.2:34807, info: ConnectionInfo {commandId = 0,
responseRequired = true, connectionId =
ID:servername.host-54089-1389976644747-2:7, clientId =
ID:servername.host-54089-1389976644747-2:7, clientIp = null, userName = ,
password = *****, brokerPath = null, brokerMasterConnector = false,
manageable = false, clientMaster = true, faultTolerant = false,
failoverReconnect = false} | org.apache.activemq.broker.TransportConnection
| ActiveMQ Transport: tcp:///192.168.106.2:34807@61613
and then I see a bunch of consumer messages like this:
2014-01-17 08:46:03,615 | DEBUG | localhost adding consumer:
ID:servername.host-54089-1389976644747-2:7:-1:1 for destination:
queue://myQueue_production |
org.apache.activemq.broker.region.AbstractRegion | ActiveMQ Transport:
tcp:///192.168.106.2:34807@61613
2014-01-17 08:46:03,618 | DEBUG | queue://myQueue_production add sub: 0,
dequeues: 0, dispatched: 0, inflight: {} |
org.apache.activemq.broker.region.Queue | ActiveMQ Transport:
tcp:///192.168.106.2:34807@61613
And, when I connect with the server that doesn't work I see the following
very similar connection string:
2014-01-17 08:42:34,407 | DEBUG | Stomp Inactivity Monitor read check
interval: 0ms, write check interval: 0ms |
org.apache.activemq.transport.stomp.StompInactivityMonitor | ActiveMQ
Transport: tcp:///192.168.107.195:50664@61613
2014-01-17 08:42:34,408 | DEBUG | Stomp Connect heartbeat conf RW[0,0] |
org.apache.activemq.transport.stomp.ProtocolConverter | ActiveMQ Transport:
tcp:///192.168.107.195:50664@61613
2014-01-17 08:42:34,408 | DEBUG | Setting up new connection id:
ID:servername.host-54089-1389976644747-2:6, address:
tcp://192.168.107.195:50664, info: ConnectionInfo {commandId = 0,
responseRequired = true, connectionId =
ID:servername.host-54089-1389976644747-2:6, clientId =
ID:servername.host-54089-1389976644747-2:6, clientIp = null, userName = ,
password = *****, brokerPath = null, brokerMasterConnector = false,
manageable = false, clientMaster = true, faultTolerant = false,
failoverReconnect = false} | org.apache.activemq.broker.TransportConnection
| ActiveMQ Transport: tcp:///192.168.107.195:50664@61613
But then that's it, there are no consumer messages. Similarily when I stop
the poller on the server that works I see a bunch of messages about the
consumers dropping from queues, and then the connection being killed.
However, when I stop the poller on the new server I don't see any
information in the log at all, just sits there and doesn't change.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Connection-being-made-but-not-registering-as-a-Consumer-of-any-queues-tp4676052p4676472.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
