|
| Problem | In this scenario WebSphere 3.5.x or 4.0.x has DB2 7.2 fp 5 of DB2 Connect (or
the client DB2 Instance). If javacores are taken 2 minutes apart during the
hang scenario they would show that several threads remain in
DB2PreparedStatement.SQLExecute() and don't seem to recover. | | | | Solution | On the WebSphere Application Server website, the prereq page shows that we don't recommend running with DB2 7.2 FP5. This particular problem has been resolved by applying FP6 to DB2 Connect. Note : Connections to DB2 390 may require z-parm changes as well, including increasing the max remote connections and max threads, and changing thread from active to inactive. | |
| | | | Product Alias/Synonym | WAS | |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Java 2 Connectivity (J2C) Operating system(s): Multi-Platform Software version: 3.5.x, 4.0.x Software edition: Advanced Reference #: 1066310 IBM Group: Software Group Modified date: 2002-10-11
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|