I am having problems with "poison messages" in Glassfish..
I am using the standard Glassfish v2 installation, including message
queues and MDB, etc...
a message is delivered to the queue, consumed by a MDB that throws an
exception, and the message is then redelivered - creating the
deadlock...
how to avoid ? workaraound this ?
if I don't throw exceptions, the message will be considered consumed ?
what kind of method or exception may I use to force the message to not
be redelivered?