I am using WebSphere Studio Application Developer (WSAD 5.0). My Application has Stateless Session Beans. These Beans call Data Access Objects (DAOs) for Database Operations (DB used is Oracle 8). In a particular bean's method, the Database operations to be done are huge and take some time in minutes (large no. of record updates). However after 120 seconds, the WSAD server console gives a message saying "Transaction XXXXXXX has timed out after 120 seconds" which leaves the Bean operation incomplete. The Session Bean used is Stateless and has Container Managed Transaction. Is 120 seconds the default value for Container Managed Transaction to timeout? Is this value configurable? Please advice.
Yes, the transaction timeout is editable within WSAD, but only by using the WebSphere Administration console. In WSAD, pick your WebSphere server and make sure the "Enable Administration console" box is checked. Then start your server. Then open a browser and type http://localhost:9090/admin to open the admin console. In the Admin console, pick the Servers tree and select your application server. In the Application Servers page for your server, pick the "Transaction Service" under "Additional Properties". On this page you can change the transaction timeout from the default (120 seconds) to a larger value. Make sure you press "Apply" and also that you Save your application server configuration. You will then probably get a notice in WSAD indicating that your server has changed. Accept the changes. Kyle
Hey Kyle! That was very prompt. And which is why I was wondering, where the Configuration parameter was. No doubt, I could not find it in WSAD Server Configuration. :-) Excellent directions, thanks! I am now able to configure the time out. Thanks, once again... Chethan.
We get the transaction timeout message in the log [10/18/04 14:11:02:729 EDT] 4bfd76cd TimeoutManage I WTRN0006W: Transaction 57415344:000000000000026f00000001d19858cf914fd558ac48b08499a1b7674c4a5331617349636973 has timed out after 120 seconds.
I'm facing the same problem in the Websphere AS. Is there any other way to solve this problem? I'm asking because my environment don't allows this kind of modification(alter the server configuration), so I would to know if any of you knows any other solution.
I'm processing a file that have around 5000 records to insert into my database and I'm getting time out when the inserts still running.
Thank you guys,
The Death of one is a tragedy, but the Death of a million is just a statistic. Joseph Stalin
SCJP 6.0, SCJD
subject: Transaction Times Out after 120 seconds in Session Bean Operation