PK94866: WHEN USING SOAP/JMS AS A ONE WAY INTERFACE, THE WEB SERVICES ENGINE DOES NOT PROPAGATE EXCEPTIONS.

Fixes are available

APAR status

Closed as program error.

Error description

When using SOAP/JMS as a one way interface, the Web Services
Engine is invoked as part of the onMessage() method to process
the SOAP message, during which it throws a SAXParseException due
to a missing end tag in the XML.  FFDC records are generated
during the processing of the exception, and a WebServiceFault
exception is created.  The suspended transaction is resumed and
the WSE returns to the onMessage() method and no exception is
encountered to the onMessage().

SAXParseException:

org.xml.sax.SAXParseException: The element type "soapenv:Body"
does not match the expected end-tag "</q0:invokeMed>".
org.xml.sax.SAXParseException: The element type "soapenv:Body"
does not match the expected end-tag "</q0:invokeMed>".
at
com.ibm.xml.xlxp.api.sax.impl.SAX2ParserBase.reportFatalError(SA
X2Parser Base.java:528)
at
com.ibm.xml.xlxp.api.was.WSXMLReader$WSScannerHelper.produceFata
lErrorEvent(WSXMLReader.java:469)

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  All developers of SOAP/JMS JAX-RPC          *
*                  applications for the IBM WebSphere          *
*                  Application Server                          *
****************************************************************
* PROBLEM DESCRIPTION: Exceptions that occur within a one-way  *
*                      service request are not propagated      *
*                      back to the EJB container.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Exceptions that occur within a one-way service request are not
propagated back to the EJB container for rollback and error
recovery.

Problem conclusion

The JMS web services code was changed to propagate exceptions
that occur in the service implementation back to the EJB
container.

The new JVM property was created to enable this new behavior:
com.ibm.ws.webservices.engine.transport.jms.propagateOneWaySyste
mExceptions

This JVM property must be set to true to enable this new
behavior.

The default value is false.

Refer to the Information Center article "Java virtual machine
custom properties" for instructions on how to set a custom
property on the JVM.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.39, 6.1.0.29 and 7.0.0.9.  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
PK94866
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-27
Closed date
2009-10-04
Last modified date
2009-10-04

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK94866: WHEN USING SOAP/JMS AS A ONE WAY INTERFACE, THE WEB SERVICES ENGINE DOES NOT PROPAGATE EXCEPTIONS.

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

Document Information

Share your feedback

Need support?