PK00560: ALLEVIATE WSIF INTEROPERABILITY WITH SOAP CLIENTS RESTRICTIONS | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description The following restrictions apply to the use of WSIF SOAP client invocations: * The mixing of WSIF SOAP client invocations with J2EE Web Service client invocations in the same client environment is not supported. * The use of WSIF SOAP client invocations local to a WebSphere Application Server can cause problems in J2EE Web Services deployed on the same Application Server. * The use of a Web Services Gateway deployed on a WebSphere Application Server can cause problems inn J2EE Web Services deployed on the same Application Server. An attempt to invoke a J2EE over JMS web service after any WSIF SOAP over HTTP or SOAP over JMS client invocation will return the following error and the request will not be sent: TRAS0014I: The following exception was logged java.lang.NullPointerException at com.ibm.ws.webservices .wsif.providers.soap .WSIFJmsSender._invoke(WSIFJmsSender.java:126) Any WSIF SOAP over HTTP or SOAP over JMS client invocation (including implicit WSIF client invocation via the Web Services Gateway) can cause various problems relating to Security, Internationalization, Request Metrics, Performance Monitoring and Transactions in J2EE Web Services deployed on the same Application Server.Local fix Problem summary **************************************************************** * USERS AFFECTED: Users of Business Processes modelled using * * the Business Process Execution Language. * **************************************************************** * PROBLEM DESCRIPTION: The following restrictions apply to the * * use of WSIF SOAP client invocations: * * * * The mixing of WSIF SOAP client * * invocations with J2EE Web Service * * client invocations in the same * * client environment is not supported. * * * * The use of WSIF SOAP client * * invocations local to a * * WebSphere Application Server can * * cause problems in J2EE Web * * Services deployed on the same * * Application Server. * * * * The use of a Web Services Gateway * * deployed on a WebSphere Application * * Server can cause problems in J2EE Web * * Services deployed on the same * * Application Server. * * * * An attempt to invoke a J2EE over JMS * * web service after any WSIF SOAP over * * HTTP or SOAP over JMS client * * invocation will return the following * * error and the request will not be * * sent: * * * * TRAS0014I: The following exception * * was logged * * java.lang.NullPointerException at * * com.ibm.ws.webservices * * .wsif.providers.soap * * .WSIFJmsSender._invoke * * (WSIFJmsSender.java:126) * * * * Any WSIF SOAP over HTTP or SOAP over * * JMS client invocation * * (including implicit WSIF client * * invocation via the Web * * Services Gateway) can cause various * * problems relating to * * Security, Internationalization, * * Request Metrics, Performance * * Monitoring and Transactions in J2EE * * Web Services deployed on * * the same Application Server. * **************************************************************** * RECOMMENDATION: * **************************************************************** To support SOAP over JMS, WSIF registers its own Transport implementation class with the Web Services Engine. The way in which this registration is done is that for the "jms" protocol, all Web Service services and clients in an application server will use the WSIF Transport (the WSIFJmsSender class). Any attempt to get a Web Service engine configuration will return the WSIF web service engine configuration. If there is therefore a JAX-RPC Web Services client which wishes to use the Web Service engine JMS Transport, and it is invoked after a WSIF client has sent a SOAP over JMS request, then this Web Services client will use the WSIF JMS Transport. Because the Web Service engine has not set up WSIF-specific objects, the WSIF Transport will fail with the following error: TRAS0014I: The following exception was logged java.lang.NullPointerException at com.ibm.ws.webservices .wsif.providers.soap .WSIFJmsSender._invoke (WSIFJmsSender.java:126) The limitation also occurs for SOAP over JMS Web Services. If a Web Service exposed on an application server, using the SOAP over JMS protocol, has not been invoked, then when a WSIF client invokes a Web Service using SOAP over JMS, the WSIF Web Service engine configuration will be registered for all users in the application server. Therefore, if a JAX-RPC client invokes the SOAP over JMS Web Service, a JMS message arrives on the Web Service queue. An MDB listener bean will be activated to process the message. This will attempt to locate the Web Service to process the message. However, because the Web Service engine configuration is now the WSIF engine configuration, all information regarding SOAP over JMS Web Service mappings is lost. The JAX-RPC client will see a message from the application server saying that the target service cannot be located.Problem conclusion WSIF has been changed to register its JMS Transport for only WSIF clients, without impacting the rest of the application server. The fix is targetted for WebSphere Application Server 5.1.1 cumulative fix 4. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 10W
Software edition:
Reference #: PK00560
IBM Group: Software Group
Modified date: Mar 10, 2005
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.