|
Problem |
This error message also contains the
following:
DB2 7.1 SQLJ/JDBC>> 00C9008E 00000302 ODNC401 .SNCSC46 .X'0004F5'
..
03/12/04 13:18:54 1000005 ERR com.ibm.db2.jcc.DB2SQLException.
If you are running WebSphere® Application Server for z/OS® V4.0.1 with
CICS® TS 2.2 (using EXCI resource adapter) and DB2® V7, using Global
transaction coordination, and you experience timeouts in WebSphere
Application Server and DB2 timeout errors in the DB2 log, you might have
this problem.
CICS CTG requests comes back with zero return code. Global transaction
fails and deadlocking occurs in the same DB2 resource. Within the same
Global transaction, CICS and WebSphere Application Server attempt to
update the same row in the DB2 table, resulting in the timeout.
|
|
Cause |
This behavior is not supported in the Web Container,
according to EJB™ 1.1 specification. |
|
Solution |
The situation that is described here is referred to as a
distributed diamond scenario. This is when two clients in the same
transaction attempt to access the same entity object, which in this case
is a database row.
The EJB 1.1 specification points this out and states that the container
does not have to provide this support. This is not supported in the Web
Container. It is also not supported if you invoke a session bean in CICS
and go after the same database row.
|
|
|
|
|
|
|
|