PI38265: WS-NOTIFICATION BROKER MAY FAIL TO DELIVER NOTIFICATIONS DUE TO ILLEGALSTATEEXCEPTION ISSUED BY THE IBM STAX PARSER.

Fixes are available

APAR status

Closed as program error.

Error description

The WS-Notification Broker application's web service client
is unable to parse XML due to an invalid character and an
illegal state exception occurs.
The exceptions occur in the following order:

StAXBuilder   1 org.apache.axiom.om.impl.builder.StAXBuilder
parserNext Rethrowing stored exception
javax.xml.stream.XMLStreamException: An invalid XML character
(Unicode: 0xffffffff) was found in the element content of the
document.javax.xml.stream.XMLStreamException: An invalid XML
character (Unicode: 0xffffffff) was found in the element
content of the document.
at
com.ibm.xml.xlxp2.api.stax.msg.StAXMessageProvider.throwWrappedX
MLStreamException(StAXMessageProvider.java:76)
at
com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl.produceFatalError
Event(XMLStreamReaderImpl.java:2013)
at
com.ibm.xml.xlxp2.api.jaxb.JAXBXMLStreamReader.produceFatalError
Event(JAXBXMLStreamReader.java:316)
at
com.ibm.xml.xlxp2.scan.DocumentScanner.reportFatalError(Document
Scanner.java:4886)
at
com.ibm.xml.xlxp2.scan.DocumentScanner.reportFatalError(Document
Scanner.java:1213)
...

CWSJN5030E: An internal error occurred: Unable to notify a
consumer at endpoint reference Address[[

https://company.hostname.com/Notifications/NotificationSubscript
ionService.svc]],
ReferenceParams[] due to
javax.xml.ws.WebServiceException:
java.lang.IllegalStateException: The current state is an
invalid text state..
at
com.ibm.ws.sib.wsn.webservices.impl.outbound.dispatch.OutboundCl
ientImpl.notifyConsumer(OutboundClientImpl.java:184)
at
com.ibm.ws.sib.wsn.impl.ProducerRoleImpl.deliverMessages(Produce
rRoleImpl.java:345)
at
com.ibm.ws.sib.wsn.msg.impl.SubscriptionImpl.consumeMessages(Sub
scriptionImpl.java:1433)
...
Caused by: javax.xml.ws.WebServiceException:
java.lang.IllegalStateException: The current state is an
invalid text state.
at
org.apache.axis2.jaxws.ExceptionFactory.createWebServiceExceptio
n(ExceptionFactory.java:175)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:70)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:128)
...
Caused by: java.lang.IllegalStateException: The current state
is an invalid text state.
at
com.ibm.xml.xlxp2.api.stax.msg.StAXMessageProvider.throwIllegalS
tateException(StAXMessageProvider.java:49)
at
com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl.getText(XMLStream
ReaderImpl.java:1260)
at
com.ibm.xml.xlxp2.api.stax.XMLInputFactoryImpl$XMLStreamReaderPr
oxyImpl.getText(XMLInputFactoryImpl.java:376)
at
com.ibm.xml.xlxp2.api.wssec.WSSXMLInputFactory$WSSStreamReaderPr
oxy.getText(WSSXMLInputFactory.java:55)
...

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server users of       *
*                  WS-Notification Broker                      *
****************************************************************
* PROBLEM DESCRIPTION: WS-Notification is unable to deliver    *
*                      messages containing certain             *
*                      characters due to a                     *
*                      javax.xml.stream.XMLStreamException     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The WS-Notification broker's outbound client that dispatches
the Notifications to the consumers made use of internal helper
classes to construct the SOAP Elements used to build the SOAP
Message.  The complex manner in which the helper classes were
used exceeded their capabilities and resulted in corruption of
the XML stream.

Problem conclusion

The WS-Notification broker's outbound client that dispatches
the Notifications to the consumers modified how it constructs
the outbound SOAP Message for the Notification message.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.39, 8.0.0.11 and 8.5.5.7.  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
PI38265
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-04-01
Closed date
2015-05-26
Last modified date
2015-05-26

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

R700 PSY
UP
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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:
28 April 2022

Tips

PI38265: WS-NOTIFICATION BROKER MAY FAIL TO DELIVER NOTIFICATIONS DUE TO ILLEGALSTATEEXCEPTION ISSUED BY THE IBM STAX PARSER.

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

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?