Missing cleanup() after second (local) transaction rollback

Question

          I wrote a simple dummy ressource adapter with local and XA transaction support and
          discovered some problems when using this adapter within an stateless session bean
          that calls setRollbackOnly().
          If I configure the resource adapter for XATransaction support, everything runs fine:
          WebLogic (or its ConnectionManager) detects the transaction rollback calls my cleanup()
          method and delists the connection from the list of busy connections (so I can do
          my rollback test with this connection a often as I want).
          If I configure my resource adapter for LocalTransaction support, the connection also
          is delisted from the list of busy connections (my cleanup method also is called)
          but after a second rollback test the connection remains in the busy connection list
          (and the cleanup call is missing). So calling the rollback test a third time brings
          a ResourceAllocationException.
          I am wondering whether the "mysterious" java.lang.IllegalStateException: Cannot delist
          resource, transaction has been rolled back
          that comes within my server log has something to do with my problem.
          Attched is my server log that reflects the situation.
          Thanks for any hint,
          juergen
          [connectorlog.txt]
          

Answer 1

Hi Neelam,
I am sure what exactly your application needs for single-threaded process.
If you have some thread context in a given thread that you need for correctly handle all message, then you may try to set max-free-pool-size to 1 on the MDB to force single threaded.
You can find more information in MDB tuning doc at http://download.oracle.com/docs/cd/E17904_01/web.1111/e13814/mdbtuning.htm#PERFM271
If all you need is to sequentially handle all messages and it does not matter if the processing is done in a particular thread, you could use a JMS feature called Unit-of-order (UOO) together with MDBs. JMS UOO gives you the capability of making sure all messages in one UOO group are processed sequentially and in the order that them are produced, even when there are multiple consumers or redelivery of messages due to fialures. Messages in different UOO groups can be processed in parallel.
For more information about UOO can be found at http://download.oracle.com/docs/cd/E17904_01/web.1111/e13727/uoo.htm#JMSPG389
The following link discusses how to process messages in order with MDBs. Re: Transaction-Rollback on foreign jms queue usin Singletonservice in weblogic
Hope these links help you find the right solution for your application.
Dongbo