PQ94270: GETTING EXCEPTION WHILE USING BPEL TO ACCESS SOAP/JMS WEBSERVICES.

 Fixes are available

5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
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.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux



APAR status
Closed as program error.

Error description
The process is defined to be "short-running"
this means that JMS sends are made within the context of a
single transaction.
Customer is getting the following exception using the
Short-Running process.

com.ibm.ws.webservices.engine.enterprise  WSWS3243I: Info:
Mapping
Exception to WebServicesFault.
[8/23/04 15:23:30:021 EDT] 158edb20 enterprise    I
com.ibm.ws.webservices.engine.enterprise  TRAS0014I: The
following
exception was logged WebServicesFault
 faultCode: Server.generalException
 faultString: org.apache.wsif.WSIFException: Receive timed out
on JMS
queue
queue://WAS_localhost_server1/AMQ.10000001?persistence=1,
timeout 10000
 faultActor: null
 faultDetail:

org.apache.wsif.WSIFException: Receive timed out on JMS queue
queue://WAS_localhost_server1/AMQ.10000001?persistence=1,
timeout 10000
 at
com.ibm.ws.webservices.wsif.providers.soap.WSIFJmsSender._invoke
(WSIFJms
Sender.java:180)
 at
com.ibm.ws.webservices.wsif.providers.soap.WSIFJmsSender.invoke(
WSIFJmsS
ender.java:99)
 at
com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHa
ndlerWra
pper.java:212)
 at
com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServic
esEngine
.java:255)
 at
com.ibm.ws.webservices.engine.client.Connection.invokeEngine(Con
nection.
java:685)


Keyword :  WebSphere , BPEL, WebServices
Local fix
Already provided a test fix.
Problem summary
****************************************************************
* USERS AFFECTED: Users of WebSphere Studio Application        *
*                 Developer Integration Edition Business       *
*                 Processes, invoking a Web Service which      *
*                 uses SOAP over JMS, in a short running       *
*                 business process (BPEL flow).                *
*                 Users of WSIF, if the WSIF client invokes    *
*                 a synchronous (two way) SOAP/JMS web         *
*                 service from inside a WebSphere Application  *
*                 Server, if the WSIF invocation happens       *
*                 under a Local or Global WebSphere            *
*                 transaction.                                 *
****************************************************************
* PROBLEM DESCRIPTION: When invoking a synchronous SOAP/JMS    *
*                      web service from WSIF under a           *
*                      transaction, the process will hang      *
*                      for 10 seconds and then a timeout       *
*                      error will be returned to the process   *
*                      client. The SOAP message will not be    *
*                      sent to the web service.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The error occurs if the WSIF client is WebSphere Process
Choreographer, or the WSIF client is an Enterprise Bean with
container-managed transactions defined on the bean method. In
a synchronous SOAP JMS invocation, WSIF will put the request
message onto a queue, then wait to receive the response. This
wait will timeout, so after 10 seconds WSIF will return the
following exception:

org.apache.wsif.WSIFException: Receive timed out on JMS queue
 queue://WAS_localhost_server1/AMQ.10000001?persistence=1,
 timeout 10000
at com.ibm.ws.webservices.wsif.providers.soap.WSIFJmsSender.
 _invoke(WSIFJmsSender.java:180)
at com.ibm.ws.webservices.wsif.providers.soap.WSIFJmsSender.
 invoke(WSIFJmsSender.java:99)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.
 invoke(PivotHandlerWrapper.java:212)
at com.ibm.ws.webservices.engine.WebServicesEngine.
 invoke(WebServicesEngine.java:255)
at com.ibm.ws.webservices.engine.client.Connection.
 invokeEngine(Connection.java:685)
at com.ibm.ws.webservices.engine.client.Connection.
 invoke(Connection.java:611)
at com.ibm.ws.webservices.engine.client.Connection.
 invoke(Connection.java:441)
at com.ibm.ws.webservices.engine.client.Call.
 invoke(Call.java:1337)
at com.ibm.ws.webservices.wsif.providers.soap.
 WSIFOperation_SOAP.invokeSOAPDocStyle
 (WSIFOperation_SOAP.java:2114)
at com.ibm.ws.webservices.wsif.providers.soap.
 WSIFOperation_SOAP.invokeRequestResponseOperation
 (WSIFOperation_SOAP.java:1632)
at com.ibm.ws.webservices.wsif.providers.soap.
 WSIFOperation_SOAP.executeRequestResponseOperation
 (WSIFOperation_SOAP.java:1053)

If the WSIF client is WebSphere Process Choreographer, the
following exception will be reported to the user:

[27/08/04 14:26:36:158 BST]  25f92fe BpelEngine    A
com.ibm.bpe.engine.BpelEngine
BPEE0071E: A two-way request for port type 'ProcessPortType'
and operation 'InputOperation' was accepted by activity
'Receive'. The process ended before a corresponding reply
activity was executed.com.ibm.bpe.api.RuntimeFaultException:
BPEE0003E: An error occurred during the invocation of the
activity implementation 'Service'.
com.ibm.bpe.invocation.InvocationException: BPEP0207E: Web
Services Invocation Framework (WSIF) invocation failed with
exception org.apache.wsif.WSIFException: Receive timed out
on JMS queue queue://WAS_localhost_server1/AMQ.10000001?
persistence=1, timeout 10000 detected by
'com.ibm.bpe.invocation.WSIFServiceInvocationHandler'.

This occurs because the JMS put is not done until the current
transaction is committed. This has not happened when WSIF
waits on a queue to receive the response. The web service
does not see the request message and does not reply.
Therefore WSIF times out.
Problem conclusion
The WSIF SOAP/JMS support has been changed to suspend any
active transaction before putting a JMS message on a queue,
and then resume the transaction after the put is done. The
message is therefore sent and the web service responds.

It is recommended that customers encountering this problem
should install WebSphere Application Server V5.1.1 with
cumulative fix 2, WebSphere Application Server V5.0.2 with
cumulative fix 9.
Temporary fix Comments
APAR information
APAR number PQ94270
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 10W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-09-15
Closed date 2004-11-05
Last modified date 2004-11-05

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

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: 10W
Software edition:
Reference #: PQ94270
IBM Group: Software Group
Modified date: Nov 5, 2004