PK71342: J2C OBJECTS ARE NOT SERIALIZING CORRECTLY CAUSING J2CA0020E ERROR

Fixes are available

APAR status

Closed as program error.

Error description

Java 2 Connector (J2C objects are not serializing correctly
causing a J2CA0020E error.

This problem was discovered in WebSphere Application Server
v6.1.0.17.

The exception stack trace for the error was as followed:

7/18/08 14:37:12:166 IST] 00000066 ResourceAdapt W   J2CA0278W:
Could not de-serialize field transactionSupport in class
com.ibm.ejs.j2c.ResourceAdapterDDImpl; default value will be
used
[7/18/08 14:37:12:166 IST] 00000066 ResourceAdapt W   J2CA0278W:
Could not de-serialize field reauthenticationSupport in class
com.ibm.ejs.j2c.ResourceAdapterDDImpl; default value will be
used
[7/18/08 14:37:12:170 IST] 00000066 ConnectionMan E   J2CA0020E:
The Connection Pool Manager could not allocate a Managed
Connection: java.lang.IllegalStateException: Internal Error:
cannot find the PoolManager Reference.
at
com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionMa
nager.java:864)
at
com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionM
anager.java:599)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcD
ataSource.java:439)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcD
ataSource.java:408)
at
com.ibm.wast.parlay.utils.ManagedServiceManager.getNewAssignment
ID(ManagedServiceManager.java:2452)
at
com.ibm.wast.parlay.RuntimeAccessorBean.getAssignmentID(RuntimeA
ccessorBean.java:93)
at
com.ibm.wast.parlay.EJSRemoteStatelessRuntimeAccessor_34dad9b7.g
etAssignmentID(EJSRemoteStatelessRuntimeAccessor_34dad9b7.java:2
7)
at
com.ibm.wast.parlay._RuntimeAccessor_Stub.getAssignmentID(_Runti
meAccessor_Stub.java:306)
at
com.ibm.wast.parlay.utils.ManagedServiceManager.generateAssignme
ntId(ManagedServiceManager.java:2222)
at
com.ibm.wast.parlay.utils.ManagedTriggeredUserLocationManager._t
riggeredLocationReportingStartReq(ManagedTriggeredUserLocationMa
nager.java:754)
at
com.ibm.wast.parlay.utils.ManagedTriggeredUserLocationManager.tr
iggeredLocationReportingStartReq(ManagedTriggeredUserLocationMan
ager.java:651)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
Impl.java:79)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
AccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at
com.ibm.wast.parlay.remote.ParlayConnectorRemoteBean.invoke(Parl
ayConnectorRemoteBean.java:377)
at
com.ibm.wast.parlay.remote.EJSRemoteStatelessParlayConnectorRemo
te_bebe6450.invoke(EJSRemoteStatelessParlayConnectorRemote_bebe6
450.java:204)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
Impl.java:79)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
AccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.ibm.rmi.util.ProxyUtil$4.run(ProxyUtil.java:727)
at
java.security.AccessController.doPrivileged(AccessController.jav
a:246)
at
com.ibm.rmi.util.ProxyUtil.invokeWithClassLoaders(ProxyUtil.java
:725)
at
com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:115
7)
at $Proxy7.invoke(Unknown Source)
at
com.ibm.wast.parlay.remote._ParlayConnectorRemote_Stub.invoke(_P
arlayConnectorRemote_Stub.java:574)
at
com.ibm.wast.parlay.remote.managers.RemoteableServiceBase.invoke
(RemoteableServiceBase.java:159)
at
com.ibm.wast.parlay.remote.managers.RemoteableUserLocationManage
r.triggeredLocationReportingStartReq(RemoteableUserLocationManag
er.java:376)
at
com.ibm.mds.loc.mapp.parlay.NotificationUtil.startParlayNotifica
tion(NotificationUtil.java:766)
at
com.ibm.mds.loc.mapp.parlay.NotificationUtil.startParlayNotifica
tion(NotificationUtil.java:811)
at
com.ibm.mds.loc.mapp.parlay.TerminalLocationParlayMapper.startGe
ographicalNotification(TerminalLocationParlayMapper.java:842)
at
com.ibm.mds.loc.mapp.parlay.TerminalLocationParlayMapper.process
(TerminalLocationParlayMapper.java:235)
at
com.ibm.mds.comm.SyncNetworkMapper.preProcess(SyncNetworkMapper.
java:123)
at
com.ibm.mds.comm.SyncPacedNetworkMapper.preProcess(SyncPacedNetw
orkMapper.java:228)
at com.ibm.mds.comm.CommonLayer.process(CommonLayer.java:285)
at
com.ibm.mds.loc.ctrl.TerminalLocationNotificationManagerBindingI
mpl.startGeographicalNotification(TerminalLocationNotificationMa
nagerBindingImpl.java:134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
Impl.java:79)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
AccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at
com.ibm.ws.webservices.engine.dispatchers.java.JavaDispatcher.in
vokeMethod(JavaDispatcher.java:178)
at
com.ibm.ws.webservices.engine.dispatchers.java.JavaDispatcher.in
vokeOperation(JavaDispatcher.java:141)

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0                        *
****************************************************************
* PROBLEM DESCRIPTION: Underlying problems with serializing    *
*                      and de-serializing of connection        *
*                      manager objects may cause               *
*                      connection manager errors.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When connection manager objects experience problems during
serialization or de-serialization, warnings similar to the
following are logged:
J2CA0278W: Could not de-serialize field transactionSupport in
class com.ibm.ejs.j2c.ResourceAdapterDDImpl; default value will
be used,
it may cause the following getConnection() errors:
J2CA0020E: The Connection Pool Manager could not allocate a
Managed Connection: java.lang.IllegalStateException: Internal
Error: cannot find the PoolManager Reference.
at
com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionMa
nager.java:864)
at
com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionM
anager.java:599)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcD
ataSource.java:439)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcD
ataSource.java:408)

Problem conclusion

Connection manager classes have been corrected to avoid
serialization and de-serialization problems.

The fix for this APAR is currently targeted for inclusion in
fixpacks 6.1.0.23 and 7.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
PK71342
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
60W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-08-29
Closed date
2008-09-19
Last modified date
2009-01-15

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PK77875

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
R61W PSY
UP
R61Z PSY
UP
R700 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":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK71342: J2C OBJECTS ARE NOT SERIALIZING CORRECTLY CAUSING J2CA0020E ERROR

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

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?