View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820440#3820440
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820440 There is an occasion when it will stop delivering messages to a message listener, this is usually caused by an unhandled error trying to receive messages. This normally happens when JBoss doesn't understand what the error means, e.g. some corruption caused by the network transport or a request the server did not understand and threw back to the client. Unless you have log4j enabled in the client you wouldn't see the warning: catch (JMSException e) { log.warn("Message consumer closing due to error in listening thread.", e); try { close(); } catch (Exception ignore) { } } It might be that an error occurred while the session was delivering the message to the consumer and the message got stuck in the session (i.e. it wasn't nacked as undeliverable). It should be nacked (negatively acknowledged) by the server if the client closes the connection or disconnects. I would need to see the warning logged above to find out what error JBossMQ failed to handle. Restarting JBoss (or redeploying the topic) will cause the subscriptions to be recovered from the persistent store. The "lost" message will be available again. Regards, Adrian ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
