JMS Transport incorrectly manage AxisFaults thrown from the endpoint
--------------------------------------------------------------------
Key: AXIS2-1767
URL: http://issues.apache.org/jira/browse/AXIS2-1767
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.1
Reporter: Juan Vaccarezza
Steps:
*Create a wsdl document with a fault declaratrion
*Generate java code for both client and service from the wsdl file
*Fill a generated skeleton method with a code sinppet that just throws the
declared exception.
*Configure AXIS to use JMS transport (uncomment it in axis2.xml)
*In the generated tests, point the generated stub to a correct jms address
*Deploy the service
*Start axis
*Run tests
Bug:
The exception will be shown in the axis server console.
The JMSReceiver ignores the fault just logs it and no action is taken, no
response is returned to the client.
The junit test will get sutcked for 30 secs (the default jms transport timeout)
and then fail because no response has been sent from the server.
The same scenario works as expected using the HTTP transport.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
