activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin C. van Vorst" <pra...@gmail.com>
Subject Re: OutOfMemoryError using 4.1.1
Date Tue, 24 Apr 2007 16:49:46 GMT

Please don't hijack my thread.  Now I'm not sure whether Christopher's
comment in any way applies to my problem.



avin98 wrote:
> 
> I have hit an OOMError without using persistent messages, and even if AMQ
> is inactive for a period of about a day or so.
> 
> [4/22/07 11:17:44:727 PDT]  [WARN] - [GeronimoConnectionEventListener] -
> connectionErrorOccurred called with null
> javax.jms.JMSException: Channel was inactive for too long.
> 	at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:46)
> 	at
> org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1519)
> 	at
> org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1535)
> 	at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:96)
> 	at
> org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:114)
> 	at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:96)
> 	at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:96)
> 	at
> org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:147)
> 	at
> org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:150)
> 	at
> org.apache.activemq.transport.InactivityMonitor.readCheck(InactivityMonitor.java:101)
> 	at
> org.apache.activemq.transport.InactivityMonitor.access$000(InactivityMonitor.java:35)
> 	at
> org.apache.activemq.transport.InactivityMonitor$1.run(InactivityMonitor.java:51)
> 	at
> edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
> 	at
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.runAndReset(FutureTask.java:198)
> 	at
> edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:102)
> 	at
> edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:189)
> 	at
> edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:213)
> 	at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> 	at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> 	at java.lang.Thread.run(Thread.java:799)
> Caused by: 
> org.apache.activemq.transport.InactivityIOException: Channel was inactive
> for too long.
> 	... 11 more
> JVMDUMP006I Processing Dump Event "uncaught", detail
> "java/lang/OutOfMemoryError" - Please Wait.
> JVMDUMP007I JVM Requesting Snap Dump using
> '/opt/WebSphere/AppServerCommunityEdition/bin/Snap0001.20070422.112429.8876.trc'
> JVMDUMP010I Snap Dump written to
> /opt/WebSphere/AppServerCommunityEdition/bin/Snap0001.20070422.112429.8876.trc
> JVMDUMP007I JVM Requesting Heap Dump using
> '/opt/WebSphere/AppServerCommunityEdition/bin/heapdump.20070422.112429.8876.phd'
> JVMDUMP010I Heap Dump written to
> /opt/WebSphere/AppServerCommunityEdition/bin/heapdump.20070422.112429.8876.phd
> JVMDUMP007I JVM Requesting Java Dump using
> '/opt/WebSphere/AppServerCommunityEdition/bin/javacore.20070422.112429.8876.txt'
> UTE503: utsGetTracePointIterator cannot allocate iterator's buffer
> JVMDUMP010I Java Dump written to
> /opt/WebSphere/AppServerCommunityEdition/bin/javacore.20070422.112429.8876.txt
> 
> 

-- 
View this message in context: http://www.nabble.com/OutOfMemoryError-using-4.1.1-tf3632613s2354.html#a10165073
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message