This next issue is very serious for us and urgently needs a resolution. I'm sure that it's the same issue I see described here at this link:
http://ecommunity.groupintelligence.com/websphere/forums/archive/index.php/t-1027.html http://ecommunity.groupintelligence.com/websphere/forums/archive/index.php/t-1027.html We've commented out all of our Oracle JDBC persistence, so this just applies to ActiveMQ-4.1.1 out of the box installed and running on the same box as WSAD running WebSphere. If we restart the app server, it comes up fine if the ActiveMQ queues are empty. If, however, there are messaging queued up, the app server hangs. This is the most serious issue we've encountered so far, since it means we can't have any sort of error recovery whatsoever. Has anybody run into this, and can anyone please suggest something to try as a resolution/workaround? Thanks. -- View this message in context: http://www.nabble.com/Urgent%3A-App-server-%28websphere%29-unable-to-restart-if-queue-not-empty-tf4601684s2354.html#a13138542 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
