MQSeries.net :: View topic - Message Driven Bean (Transaction Control Problem)

nakuser

I have a an MDB running in websphere, listening to messages from MQ series. The bean sends the message to a Session bean which has Transaction control settings set as Required. When the responce comes back from the Bean, Transaction manager tries to commit and release all the resources that are held.
As a result all the dirty entity beans will have their ejbStore() methods invoked.

The Entity beans which are being persisted are set as BMP. One of the bean's instance hangs on the execution of it's PreparedStatement thus the Session bean never completes it's transaction to return a result to the message driven bean. The Session bean hangs at the point where it has to leave it's stub ==> and return to the MDB ==>. The Stub passes control over to the ==> transaction manager and the manager calls all the ==>Entity beans ejbStore() methods, then the execution of an update statement hangs. I put displays in the store method to see if there is a clash of keys, and no duplicate keys are used. A number of the instances are persited but at some point the thing hangs. There is no dead lock reported by the Database, the transaction ultimately times out and you get a dump to show the method calls (Stack trace).

I tried to isolate the problem by writting a Client class which calls my Session Bean to see if the problem is in the remote Components where the Entity bean reside.
With luck the transaction started by the Session bean completes and returns to my Client program.

So I am stuck. I have tried everything under sun.

In short "HELP".

I have been looking at this problem for more than Three weeks. By the way, I am using Web Sphere Studio Developer Version 5 and the database we are using is DB2 UDB.
_________________
SCJP