A fix is available
APAR status
Closed as program error.
Error description
XMLNS parser does not reset after trying to parse bad xml.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Message Broker that * * use the XMLNS parser. * **************************************************************** * PROBLEM DESCRIPTION: The XMLNS parser continues to fail * * with a 5004/5009 message after parsing * * a bad namespace xml message even * * the subsequent messages are valid. * **************************************************************** * RECOMMENDATION: * **************************************************************** If an XML message that has an invalid namespace is parsed, the XMLNS parser will correctly throw a BIP5004/BIP5009 error. If the next message is a valid message , the XMLNS parser will still throw a BIP5004/BIP5099 error even though the message is good.
Problem conclusion
The XMLNS parser was not reset after parsing a bad xml message causing subsequent messages to fail. The change was to reset the parser.
Temporary fix
Comments
APAR Information
APAR number
IZ04441
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
2007-09-07
Closed date
2007-12-10
Last modified date
2007-12-10
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:
10 December 2007