activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <de...@nighttale.net>
Subject Re: testing WebSocket + STOMP support, getting occasional "No transportListener available..." errors
Date Fri, 25 Jun 2010 07:44:07 GMT
Hi Steve,

WebSocket support is pretty new. Thanks for testing it, can you post your JS
code so we can try reproduce the problem you're seeing?

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Thu, Jun 24, 2010 at 11:25 PM, Steve Kehlet <stevek@mirthcorp.com> wrote:

>
> 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://0.0.0.0:61614"/>
>            <transportConnector name="stomp"
> uri="stomp://0.0.0.0:61612?transport.closeAsync=false"/>
>            <transportConnector name="stomp+nio"
> uri="stomp+nio://0.0.0.0:61613?transport.closeAsync=false"/>
>
> Basically just following the directions from:
> http://www.nighttale.net/activemq/activemq-54-stomp-over-web-sockets.html,
> and using the JS lib from http://jmesnil.net/stomp-websocket/doc/ , 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
> response.
>
> 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
> increased?
>
> Thanks very much :-)
>
>
> --
> View this message in context:
> http://old.nabble.com/testing-WebSocket-%2B-STOMP-support%2C-getting-occasional-%22No-transportListener-available...%22-errors-tp28986861p28986861.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message