PM08945: IF PREPARED STATEMENT IS CREATED BUT NO QUERIES ARE RUN, CLEANUP OF IT MAY RESULT IN SQLEXCEPTION: NO ACTIVE RESULT AFTER PK85473

Fixes are available

APAR status

Closed as program error.

Error description

This problem is observed only with specific database drivers;
this problem can be produced using Informix or Sybase drivers
with WebSphere Application Server.  The problem happens when
cleaning up a prepared statement for which no queries were
executed.  The SQLException that is thrown is this:
.
[1/29/10 15:49:33:050 MST] 00000013 WSJdbcUtil    3
mapException

SQL STATE:  IX000
ERROR CODE: -79733
java.sql.SQLException: No active result
 at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.
java:373)
 at com.informix.jdbc.IfxStatement.getUpdateCount(IfxStatement.
java:1050)
 at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.
closeWrapper(WSJdbcPreparedStatement.java:445)
 at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.
java:185)
 at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.
java:144)
.
   This problem may be observed using Sybase or Informix for the
SIB persistence database.  In that case, the following error
messages would be logged.
.
[1/28/10 16:52:25:456 MST] 00000013 SibMessage    E
[verifybus:eWebtestNode01.server1-verifybus] CWSIS0002E: The
messaging engine encountered an exception while starting.
Exception:
com.ibm.ws.sib.msgstore.PersistenceException: CWSIS1501E: The
data source has produced an unexpected exception:
java.sql.SQLException: No active result
.
[1/28/10 16:52:25:459 MST] 00000013 MessageStoreI 1
[verifybus:eWebtestNode01.server1-verifybus/7bc87bc8] Exception:
com.ibm.ws.sib.msgstore.PersistenceException: CWSIS1501E: The
data source has produced an unexpected exception:
java.sql.SQLException: No active result
 at com.ibm.ws.sib.msgstore.persistence.impl.
PersistentMessageStoreI mpl.star t(PersistentMessageStoreImpl.
java:201)

.
WebSphere AppServer added cleanup code in the APARs PK70930
(6.0.2.35, 6.1.0.23, and 7.0.0.5) and PK85473 (6.1.0.29; it is
not yet available in 6.0 or 7.0 fix pack).

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application Server
****************************************************************
* PROBLEM DESCRIPTION: If a prepared statement is created but  *
*                      no queries are run, the cleanup of it   *
*                      may result in SQLException: No active   *
*                      result                                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebSphere Application Server customers using an Informix/Sybase
database would notice SQLException in their application when
they attempt to close a prepared statement for which no
queries were run.

Informix -- java.sql.SQLException: No active result
Sybase -- java.sql.SQLException: JZ0PA: The query has been
canceled and the response discarded.  The cancel was probably
issued by another statement on the connection.

Informix & Sybase interpreted the requirements of the JavaDoc
for Statement.getUpdateCount differently than we did in
WebSphere Application Server. Instead of returning -1, they
throw SQLException when no queries are run before we invoke
getUpdateCount().

Problem conclusion

The code has been fixed to resolve this problem.
The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.33.  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
PM08945
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
2010-03-03
Closed date
2010-05-04
Last modified date
2010-05-04

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

[{"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:
24 October 2021

Tips

PM08945: IF PREPARED STATEMENT IS CREATED BUT NO QUERIES ARE RUN, CLEANUP OF IT MAY RESULT IN SQLEXCEPTION: NO ACTIVE RESULT AFTER PK85473

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

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?