Right now there are any number of ways to cause JBoss to spin in a tight
loop
trying to deliver a transacted msg to an mdb due to a problem with either
the msg or mdb code that either causes an exception thrown from onMessage()
or the tx to be rolled back. A trivial example of the latter is to have an
mdb
do a findByPrimaryKey() using a key from the msg that happens to be null.
One solution would be to have the mdb container fail such msgs after so
many delivery attempts. On failure, the msg along with the exception would
be placed into a error queue associated with the container. An admin would
have to pull the msg off, fix any data problems and then place the msg
back onto the mdb queue/topic for redelivery.
Are there any better ways to handle this?
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
