Problem with JTATransactionManager recently, amount, where

amy

Hi,
I am facing a peculiar problem with transaction in Spring. My project is using JTATransactionManger and is working fine. But there was a load testing conducted recently which got the application stuck up. The scenarion is as follows:
There is an MDB that listens to a queue and corresponding to each message received it generates a sequence id and assigns that to the message. (btw I am using Oracle as the database and Weblogic 8.1 as the appserver). Now in case where there is a large amount of messages(say around 30,000) some messages are getting transaction timeout error. That seems pretty obvious as the the number of connections it can get at a time is limited. Now after that the application is getting stuck up although there is free connection in the pool.

Has anyone faced this type of problem earlier? What can be the reason behind this?There is nothing in the log except the transaction timeout error.

What exactly are you doing in the MDB. What do you mean by quot;assigning a sequence to a messagequot;. Is there some additional database update involved where you might get into resource locking problems?

The MDB is getting the message, generate a sequence and assign it to the message and then persists the message in other tables. I mentioned the sequence generation part specifically because the log extract shows that it is getting a transaction timeout while generating the sequence.

We have experienced a similar problem with WebLogic 9.1.   I have noticed that our read-only queries are timing out when trying to commit....which I don't understand why they are trying to commit.

Did you find any resolution to your issue?

No solution still..I will would rather ask Spring developers to look into this matter....