I am seeing stuck message using AMQ 4.1 with JBoss embedded brokers, SLSB
producers, MDB consumers, vm transport and derby persistence. (Also with
an external JMS consumer.) I have 2 embedded brokers and 3 queues (1+2) so
far.
This seems to be a start-up issues. If I re-start JBoss, the queue(s) gets
unstuck and seem to run fine after that. (But I have not tested with a
heavy load.)
When I shutdown JBoss from the JMX Console I (always) get the following
error, which may or may not be related. Perhaps my EJBs need to be
clossing JMS connections?? Perhaps ActiveMQ is neglecting to close
them????
[ActiveMQManagedConnection] Error occured during close of a JMS connection.
javax.jms.JMSException: Peer (vm://localhost#35) disposed.
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:58)
at
org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1153)
at
org.apache.activemq.ActiveMQConnection.close(ActiveMQConnection.java:578)
at
org.apache.activemq.ra.ActiveMQManagedConnection.destroy(ActiveMQManagedConnection.java:225)
--
View this message in context:
http://www.nabble.com/Is-anyone-else-seeing-messages-stuck-on-a-queue--tf3027911.html#a8524461
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
