Re: already connected from tcp://xx.xxx.x.xxx:59357

2014-02-14 Thread artnaseef
Is the client code setting a Client ID on the connection via setClientID()? http://docs.oracle.com/javaee/1.4/api/javax/jms/Connection.html#setClientID(java.lang.String) If so, then only one connection with a specific client ID can connect to the broker/network-of-brokers at any one time. Given

Re: already connected from tcp://xx.xxx.x.xxx:59357

2014-02-14 Thread Rodrigo Ramos
Im using an only one cosumer for all queues. Regards El feb 14, 2014 6:13 PM, "Noel OConnor" escribió: > Are you using topics and reusing the same client id for multiple producers. > Its just a guess but check just in case. > > > On Sat, Feb 15, 2014 at 9:18 AM, Rodrigo Ramos > wrote: > > > Hi

Re: already connected from tcp://xx.xxx.x.xxx:59357

2014-02-14 Thread Noel OConnor
Are you using topics and reusing the same client id for multiple producers. Its just a guess but check just in case. On Sat, Feb 15, 2014 at 9:18 AM, Rodrigo Ramos wrote: > Hi > > > Im testing a web application that is connected with ActiveMQ as producer. > IM getting below error with load: > >

already connected from tcp://xx.xxx.x.xxx:59357

2014-02-14 Thread Rodrigo Ramos
Hi Im testing a web application that is connected with ActiveMQ as producer. IM getting below error with load: [#|2014-02-14T15:59:26.840-0600|WARNING|glassfish3.1.2|javax.enterprise.system.core.transaction.com.sun.jts.jta|_ThreadID=801;_ThreadName=Thread-2;|JTS5041: The resource manager is doin