You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by jgunz <sl...@twcny.rr.com> on 2008/02/21 15:05:37 UTC

Old message cleanup failed

I'm occasionally seeing the following error message in my ActiveMQ 4.1.1 log,
when it happens all of my consumers block on opening connections..

2008-02-21 12:19:20,657 [eckpoint Worker] WARN  JDBCPersistenceAdapter        
- Old message cleanup failed due to: SQL Exception: Java exception: 'GC
overhead limit exceeded: java.lang.OutOfMemoryError'.

How can I correct this? 

Also, I thought I had persistence disabled so I'm not sure why it's even
doing anything with persistence, below is my configuration:

<beans>

  <!-- Allows us to use system properties as variables in this configuration
file -->
  <bean
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>

  <broker brokerName="localhost" useJmx="true"
xmlns="http://activemq.org/config/1.0">

    <!-- Use the following to configure how ActiveMQ is exposed in JMX -->
    <managementContext>
       <managementContext connectorPort="1098"
jmxDomainName="org.apache.activemq"/>
    </managementContext>

    <!-- Persistence setup
    DISABLED
    <persistenceAdapter>
        <journaledJDBC journalLogFiles="5"
dataDirectory="${activemq.base}/activemq-data"/>
    </persistenceAdapter>
    -->

    <transportConnectors>
       <transportConnector name="openwire" uri="tcp://localhost:61606"/>
       <transportConnector name="http" uri="http://localhost:61608"/>
    </transportConnectors>

  </broker>

</beans>

-- 
View this message in context: http://www.nabble.com/Old-message-cleanup-failed-tp15612129s2354p15612129.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: Old message cleanup failed

Posted by jgunz <sl...@twcny.rr.com>.
Here's some additional log messages I'm seeing after a restart:

2008-02-21 13:59:25,068 [eckpoint Worker] WARN  JDBCPersistenceAdapter        
- Old message cleanup failed due to: SQL Exception: Java exception: 'GC
overhead limit exceeded: java.lang.OutOfMemoryError'.
2008-02-21 13:59:39,731 [eckpoint Worker] ERROR JournalPersistenceAdapter     
- Failed to checkpoint a message store:
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
java.lang.OutOfMemoryError: GC overhead limit exceeded
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
java.lang.OutOfMemoryError: GC overhead limit exceeded
    at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299)
    at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118)
    at
org.apache.activemq.store.journal.JournalPersistenceAdapter.doCheckpoint(JournalPersistenceAdapter.java:386)
    at
org.apache.activemq.store.journal.JournalPersistenceAdapter$2.iterate(JournalPersistenceAdapter.java:129)
    at
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:101)
    at
org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25)
    at
org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
2008-02-21 14:07:15,568 [s Monitor: http] ERROR TransportStatusDetector       
- failed to complete a sweep for blocked clients
java.lang.OutOfMemoryError: GC overhead limit exceeded
2008-02-21 14:08:16,903 [eckpoint Worker] WARN  JDBCPersistenceAdapter        
- Old message cleanup failed due to: SQL Exception: A lock could not be
obtained within the time requested
2008-02-21 14:11:48,787 [nitor: openwire] ERROR TransportStatusDetector       
- failed to complete a sweep for blocked clients
java.lang.OutOfMemoryError: GC overhead limit exceeded
2008-02-21 14:15:18,291 [eckpoint Worker] WARN  JDBCPersistenceAdapter        
- Old message cleanup failed due to: SQL Exception: The exception
'java.lang.OutOfMemoryError: GC overhead limit exceeded' was thrown while
evaluating an expression.
2008-02-21 14:21:21,598 [eckpoint Worker] WARN  JDBCPersistenceAdapter        
- Old message cleanup failed due to: SQL Exception: A lock could not be
obtained within the time requested

-- 
View this message in context: http://www.nabble.com/Old-message-cleanup-failed-tp15612129s2354p15612448.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.