Fixes are available
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
APAR status
Closed as program error.
Error description
If you create a WSN Service and a permanent topic namespace, and create a subscription for a topic using the permanent topic namespace, when the server is stopped and restarted, the first notify message that is sent (which is a match for the subscribed topic and topic namespace) we see an exception in the logs: ~ "InternalExcep E com.ibm.ws.webservices.engine.InternalException <init> WSWS3227E: Error: Exception: The namespace prefix "pcr" was not declared." ~ (note: "pcr" is the name of the permanent topic namespace). ~ The subscription shows it is in error status but when it re-tries to deliver the message (after the timeout interval) the message is delivered successfully without any errors or exceptions. All subsequent notify messages are successful as well. The problem will re-appear when the server is re-started - the first notify message sent after the restart will have the above exception.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server users of * * WS-Notification using WS-Addressing EPRs * * that contain wsa:Metadata elements. * **************************************************************** * PROBLEM DESCRIPTION: WSWS3227E occured when * * WS-Notification used a consumer * * EndpointReference containing * * wsa:Metadata * **************************************************************** * RECOMMENDATION: * **************************************************************** When an EPR contained in an inbound request is deserialized from a SOAP Element, the SOAPElements representing parts of the EPR are detached from their parents. The WS-Addressing Metadata however still uses its original SOAPElement for holding its state data. If this SOAPElement contains QNames that rely on namespace declarations that exist higher up the SOAPElement hierarchy then these are no longer available to it. This results in the persisted form of the Metadata containing a QName prefix and LocalName pair with no reference to the namespace. When the persisted data is deserialized and then used this results in the following error: com.ibm.ws.webservices.engine.InternalException <init> WSWS3227E: Error: Exception: org.xml.sax.SAXParseException: The namespace prefix "test" was not declared. at com.ibm.xml.xlxp2.api.sax.impl.SAX2ParserBase.reportFatalError(S AX2ParserBase.java:566) at com.ibm.xml.xlxp2.api.sax.impl.SAX2DocumentScanner.produceFatalE rrorEvent(SAX2DocumentScanner.java:157) at ...
Problem conclusion
The code was modified to ensure that namespace declarations referenced by SOAPElements in the Metadata were declared in the SOAPElement of the Metadata itself before it is detached from its parent SOAPElement. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.1. 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
PM86853
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-04-11
Closed date
2013-07-02
Last modified date
2013-07-02
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
R850 PSY
UP
Document Information
Modified date:
12 January 2022