Thanks for the response. I guess that means either the machine that is running the benchmark might have something going on with it or perhaps it's the benchmark itself. Are there any known issues with the benchmark that anyone may know about that could be causing this type of error?
-- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-log-question-tp3769350p3772216.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
