Ah ok great thanks. Possibly it's the thread per session setting rather than socket threads. I'll run some tests.
Thanks Sent from my iPhone On 15 Oct 2012, at 16:08, "dejanb [via ActiveMQ]" <[email protected]> wrote: > Hi Dan, > > when using WebSockets, connectivity is done through Jetty and we're > already using nio connector. So there must be something else creating > problems for you. > > Can you test a latest snapshot from > > https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/5.8-SNAPSHOT/ > > as there were some improvements in this area lately. > > Regards > -- > Dejan Bosanac > ---------------------- > Red Hat, Inc. > FuseSource is now part of Red Hat > [hidden email] > Twitter: @dejanb > Blog: http://sensatic.net > ActiveMQ in Action: http://www.manning.com/snyder/ > > > On Mon, Oct 15, 2012 at 3:19 PM, blackhurstd > <[hidden email]> wrote: > > > > > Hi, > > > > I have a requirement for a large number of websocket subscribers and I > > cannot find a way of enabling NIO over websockets. Is it possible? I can > > see > > its available for stomp but not websockets. > > > > I'm seeing thousands of threads and hitting OS limits quite easily. > > > > Thanks, > > > > Dan > > > > > > > > -- > > View this message in context: > > http://activemq.2283324.n4.nabble.com/Websocket-Stomp-NIO-tp4657800.html > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > If you reply to this email, your message will be added to the discussion > below: > http://activemq.2283324.n4.nabble.com/Websocket-Stomp-NIO-tp4657800p4657802.html > To unsubscribe from Websocket (Stomp) NIO, click here. > NAML -- View this message in context: http://activemq.2283324.n4.nabble.com/Websocket-Stomp-NIO-tp4657800p4657803.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
