APAR status
Closed as program error.
Error description
WMB Execution Groups fail to start with switching MB to use Java 1.5
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Message Broker * * using SCADA libraries. * **************************************************************** * PROBLEM DESCRIPTION: When SCADA libraries are loaded along * * with JAVA 1.5 the Broker will * * start reporting that the Execution * * Groups are not responding (BIP2080E). * **************************************************************** * RECOMMENDATION: * **************************************************************** A user will receive a BIP2080E messages when loading SCADA libraries if the Broker is using Java 1.5. The problem does not occur if Java 1.5 is not being used.
Problem conclusion
WebSphere Message Broker has been modified so that when loading SCADA libraries and using Java 1.5 the execution groups do not hang and report a BIP2080E message.
Temporary fix
Comments
APAR Information
APAR number
IZ25601
Reported component name
MSSG BROKER AIX
Reported component ID
5724J0501
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-06-25
Closed date
2008-06-30
Last modified date
2009-06-12
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
MSSG BROKER AIX
Fixed component ID
5724J0501
Applicable component levels
R100 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSKM8N","label":"WebSphere Message Broker"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
12 June 2009