Downgrading to JDK 1.6 from 1.7 resolves the strange ever-growing CPU problem.
Interestingly, the top thread in terms of CPU usage becomes the "Selector Worker: 0" after the downgrade. http://activemq.2283324.n4.nabble.com/file/n4654368/mq_topThreads_16.png I agree it feels like a livelock of some sort that spontaneously resolves itself every 12 hours. I can foresee spending some more time doing load testing against an ActiveMQ instance on JDK 1.7 in a staging environment in the future with extra logging enabled, but we're likely to defer any further investigation since running an older JDK allows us to move onto other production matters and defer this problem until the broader community attempts to run ActiveMQ on 1.7. -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-6-CPU-steadily-increases-but-drops-at-noon-and-midnight-exactly-tp4654328p4654368.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
