Looks like we have some sort of tcpBufferedInputStream.fill issue going on, consuming most of the cpu.
-- View this message in context: http://activemq.2283324.n4.nabble.com/HIGH-CPU-and-Java-Threads-Post-Upgrade-to-5-10-tp4685559p4685561.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
