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.