Fix (APAR): JR25285 Status: Fix Release: 6.0.2,6.0.1.4,6.0.1.3 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: JR25285 Byte size of APAR: 26149 Date: 2007-02-02 Abstract: A ServiceExpirationRuntimeException is thrown when the responding message has incorrect payload. If the provider responds to the request with the right correlation ID but wrong me Description/symptom of problem: JR25285 resolves the following problem: ERROR DESCRIPTION: A ServiceExpirationRuntimeException is thrown when the responding message has incorrect payload. If the provider responds to the request with the right correlation ID but wrong message payload (well formed but undefined or not expected), the SERE is thrown - there is no indication that anything has gone wrong. LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server 6.0.1.x users PROBLEM DESCRIPTION: A ServiceExpirationRuntimeException is thrown when the responding message has incorrect payload. If the provider responds to the request with the right correlation ID but wrong message payload (well formed but undefined or not expected), the SERE is thrown - there is no indication that anything has gone wrong. RECOMMENDATION: None When an error occurs in a response to a request using the JMS data binding, the exception is not propagated to the invoking component (for example, a BPEL invoke activity). The invoke will wait until there is a time out. PROBLEM CONCLUSION: Data Binding errors were treated as recoverable failures and the errors were not propagated. The JMS messages could be resubmitted if the data binding or message was fixed. APARs JR25018 and JR25285 provide new logic that propagates a ServiceRuntimeException to the invoke component (BPEL, etc) with a message DATABINDING_PARSING_ERROR. Refer to the technote JMS data binding errors does not get propagated to the invoking component at http://www-1.ibm.com/support/docview.wss?rs=2307&context= SSQH9M&dc=DB520&uid=swg21254452&loc=en_US&cs=utf-8&lang=en for more information. Directions to apply fix: Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system. Also download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Run the UpdateInstaller and follow the prompts. 4) Restart WebSphere Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server Additional Information: This iFix is related to the iFix for JR25018. JR25018 solves the problem related to a malformed JMS message reply, and this APAR JR25285 solves the problem related to an unexpected JMS message reply. In both cases, the fixes enable the caller to be notified of a data binding error.