Hi all,
Thanks for all your concerns and considerations. Yesterday I've made a
thread dump and as vaguely expected it was the main thread which was waiting
for a System.in.read() call that was requesting the call. For now I've
replaced it with
InputStreamReader reader = new
InputStreamReader(System.in);
while (true) {
if (Thread.interrupted()) {
break;
}
if (reader.ready() &&
Character.getType(reader.read()) == 15) {
break;
}
Thread.sleep(1000);
}
which wipes out the 100% CPU usage alltogether. It was no activeMQ issue, so
that's positive!
All the best,
Niels
--
View this message in context:
http://activemq.2283324.n4.nabble.com/100-CPU-tp4665414p4666189.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
