Exception in thread "ActiveMQ Broker[localhost] Scheduler" java.lang.OutOfMemoryError: unable to create new native thread

Hi there, I'm using AMQ 5.10.0 with failover transport and I'm getting following exception:- Have following setting:- ACTIVEMQ_OPTS="-Xmx1G -Dorg.apache.activemq.UseDedicatedTaskRunner=false Exception in thread "ActiveMQ Broker[localhost] Scheduler" java.lang.OutOfMemoryError: unable to create n

Re: DEBUG | Transport Connection to: tcp://127.0.0.1:46804 failed: java.io.IOException: Java heap space | org.apache.activemq.broker.TransportConnection.Transport

ocess, encountered the following link:- http://working-with-activemq.blogspot.com/2012/05/performance-improvements.html which talks about performance fine tuning, I have applied changes suggested for vertical scaling and Other settings. -Sid On Tue, Dec 30, 2014 at 5:46 PM, tbain98 [via ActiveMQ]

Re: DEBUG | Transport Connection to: tcp://127.0.0.1:46804 failed: java.io.IOException: Java heap space | org.apache.activemq.broker.TransportConnection.Transport

Please see the following ticket for the issue details:- https://issues.apache.org/jira/browse/AMQ-4986 Thanks, Sid On Mon, Dec 29, 2014 at 7:32 PM, tbain98 [via ActiveMQ] < ml-node+s2283324n4689316...@n4.nabble.com> wrote: > It sure looks like your broker ran out of memory. So yo

Re: DEBUG | Transport Connection to: tcp://127.0.0.1:46804 failed: java.io.IOException: Java heap space | org.apache.activemq.broker.TransportConnection.Transport

Please see the following ticket for the issue details:- https://issues.apache.org/jira/browse/AMQ-4986 Thanks, Sid -- View this message in context: http://activemq.2283324.n4.nabble.com/DEBUG-Transport-Connection-to-tcp-127-0-0-1-46804-failed-java-io-IOException-Java-heap-space-org-apat

DEBUG | Transport Connection to: tcp://127.0.0.1:46804 failed: java.io.IOException: Java heap space | org.apache.activemq.broker.TransportConnection.Transport

nitor WriteCheckTimer Thanks, Sid -- View this message in context: http://activemq.2283324.n4.nabble.com/DEBUG-Transport-Connection-to-tcp-127-0-0-1-46804-failed-java-io-IOException-Java-heap-space-org-apat-tp4689306.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Fixing following issue:- WARN | Transport Connection to: blockingQueue_1942843618 failed: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long

g" error on broker then what steps I need to take, because earlier I experienced that after facing above issue, the connectivity is lost among producer, consumer and broker. So what's recommended next step. Thanks, Sid -- View this message in context: http://activemq.2283324.n4.nab

ProducerFlowControl on production - using only one queue - no cluster configured

rpose. --- Thanks, Sid -- View this message in context: http://activemq.2283324.n4.nabble.com/ProducerFlowControl-on-production-using-onl

Fixing following issue:- WARN | Transport Connection to: blockingQueue_1942843618 failed: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long

616?wireFormat.maxInactivityDuration=0&keepAlive=true&wireFormat.maxFrameSize=104857600)?jms.blobTransferPolicy.defaultUploadUrl=http://127.0.0.1:8161/fileserver/&initialReconnectDelay=1&useExponentialBackOff=false&randomize=false Please let me know if this is good to go on live. Than