APAR status
Closed as program error.
Error description
Currently, as we already know, the web services engine does not
support the ability to save unsendable SOAP/JMS messages to a
temporary queue. These request messages are unsendable because
the specified target service does not exist. The engine just
logs a message, propagates an exception back to client, and
discards the message.
Local fix
"[J]ust have the SOAP/JMS MDB cause a transaction rollback in
the event of a failure to process a one-way message, leaving
the request message on the inbound queue. This will typically
cause the message to be re-read (and likely fail) another four
times due to the retry count, but at this point the messaging
provider can do-the-right-thing with the message, which in our
case will be to move the message to the exception destination.
... Allowing the messaging provider to handle the error results
in the original message being moved to the exception
destination as a result of a messaging error. The original
message will still contain certain bits of messaging-level
information on it that may be useful in problem determination
that will have been lost if the MDB sends a copy of the
message itself."
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of web *
* services *
****************************************************************
* PROBLEM DESCRIPTION: An unsendable SOAP/JMS message to a *
* non-existent queue will now result in *
* a transaction rollback. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An unsendable SOAP/JMS message to a non-existent queue will
now result in a transaction rollback. This rollback is
actually done by the EJB container, not the web services
engine, which just throws a RuntimeException.
The rollback allows for the messaging server (like MQ server)
to place the unsendable message to a sort-of "dead-letter"
queue, normally used for auditing purposes.
Problem conclusion
Web services engine throws a RuntimeException
from JMSListenerMDB class.
The fix for this APAR is currently targeted for inclusion
in cumulative fix 5.1.1.12, 6.0.2.15, and 6.1.0.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 |
PK27306 |
Reported component name |
WEBSPHERE BASE |
Reported component ID |
5630A3600 |
Reported release |
10A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2006-06-28 |
Closed date |
2006-09-18 |
Last modified date |
2007-02-27 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WEBSPHERE BASE |
Fixed component ID |
5630A3600 |
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|