PK79012: WITH THE 6.0.2.31 CORE GROUP PROTOCOL AND UNDER CERTAIN TIMING CONDITIONS, SEAMLESS FAILOVER IS NOT MAINTAINED.

Fixes are available

APAR status

Closed as program error.

Error description

Under certain timing conditions, the 6.0.2.31 core group
protocol (delivered with APAR PK64003) is not honored.  This
results in state not being persistently available during
core group bridge stops/starts.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of core group bridge in IBM       *
*                  WebSphere Application Server                *
****************************************************************
* PROBLEM DESCRIPTION: When using the                          *
*                      "IBM_CS_HAM_PROTOCOL_VERSION=6.0.2.31"  *
*                      core group protocol, state              *
*                      information is not always persisted     *
*                      during bridge failover.                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The "IBM_CS_HAM_PROTOCOL_VERSION=6.0.2.31" core group protocol
was added via PK64003 to enable core groups to maintain state
information during bridge failover.  However, the transparent
bridge failover behavior was not being honored during all
bridge recovery scenarios.  This may result in 404s for
WebSphere Virtual Enterprise's On-Demand Router or other
problems when state information from non-local core groups is
temporarily lost during bridge failover.

The following exception may also occur.

[3/30/09 23:45:25:103 CDT] 0000001a JobsProcessor W
DCSV0002W: DCS Stack <null> at Member <null>: An unexpected
programming state has occurred. Internal details:  "Failed to
process job"
{ThreadName=ThreadManager.JobsProcessorThread.ApplicationThread.
0, Job= {CCVersion=((7292:0.170.49.25.41:9353).1.0),
failedMembers=[]} } . The exception is
java.util.ConcurrentModificationException
 at
java.util.HashMap$HashIterator.nextEntry(HashMap.java(Compiled
Code))
 at java.util.HashMap$EntryIterator.next(HashMap.java(Compiled
Code))
 at
com.ibm.ws.cgbridge.core.impl.SubjectPostCache.getSubjectPostCac
heSize(SubjectPostCache.java(Compiled Code))
 at
com.ibm.ws.cgbridge.core.impl.SynchronizedCoreGroups.notifyListe
ners(SynchronizedCoreGroups.java(Inlined Compiled Code))
 at
com.ibm.ws.cgbridge.core.impl.SynchronizedCoreGroups.removeCoreG
roup(SynchronizedCoreGroups.java(Compiled Code))
 at
com.ibm.ws.cgbridge.core.impl.InterCGBridgePMGEvents.mayUnstabil
ize(InterCGBridgePMGEvents.java(Compiled Code))
 at
com.ibm.ws.hamanager.partitionedmanager.PartitionedManagerGroupI
mpl.viewAboutToChange(PartitionedManagerGroupImpl.java(Compiled
Code))
 at
com.ibm.ws.hamanager.impl.ViewSynchronousHAGroup.dataStackViewAb
outToChange(ViewSynchronousHAGroup.java:516)
 at
com.ibm.ws.hamanager.datastack.DataStackImpl.handleViewChangeEve
nt(DataStackImpl.java:595)
 at
com.ibm.ws.dcs.common.impl.DCSStackImpl$CCJob.process(DCSStackIm
pl.java:1369)
 at
com.ibm.ws.dcs.vri.common.JobsProcessorThread.executeJob(JobsPro
cessorThread.java(Inlined Compiled Code))
 at
com.ibm.ws.dcs.vri.common.JobsProcessorThread.run(JobsProcessorT
hread.java(Compiled Code))

Problem conclusion

This problem was resolved by switching the core group bridge
to use its own thread pool.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.37, 6.1.0.27, and 7.0.0.5.  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
PK79012
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-20
Closed date
2009-04-09
Last modified date
2009-04-09

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
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":"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 December 2021

Tips

PK79012: WITH THE 6.0.2.31 CORE GROUP PROTOCOL AND UNDER CERTAIN TIMING CONDITIONS, SEAMLESS FAILOVER IS NOT MAINTAINED.

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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?