Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
In a very rare case involving the Sybase jConnect JDBC driver, hung threads like below were noticed in the logs. The hung threads occurred during CallableStatement.close() processing when WebSphere Application Server attempted to determine if the PreparedStatement could be cached. [1/17/11 14:05:37:041 CET] 00000023 ThreadMonitor W WSVR0605W: Thread "ORB.thread.pool : 25" (00000053) has been active for 690828 milliseconds and may be hung. There is/are 3 thread(s) in total in the server that may be hung. at com.sybase.jdbc3.utils.CacheManager.beginReading(Unknown Source) at com.sybase.jdbc3.utils.CacheManager.open(Unknown Source) at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.getMoreResults(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.getMoreResults(Unknown Source) at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.closeWrapper(W SJdbcPre paredStatement.java:446)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Selectable fix for avoiding hung * * threads noticed with Sybase JConnect * * JDBC Driver * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PK85473 addressed a possible leak by adding code to check for unprocessed results set objects before placing a statement in the cache. When the customer who reported this issue moved up to the level that included apar PK85473 and used jConnect JDBC Driver to connect to Sybase, hung threads like below were noticed in the logs. This problem surfaced in the Sybase jConnect JDBC driver and is being exposed by WebSphere code which was added under APAR PK85473 (and related fixes) to prevent caching of PreparedStatements with unprocessed results. ThreadMonitor W WSVR0605W: Thread "ORB.thread.pool : 25" (00000053) has been active for 690828 milliseconds and may be hung. There is/are 3 thread(s) in total in the server that may be hung. at com.sybase.jdbc3.utils.CacheManager.beginReading(UnknownSource) at com.sybase.jdbc3.utils.CacheManager.open(Unknown Source) at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.getMoreResults(UnknownSource) at com.sybase.jdbc3.jdbc.SybStatement.getMoreResults(UnknownSource) The exact cause of the hang has not been determined, but appears to manifest only under particular conditions. Possible factors are CallableStatement parameter data types, stored procedure results data types, jConnect internal state, or other conditions present in the environment of the customer reporting the problem. We expect that most customers will never encounter this issue. Through apar PM40751 we introduce a datasource custom property "skipCheckForUnprocessedResults" which can be enabled to bypass the code which was intended to address PK85473, i.e skip the check for unprocessed results set objects before placing a statement in the cache. Well-behaved applications which process all results produced when invoking a PreparedStatement have no need for WebSphere to check for unprocessed results and this check can safely be bypassed. Bypassing the check for unprocessed results avoids the sensitive path in the JDBC driver. To enable the fix, set a datasource custom property "skipCheckForUnprocessedResults" to true. You can set the datasource custom property by opening the administrative console and navigating to Resources > JDBC > JDBC providers > (JDBC Provider Name) > Data sources > (Datasource name)> Custom properties.
Problem conclusion
This fix introduces the datasource custom property skipCheckForUnprocessedResults. Only enable this fix if you notice a hang situation when using Sybase JConnect JDBC Driver as described in the APAR. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.19 and 8.0.0.1. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM40751
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-06-03
Closed date
2011-06-29
Last modified date
2011-06-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
27 October 2021