|
Home > Archive > WebSphere Application Server > April 2005 > 120 seconds trasaction time out
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
120 seconds trasaction time out
|
|
| ssiripuram 2004-05-23, 12:08 pm |
| Hi,
I have deployed one ear file on websphere 5.0.2.2. It throws the following exception some times. Could anybody help me in fixing this problem
[5/23/04 10:35:08:623 CDT] e584462 CoordinatorIm I WTRN0066W: Transaction (4) 0
001bba9:00000001041430ba371c62ef64a7b96e
00d7264d5cfceee5f025[] has timed out aft
er 120 seconds.
2004.05.23 10:36:09.074--UnitOfWork(1620231287)--Thread[Servlet.Engine.Transport
s : 58,5,main]--EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3.3 (Build 430)): oracle
toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: ORA-02049: timeout: distributed tr
ansaction waiting for lock
EXCEPTION DESCRIPTION: java.sql.SQLException: ORA-02049: timeout: distributed transaction waiting for lock
| |
| Ken Hygh 2004-05-24, 7:30 am |
| ssiripuram wrote:
>Hi,
>
>I have deployed one ear file on websphere 5.0.2.2. It throws the following exception some times. Could anybody help me in fixing this problem
>
>[5/23/04 10:35:08:623 CDT] e584462 CoordinatorIm I WTRN0066W: Transaction (4) 0
> 001bba9:00000001041430ba371c62ef64a7b96e
00d7264d5cfceee5f025[] has timed out aft
>er 120 seconds.
>2004.05.23 10:36:09.074--UnitOfWork(1620231287)--Thread[Servlet.Engine.Transport
>s : 58,5,main]--EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3.3 (Build 430)): oracle
>toplink.exceptions.DatabaseException
>EXCEPTION DESCRIPTION: java.sql.SQLException: ORA-02049: timeout: distributed tr
>ansaction waiting for lock
>EXCEPTION DESCRIPTION: java.sql.SQLException: ORA-02049: timeout: distributed transaction waiting for lock
>
>
>
this can be caused by any of a number of things. Your code may not be
committing or rolling back the transaction, which will cause this. A
database search may be taking longer than 120 seconds to complete. You
may have a deadlock.
Ken
| |
|
| Hi Sripuran,
Please send me the link of how you got the Websphere 5.0.2.2 Cumulative fix.
Is there is any place where i can find it ?
|
|
|
|
|