PK73634: MIGRATING V6.1 CLUSTER TO V7.0 FAILS DUE TO CLASS INCOMPATIBILITY.

Fixes are available

APAR status

Closed as program error.

Error description

When trying to upgrade a working WebSphere Application Server
V6.1 cluster to a WebSphere Application Server V7.0 cluster
there is a serialization version exception since some
classes have changed their structure between versions and can't
be serialized or deserialized correctly.

Local fix

no workaround. There is one class that need to be reverted to
its older version , which seems to solve the migration problem.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V7.0                                        *
****************************************************************
* PROBLEM DESCRIPTION: Live migration of SIP cluster from      *
*                      Network Deployment V6.1 to V7.0 has a   *
*                      replication exception  (when            *
*                      replication domain is defined).         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A class serialization exception (versioning) occurs during live
upgrade from 6.1 to 7.0

Problem conclusion

After examination of the problematic class (the one
which caused the serialization exception) it was reverted to be
identical to the one shipped with WebSphere Application Server
V6.
Now, that both versions have same class , there are no problems
in the serialization versions of this class.
To see if the problem exists, search the exception in the
SystemOut.log:java.io.InvalidClassException:
com.ibm.ws.sip.hamanagment.logicalname.impl.LogicalName; local
class incompatible: stream classdesc serialVersionUID = <more
errors here...>

The fix for this APAR is currently targeted for inclusion in
fixpack 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

can be bypassed if shutting down the replication domain and
doing a normal upgrade to the nodes. Then starting all nodes
in that replication domain. Problem doesn't appear if all nodes
in the replication domain have the same WebSphere version.

Comments

APAR Information

APAR number
PK73634
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
2008-10-12
Closed date
2008-11-04
Last modified date
2008-11-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

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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 October 2021

Tips

PK73634: MIGRATING V6.1 CLUSTER TO V7.0 FAILS DUE TO CLASS INCOMPATIBILITY.

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

Document Information

Share your feedback

Need support?