PM19904: DATABASE CONNECTION TO AN ORACLE DATABASE THAT IS ACCESSING A STORED PROCEDURE WILL HANG WHEN CONNECTION.CLOSE IS CALLED

Fixes are available

APAR status

Closed as program error.

Error description

The following hung thread stack trace will be generated in the
SystemOut.log whenever a connection.close() method is called on
an Oracle database connection that is accessing a stored
procedure:


[5/20/10 13:22:19:154 CST] 00000031 ThreadMonitor W   WSVR0605W:
Thread "WebContainer : 5" (000000cf) has been active for 601448
milliseconds and may be hung.  There is/are 1 thread(s) in total
in the server that may be hung.

at
com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.closeWrapper(W
SJdbcPreparedStatement.java:445)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcCallableStatement.closeWrapper(W
SJdbcCallableStatement.java:236)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java:1
85)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java:1
44)
at
com.ibm._jsp._testprocedure$test.method(_testprocedure.java:63)
at
com.ibm._jsp._testprocedure._jspService(_testprocedure.java:121)
at
com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
apper.java:1146)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
apper.java:1087)
at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp
FilterChain.java:118)
at
com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAp
pFilterChain.java:87)
at
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebA
ppFilterManager.java:848)
at
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebA
ppFilterManager.java:691)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser
vletWrapper.java:588)
at
com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(S
ervletWrapper.java:525)
at
com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleR
equest(GenericServletWrapper.java:122)
at
com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrappe
r.handleRequest(AbstractJSPExtensionServletWrapper.java:232)
at
com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleReques
t(CacheServletWrapper.java:90)
at
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.
java:764)
at
com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContaine
r.java:1478)
at
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLin
k.java:133)
at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr
imination(HttpInboundLink.java:458)
at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewIn
formation(HttpInboundLink.java:387)
at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpI
nboundLink.java:267)
at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sen
dToDiscriminators(NewConnectionInitialReadCallback.java:214)
at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.com
plete(NewConnectionInitialReadCallback.java:113)
at
com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureComp
leted(AioReadCompletionListener.java:165)
at
com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyn
cFuture.java:217)
at
com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncC
hannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at
com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
at
com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHand
ler.java:751)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497)

Local fix

set prepared statement cache size to "0" on data source

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0 who use stored         *
*                  procedures mostly with Oracle as the        *
*                  back-end database                           *
****************************************************************
* PROBLEM DESCRIPTION: Hung threads stack trace seen in        *
*                      systemout.log while closing an Oracle   *
*                      connection running a stored procedure   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The following hung thread stack trace would be logged in the
SystemOut.log
[5/20/10 13:22:19:154 CST] 00000031 ThreadMonitor W   WSVR0605W:
Thread "WebContainer : 5" (000000cf) has been active for 601448
milliseconds and may be hung.  There is/are 1 thread(s) in total
in the server that may be hung.
at
com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.closeWrapper(W
SJdbcPreparedStatement.java:445)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcCallableStatement.closeWrapper(W
SJdbcCallableStatement.java:236)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java:1
85)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java:1
44)
at
com.ibm._jsp._testprocedure$test.method(_testprocedure.java:63)

when a connection.close() is called on an Oracle database
connection that is accessing a stored procedure that has
unprocessed result sets.

Problem conclusion

When unprocessed results exist in a statement then they would
be processed before caching the statement, otherwise there
would be a leak in statements. Because Oracle was not returning
the right updateCount there was a problem in processing the
unprocessed results.
To work-around this problem, the adapter code has been
modified to cache a statement only when there are no
unprocessed results. If unprocessed results exist in a
statement then the statement will be closed rather than being
cached.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.37 and 7.0.0.15.  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
PM19904
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-08-05
Closed date
2010-10-12
Last modified date
2011-02-15

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61S PSY
UP
R61W PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM19904: DATABASE CONNECTION TO AN ORACLE DATABASE THAT IS ACCESSING A STORED PROCEDURE WILL HANG WHEN CONNECTION.CLOSE IS CALLED

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61S PSY

R61W PSY

R700 PSY

Document Information

Share your feedback

Need support?