PI16932: CLOSE NAMING CONTEXT BEFORE CREATING CONTEXT WRAPPER

Fixes are available

APAR status

Closed as program error.

Error description

In a DB2 client reroute scenario, when the database has failed
over successfully, the JDBC driver will try to update the JNDI
namestore but get the following exception:

[3/4/14 12:09:11:340 GMT+08:00] 00000022 CNContextImpl <
rebind Exit
javax.naming.NamingException: Context closed
at com.ibm.ws.naming.jndicos.CNContextImpl.rebind
at com.ibm.ws.naming.jndicos.CNContextImpl.rebind
at com.ibm.ws.rsadapter.spi.WSJndiContextWrapper$2.run
at com.ibm.ws.security.auth.ContextManagerImpl.runAs
at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem
at com.ibm.ws.security.core.SecurityContext.runAsSystem
....

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: When the application explicitly         *
*                      closes the naming context, context      *
*                      closed exception is thrown in the DB2   *
*                      Client reroute scenario during client   *
*                      reroute JNDI lookup                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the application explicitly closes the naming context,
context closed exception is thrown in the DB2 Client reroute
scenario during client reroute JNDI lookup.
Naming context used in the initial lookup is passed to DB2 for
client reroute and since the context is closed it throws the
exception

Problem conclusion

Named context is cloned and passed to DB2 for client reroute.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.35, 8.0.0.10 and 8.5.5.3.  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
PI16932
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-04-29
Closed date
2014-06-10
Last modified date
2014-06-10

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

R700 PSY
UP
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PI16932: CLOSE NAMING CONTEXT BEFORE CREATING CONTEXT WRAPPER

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

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?