PK87188: Running server cannot dynamically become default messaging provider bootstrap server

Fixes are available

APAR status

Closed as program error.

Error description

If SIB service is enabled on a server, the
InboundBasicMessaging and InboundSecureMessaging transport
chains on these servers are not started automatically when a
bus is added to the cell.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider in  *
*                  WebSphere Application Server v7.0           *
****************************************************************
* PROBLEM DESCRIPTION: When a bus is added to a cell which     *
*                      previously did not have a bus and       *
*                      there are servers running in the cell   *
*                      that have SIB service and dynamic       *
*                      config enabled it is not possible for   *
*                      clients to use these servers as         *
*                      bootstrap servers until they are        *
*                      restarted.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This problem occurs because the InboundBasicMessaging and
InboundSecureMessaging transport chains on these servers are
not started automatically when a bus is added to the cell.

Conversely the InboundBasicMessaging and
InboundSecureMessaging transport chains on these servers are
not stopped automatically when all the buses are removed from
the cell.

Also a CWSIC2001I message is output stating that messaging
connections are being accepted, when this is not true because
the InboundBasicMessaging and InboundSecureMessaging transport
chains are not started.

Problem conclusion

The fix for this APAR dynamically starts and stops chains when
a bus is added to, or deleted from, a cell. A CWSIC2001I log
entry is only output the first time any inbound messaging
chains are started.

This APAR is targeted for WebSphere Application Server
fix pack 7.0.0.5.

Temporary fix

Comments

APAR Information

APAR number
PK87188
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-22
Closed date
2009-06-29
Last modified date
2009-06-29

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
PLAT MSG COM
Fixed component ID
620800101

Applicable component levels

R300 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:
24 October 2021

Tips

PK87188: Running server cannot dynamically become default messaging provider bootstrap server

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

R300 PSY

Document Information

Share your feedback

Need support?