[jira] Resolved: (AXIS2-1767) JMS Transport incorrectly manage AxisFaults thrown from the endpoint

["Sanka Samaranayake (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AXIS2-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sanka Samaranayake resolved AXIS2-1767.
---------------------------------------

    Resolution: Fixed


Applied the changes suggested. (Committed revision 522441)

Thanks Juan .. !!

--Sanka


> JMS Transport incorrectly manage AxisFaults thrown from the endpoint
> --------------------------------------------------------------------
>
>                 Key: AXIS2-1767
>                 URL: https://issues.apache.org/jira/browse/AXIS2-1767
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Juan Vaccarezza
>         Assigned To: Sanka Samaranayake
>
> 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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org