If there is no correct database connection in the WebSphere environment, the following error will be played in the systemout.log file: [06-5-9 17: 02: 07: 458 GMT 08: 00] 1AE9F948 SharedPool i J2CA0086W: In the local transaction, the boundary jdbc resource use / unicall can share 1df4f943 Managed connection com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl@17feb94d State connection MCWrapper id: STATE_TRAN_WRAPPER_INUSE after a large number of such information occurs, the system may be down in detail can be found in IBM. Document description. WebSphere uses the rules of local transaction management, which generally writes database processing logic in accordance with the following rules in the WebSphere environment.
Get ConnectionUse ConnectionClose ConnectionCommit Transaction If the following method is used, it is possible to cause deadlock Get Con1; use con1; get con2; // a new connection is created.// We can't Reuse Con1 Because // IT Hasn't Been Closed.use con2; close con1; close con2; solution has two: increasing connection pool size strictly writes programs in accordance with LocalTransaction
