Does anyone know what the transactional behavior of an MDB with NOT_SUPPORTED will be with respect to the message which it is processing? For example, should the message be ack'd and committed before onMessage() is called, or after as it would if it was REQUIRED.
It seems that if it is done after, then there is a tx. which contradicts the NOT_SUPPORTED declaration. Does anyone know how the message tx works when the MDB is bean managed instead of container managed either? Basically I am trying to get an MDB to ack a message mid-way through onMessage() to indicate that the message should not be redelivered, but I need onMessage() to block afterwards to wait for a long lived process to do some work. Anyone had to do this before? I believe this works fine with JBossMQ, but SwiftMQ will hang on the ack. waiting for the tx to commit (which it will never do as the MDB is locked now). MDB really pisses me off. I should just stop using them. but that is entirely too much work at the moment. =( --jason ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
