Re: ActiveMQ High number of threads

Thanks for your help artnaseef. I'll be waiting for this issue to be fixed. This is urgent for my project. Kind Regards, Nelson -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-High-number-of-threads-tp4693185p4694087.html Sent from the ActiveMQ - User mailing

JMS to JMS bridge connection

Hi everyone, I'm using a JMS to JMS bridge consuming from queueA and dispatching the messages to queue B (connection to WebLogic Service). I was having problems to make the connection to the WebLogic, but there was no output in the logs that it fails to connect. Only when I changed the logs to

Re: ActiveMQ High number of threads

This issue happens when my URI is: failover:(tcp://MACHINE_1:61616,tcp://MACHINE_2:61616)?randomize=falseuseExponentialBackOff=falseinitialReconnectDelay=1000startupMaxReconnectAttempts=40timeout=3 When I change to only 1 machine, the number of threads stays stable:

Re: ActiveMQ High number of threads

I've found another thread with similiar issue: https://issues.apache.org/jira/browse/AMQCPP-451 But it says that was fixed in version 3.6.x. Maybe this is another issue -- View this message in context:

ActiveMQ High number of threads

Hi everyone, I'm using failover connection to connect to the broker. When the broker stops, my application start to have more threads and keep growing... Only when the broker starts again the number of threads is reduced to its normal size. Can anyone help me with this issue? Kind regards,

Re: ActiveMQ High number of threads

Hi, I'm using ActiveMQ-CPP version 3.8.4. I'm using solaris OS in a platform that right now I can't make debug Full Stack trace: pstack_trace.7z http://activemq.2283324.n4.nabble.com/file/n4693194/pstack_trace.7z This is an application server that sends message sometimes to the broker.

maxReconnectAttempts parameter

Hi, I'm trying to use the maxReconnectAttempts parameter, but without success. I'm using a client connection with the following URI:

Re: maxReconnectAttempts parameter

Hi, If I use the URI: failover:(tcp://localhost:61616,tcp://localhost:61626)?randomize=false The thread blocks in sending message, and only unlocks when broker is started. Since I don't want to block the thread I can fix my problem using timeout parameter. I thought the reconnect attempt was

Re: maxReconnectAttempts parameter

Tks for your quick feedback. So what configuration should I use in the client so it tries to reconnect always once, even if the broker is down? Kind Regards, Nelson Cintra -- View this message in context:

Re: maxReconnectAttempts parameter

That parameter is what I'm using, but it ignores the parameter and never reconnects again. Kind Regards -- View this message in context: http://activemq.2283324.n4.nabble.com/maxReconnectAttempts-parameter-tp4690272p4690283.html Sent from the ActiveMQ - User mailing list archive at