Thank you for the response. Well, it's just that the instance was up since from some time now. And not much significant processing was involved.
Earlier broker -Xmx was set to 1G, after facing the above issue I have increased to 2G. And this resolved the issue for now. During this process, 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] < ml-node+s2283324n4689334...@n4.nabble.com> wrote: > What makes you believe that your problem is the same as that bug, given > that you're using different options than what's described in the bug? > Either way, it should be easy to step through that code in a debugger and > confirm whether that problem really is what you're running into. > On Dec 30, 2014 1:38 AM, "Sid" <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4689334&i=0>> wrote: > > > 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] < > > [hidden email] <http:///user/SendEmail.jtp?type=node&node=4689334&i=1>> > wrote: > > > > > It sure looks like your broker ran out of memory. So you need to > > evaluate > > > whether your JVM is properly sized and give it more RAM if it's not. > If > > > you're positive your broker has more than enough RAM and you're still > > > hitting the problem, then it's possible that a bug in the ActiveMQ > code > > is > > > leaking memory (so you'll need to use a memory analyzer to figure out > > what > > > objects are being kept alive), but it's far more likely that either > you > > > just need a larger JVM heap or you're doing something that results in > > > memory being used unnecessarily (for example, connecting a durable > > > subscriber and then disconnecting without unsubscribing). > > > On Dec 29, 2014 3:39 AM, "Sid" <[hidden email] > > > <http:///user/SendEmail.jtp?type=node&node=4689316&i=0>> wrote: > > > > > > > Hi there, > > > > > > > > What's the reason for getting following error on ActiveMQ- 5.10.0:- > > > > > > > > ActiveMQ service log:- > > > > 2014-12-17 01:16:37,153 | DEBUG | Checkpoint done. | > > > > org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal > > > > Checkpoint Worker > > > > 2014-12-17 01:16:39,481 | DEBUG | Sending: WireFormatInfo { > version=10, > > > > properties={MaxFrameSize=9223372036854775807, CacheSize=1024, > > > > CacheEnabled=true, SizePrefixDisabled=false, > > > > MaxInactivityDurationInitalDelay=10000, TcpNoDelayEnabled=true, > > > > MaxInactivityDuration=30000, TightEncodingEnabled=true, > > > > StackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]} | > > > > org.apache.activemq.transport.WireFormatNegotiator | ActiveMQ > > > > BrokerService[localhost] Task-530 > > > > *2014-12-17 01:16:39,569 | DEBUG | Transport Connection to: > > > > tcp://127.0.0.1:46804 failed: java.io.IOException: Java heap space > | > > > > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ > NIO > > > > Worker 2 > > > > java.io.IOException: Java heap space* > > > > at > > > > > > > > > > > > > > org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:39)[activemq-client-5.10.0.jar:5.10.0] > > > > > > > > at > > > > > > > > > > > > > > org.apache.activemq.transport.nio.NIOTransport.serviceRead(NIOTransport.java:151)[activemq-client-5.10.0.jar:5.10.0] > > > > > > > > at > > > > > > > > > > > > > > org.apache.activemq.transport.nio.NIOTransport$1.onSelect(NIOTransport.java:69)[activemq-client-5.10.0.jar:5.10.0] > > > > > > > > at > > > > > > > > > > > > > > org.apache.activemq.transport.nio.SelectorSelection.onSelect(SelectorSelection.java:94)[activemq-client-5.10.0.jar:5.10.0] > > > > > > > > at > > > > > > > > > > > > > > org.apache.activemq.transport.nio.SelectorWorker$1.run(SelectorWorker.java:119)[activemq-client-5.10.0.jar:5.10.0] > > > > > > > > at > > > > > > > > > > > > > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)[:1.7.0_05] > > > > > > > > at > > > > > > > > > > > > > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)[:1.7.0_05] > > > > > > > > at java.lang.Thread.run(Thread.java:722)[:1.7.0_05] > > > > 2014-12-17 01:16:39,570 | DEBUG | Unregistering MBean > > > > > > > > > > > > > > org.apache.activemq:type=Broker,brokerName=localhost,connector=clientConnectors,connectorName=nio_//localhost_61616,connectionViewType=remoteAddress,connectionName=tcp_//127.0.0.1_46804 > > > > > > > > | org.apache.activemq.broker.jmx.ManagementContext | ActiveMQ NIO > > Worker > > > 2 > > > > 2014-12-17 01:16:39,570 | DEBUG | Stopping connection: tcp:// > > > > 127.0.0.1:46804 > > > > | org.apache.activemq.broker.TransportConnection | ActiveMQ > > > > BrokerService[localhost] Task-531 > > > > 2014-12-17 01:16:39,570 | DEBUG | Stopping transport > > > > tcp:///127.0.0.1:46804@61616 | > > > > org.apache.activemq.transport.tcp.TcpTransport | ActiveMQ > > > > BrokerService[localhost] Task-531 > > > > 2014-12-17 01:16:39,571 | DEBUG | Initialized > > TaskRunnerFactory[ActiveMQ > > > > Task] using ExecutorService: null | > > > > org.apache.activemq.thread.TaskRunnerFactory | ActiveMQ > > > > BrokerService[localhost] Task-531 > > > > 2014-12-17 01:16:39,571 | DEBUG | Closed socket Socket[unconnected] > | > > > > org.apache.activemq.transport.tcp.TcpTransport | ActiveMQ Task-1 > > > > 2014-12-17 01:16:39,571 | DEBUG | Stopped transport: null | > > > > org.apache.activemq.broker.TransportConnection | ActiveMQ > > > > BrokerService[localhost] Task-531 > > > > 2014-12-17 01:16:39,571 | DEBUG | Connection Stopped: null | > > > > org.apache.activemq.broker.TransportConnection | ActiveMQ > > > > BrokerService[localhost] Task-531 > > > > 2014-12-17 01:16:42,156 | DEBUG | Checkpoint started. | > > > > org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal > > > > Checkpoint Worker > > > > 2014-12-17 01:16:42,264 | DEBUG | Checkpoint done. | > > > > org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal > > > > Checkpoint Worker > > > > 2014-12-17 01:16:43,833 | DEBUG | WriteChecker: 10000ms elapsed > since > > > last > > > > write check. | > org.apache.activemq.transport.AbstractInactivityMonitor > > | > > > > ActiveMQ InactivityMonitor 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. > > > > > > > > > > > > > ------------------------------ > > > If you reply to this email, your message will be added to the > discussion > > > below: > > > > > > > > > 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-tp4689306p4689316.html > > > To unsubscribe from DEBUG | Transport Connection to: tcp:// > > > 127.0.0.1:46804 failed: java.io.IOException: Java heap space | > > > org.apache.activemq.broker.TransportConnection.Transport, click here > > > < > > > > > > . > > > NAML > > > < > > > http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > > > > > > > > > > > > > > > > -- > > 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-tp4689306p4689329.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/DEBUG-Transport-Connection-to-tcp-127-0-0-1-46804-failed-java-io-IOException-Java-heap-space-org-apat-tp4689306p4689334.html > To unsubscribe from DEBUG | Transport Connection to: tcp:// > 127.0.0.1:46804 failed: java.io.IOException: Java heap space | > org.apache.activemq.broker.TransportConnection.Transport, click here > <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4689306&code=aGlyZW1hdGg0N0BnbWFpbC5jb218NDY4OTMwNnwtMTUyODU5ODEzMg==> > . > NAML > <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- 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-tp4689306p4689342.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
