PM11279: DRS DOES NOT HAVE CODE TO SEND RENOUNCES ON THE OTHER CHANNEL

Fixes are available

APAR status

Closed as program error.

Error description

Data Replication Service (DRS) uses 2 channels to send messages
to other application servers. Almost all messages travel on one
channel and removes and renounces travel on the other.

HAManager guarantees message order delivery when messages travel
on one channel.

There is no guarantee when messages are flowing on the 2
channels. DRS allows consumers to indicate that remove messages
should flow on the same channel as other messages using JVM
custom properties or misc properties when they create their DRS
instance.

DRS does not have code to send renounces on the other channel
and because invalidations use renounce instead of remove they
are traveling on the other channel.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server using HTTP session replication       *
*                  using the client/server topology.           *
****************************************************************
* PROBLEM DESCRIPTION: An out of memory condition can occur    *
*                      when replicated session objects are     *
*                      not completely invalidated.             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In a client/server replication topology, replicated objects may
not be completely removed from all application servers in the
replication domain.  Overtime this could result in a build up
of stale replicated session objects and eventually lead to an
out of memory condition.

Problem conclusion

Data Replication Services (DRS) and HTTP session manager have
closed the gaps that lead to the replicated session objects
not being removed after invalidation.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.35 and 7.0.0.13.  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
PM11279
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-31
Closed date
2010-07-07
Last modified date
2010-07-07

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

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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM11279: DRS DOES NOT HAVE CODE TO SEND RENOUNCES ON THE OTHER CHANNEL

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

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?