activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Kehlet <>
Subject testing WebSocket + STOMP support, getting occasional "No transportListener available..." errors
Date Thu, 24 Jun 2010 21:25:19 GMT

Verified on a 5.4 snapshot from today, but first noticed on a snap from Jun
9th. I'm testing connecting Chrome directly to activemq over WebSockets, and
STOMP on top of that.  I modified activemq.xml with:

            <transportConnector name="websocket" uri="ws://"/>
            <transportConnector name="stomp"
            <transportConnector name="stomp+nio"

Basically just following the directions from: ,
and using the JS lib from , and
ideas from various blogs.

Occasionally I'm seeing this error in the activemq.log:

2010-06-24 13:43:11,133 | ERROR | No transportListener available to process
inbound command: ConnectionInfo {commandId = 0, responseRequired = true,
connectionId = ID:appliance-55869-1277408644809-3:153, clientId =
ID:appliance-55869-1277408644809-3:153, userName = guest, password = *****,
brokerPath = null, brokerMasterConnector = false, manageable = false,
clientMaster = true, faultTolerant = false} |
org.apache.activemq.transport.TransportSupport | qtp20195943-22

Doing tcpdumps, I see the JS STOMP library issuing a CONNECT, but unlike
other times when it does work, ActiveMQ doesn't respond with a CONNECTED

Is this simply a resource issue?  Sorry for being such a noob, but how do I
increase the number of websocket transportConnectors?  

Also I noticed from tcpdumps that the ActiveMQ side is closing the
connection after 200 seconds (not sure inactivity or total), how can this be

Thanks very much :-)

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message