APAR status |
Closed as program error.
| Error description
This defect is for the work required on WS/distributed to
enhance certain container classes that are passed by value
between client and server, so they will correctly interoperate
with WebSphere/390.
SessionHandle
EntityHandle
EJBMetaData
FinderEnumeration
EntityHomeHandle
RemoteIterator
possibly others TBD Local fixProblem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users of *
* getEJBMetaData, getHandle, getHomeHandle, *
* and finders (Enumeration returning or *
* Collection returning). *
****************************************************************
* PROBLEM DESCRIPTION: Serialization errors occurred when *
* calling getEJBMetaData on homes. *
* Also Serialization errors occur *
* while calling getHandle on *
* EJBs. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
There were basically two reasons this failed.
One was that the Container didn't code the serializable classes
which had problems according to the java spec. This resulted in
a variety of symptoms, such as mis-matched serialization UIDs,
underlying bridge exceptions, and invalid chunk size exceptions.
.
Once the container team fixed their code, it was discovered
that the jdk orb had problems as well. These problems are fixed
in 3.5.6 and 4.0.3 in the jdk's which shipped with those ptfs. Problem conclusion
The implementations for Handles, HomeHandles, FinderEnumerators,
FinderEnumerations, and EJBMetaData were changed to conform to
the java serialization guidelines. This was done for 3.5.6
and 4.0.3. zSeries also did the same.
Defects were: 113380 113380.1 113380.2 113380.4 110799 Temporary fixComments
APAR information | APAR number | PQ57731 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-02-11 | Closed date | 2002-03-19 | Last modified date | 2002-03-19 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|