PQ97022: LONG RUNNING PROCESSES WHICH USE SOAP OVER JMS FAIL WITH THE WSWS3269E: ERROR: DEFAULT TYPE MAPPING CANNOT BE MODIFIED

 Fixes are available

5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for AIX
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for HP-UX
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Linux
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for HP-UX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Solaris
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Windows
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Solaris
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Windows
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Solaris
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Windows
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Solaris
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Linux
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Solaris
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Windows
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Solaris
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for AIX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for AIX
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Linux
5.0.2.12: WebSphere Application Server 5.0.2 Cumulative Fix 12
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for HP-UX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for AIX
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Windows
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for HP-UX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for AIX
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for AIX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for HP-UX
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Linux
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for HP-UX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Solaris
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for AIX
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Windows
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Solaris
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Linux
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for HP-UX
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for AIX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Windows
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Solaris
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Windows
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for AIX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Linux
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for HP-UX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for AIX
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Windows
5.0.2.13: WebSphere Application Server 5.0.2 Cumulative Fix 13
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for HP-UX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for AIX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Windows
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Linux
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for HP-UX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for HP-UX
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Solaris
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for AIX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Linux
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Linux
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for HP-UX



APAR status
Closed as program error.

Error description
When you call an IBM Web Service that was generated with a
SOAP/JMS service and binding from a long running BPEL Business
Process in WBI-SF 5.1.1, it results in an error.

For services generated top-down, the error is:

[9/20/04 17:20:49:891 PDT] 2721bcf0 Engine A
com.ibm.bpe.engine.Engine BPEE0003E:  An error occurred during
the invocation of the activity implementation
'CreateLogibro'.com.ibm.bpe.invocation.InvocationException:
BPEP0207E:  Web Services Invocation Framework (WSIF) invocation
failed with exception org.apache.wsif.WSIFException:  WSWS3269E:
Error:  Default type mapping cannot be modified.  detected by
'com.ibm.bpe.invocation.WSIFServiceInvocationHandler'.
org.apache.wsif.WSIFException:  WSWS3269E:  Error:  Default type
mapping cannot be modified.


For services generated bottom up, the error is:

[9/23/04 13:07:35:677 PDT] 2ec57316 Engine        A
com.ibm.bpe.engine.Engine
BPEE0003E: An error occurred during the invocation of the
activity implementation
'Invoke'.com.ibm.bpe.invocation.InvocationException:
BPEP0207E: Web Services Invocation Framework (WSIF) invocation
failed with exception org.apache.wsif.WSIFException:
WebServicesFault getting response SOAP envelope; nested
exception is:
 org.xml.sax.SAXException: WSWS3368E: Error: The deserialization
event characters for (
) was unexpected in test.GetRoomResponseElement_Deser.

Message being parsed: <?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:addEntryResponse
xmlns:ns1="http://wsifservice.addressbook/"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding
/">
</ns1:addEntryResponse>

</SOAP-ENV:Body>
</SOAP-ENV:Envelope> detected by
'com.ibm.bpe.invocation.WSIFServiceInvocationHandler'.
org.apache.wsif.WSIFException: WebServicesFault getting response
SOAP
envelope; nested exception is:
 org.xml.sax.SAXException: WSWS3368E: Error: The deserialization
event
characters for (
) was unexpected in test.GetRoomResponseElement_Deser. Message
being
parsed: <?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:addEntryResponse
xmlns:ns1="http://wsifservice.addressbook/"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding
/">
</ns1:addEntryResponse>

</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Evidently these errors have been addresses in an (unavailable?)
patch for botp defect 231548, but this patch still results in an
error when calling the service.  When the patch is applied, the
attempt to call the service results in the error:

9/24/04 9:12:40:610 CEST] 4bad669d *             d
org.apache.wsif.*
EXCEPTION
[9/24/04 9:12:40:610 CEST] 4bad669d *             d
org.apache.wsif.*
The following exception was logged
                                 javax.xml.rpc.JAXRPCException:
WSWS3269E: Error: Default type mapping cannot be modified.
   at
com.ibm.ws.webservices.engine.encoding.DefaultTypeMappingImpl.re
gister(D
efaultTypeMappingImpl.java:655)
   at
com.ibm.ws.webservices.wsif.providers.soap.WSIFOperation_SOAP.re
gisterDe
faultTypeMappings(WSIFOperation_SOAP.java:2698)
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Users of WSIF. Users of WebSphere Business   *
*                 Integration Server Foundation Process        *
*                 Choreographer.                               *
****************************************************************
* PROBLEM DESCRIPTION: The problem occurs in an asynchronous   *
*                      WSIF operation, using the SOAP over     *
*                      JMS protocol.                           *
*                                                              *
*                      When the response message is received   *
*                      and the method processAsyncResponse()   *
*                      is called on a WSIFOperation object,    *
*                      the error will occur. The               *
*                      asynchronous response will not be       *
*                      processed.                              *
*                                                              *
*                      Long running BPEL processes which       *
*                      invoke Web Service partners using       *
*                      the SOAP over JMS protocol will         *
*                      call the processAsyncResponse()         *
*                      method upon receiving the               *
*                      response from the partner Web           *
*                      Service.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When processAsyncResponse() is called, either explicitly by a
WSIF client or implicitly in a long running BPEL process, the
error will occur:

org.apache.wsif.WSIFException:  WSWS3269E:  Error:  Default type
mapping cannot be modified.

This occurs in a long running BPEL process if a Web Service
partner invoke is used, and the protocol is SOAP over JMS.

This occurs in a standalone WSIF client if the Web Service
is invoked using the SOAP over JMS protocol, and the WSIF
client is using asynchronous invokation. This means the WSIF
client calls either executeRequestResponseAsync() method on
the WSIFOperation object.

The error only occurs if the standalone WSIF
client is running in either the WebSphere EJB container (ie in
an Enterprise Bean), or the WebSphere Servlet container (ie in
a Servlet or JSP). The error does not occur if
the WSIF client is running in the WebSphere Client container
(ie from launchClient).
Problem conclusion
A code fix has been made in WSIF which enables asynchronous
SOAP over JMS responses to be processed.

The fix is targetted to be included in WebSphere Application
Server 5.0.2 cumulative fix 10 and WebSphere Application Server
5.1.1 cumulative fix 3.

Please refer to the Recommended Updates page for delivery dates:
 
http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP
&uid=swg27004980
Temporary fix Comments
APAR information
APAR number PQ97022
Reported component name WBISF 510
Reported component ID 5724H7400
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-11-10
Closed date 2005-01-13
Last modified date 2005-01-13

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WSIF          

Publications Referenced

Fix information
Fixed component name WAS BASE 5.0
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


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ97022
IBM Group: Software Group
Modified date: Jan 13, 2005