[
https://issues.apache.org/jira/browse/ODE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Boisvert updated ODE-578:
------------------------------
Description:
Currently, when a process is called and some error happens during processing,
the error is not communicated back to the client. Instead, all the client gets
is a timeout exception which can be confusing.
Here is an example:
2009-03-05 19:30:06,873 ERROR [org.apache.ode.axis2.ODEService] Timeout or
execution error when waiting for response to MEX {MyRoleMex#632 [Client
96038a45-1409-4bda-ab33-81fd29de4a48-3] calling
{http://www.intalio.com/bpms/workflow/ib4p_20051115}UIFWService.completeTask(...)}
java.util.concurrent.TimeoutException: Message exchange
org.apache.ode.bpel.engine.myrolemessageexchangeimpl$responsefut...@e8b20a
timed out when waiting for a response!
java.util.concurrent.TimeoutException: Message exchange
org.apache.ode.bpel.engine.myrolemessageexchangeimpl$responsefut...@e8b20a
timed out when waiting for a response!
at
org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture.get(MyRoleMessageExchangeImpl.java:241)
at
org.apache.ode.axis2.ODEService.onAxisMessageExchange(ODEService.java:152)
at
org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODEMessageReceiver.java:67)
at
org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODEMessageReceiver.java:50)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
The proposal is to report back to the client any error during processing of the
request (by default). This feature could be turned off for security reasons
since it may create a risk of information disclosure.
was:
Currently, when a process is called and some error happens during processing,
the error is not communicated back to the client. Instead, all the client gets
is a timeout exception which can be confusing.
A good example of this can be seen in ticket
http://support.intalio.com/deskpro//tech/tickets/ticketview.php?id=3412
2009-03-05 19:30:06,873 ERROR [org.apache.ode.axis2.ODEService] Timeout or
execution error when waiting for response to MEX {MyRoleMex#632 [Client
96038a45-1409-4bda-ab33-81fd29de4a48-3] calling
{http://www.intalio.com/bpms/workflow/ib4p_20051115}UIFWService.completeTask(...)}
java.util.concurrent.TimeoutException: Message exchange
org.apache.ode.bpel.engine.myrolemessageexchangeimpl$responsefut...@e8b20a
timed out when waiting for a response!
java.util.concurrent.TimeoutException: Message exchange
org.apache.ode.bpel.engine.myrolemessageexchangeimpl$responsefut...@e8b20a
timed out when waiting for a response!
at
org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture.get(MyRoleMessageExchangeImpl.java:241)
at
org.apache.ode.axis2.ODEService.onAxisMessageExchange(ODEService.java:152)
at
org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODEMessageReceiver.java:67)
at
org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODEMessageReceiver.java:50)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
The proposal is to report back to the client any error during processing of the
request (by default). This feature could be turned off for security reasons
since it may create a risk of information disclosure.
> Better error reporting for WS clients
> -------------------------------------
>
> Key: ODE-578
> URL: https://issues.apache.org/jira/browse/ODE-578
> Project: ODE
> Issue Type: Improvement
> Reporter: Alexis Midon
> Assignee: Alexis Midon
> Fix For: 1.3.1, 2.0
>
>
> Currently, when a process is called and some error happens during processing,
> the error is not communicated back to the client. Instead, all the client
> gets is a timeout exception which can be confusing.
> Here is an example:
> 2009-03-05 19:30:06,873 ERROR [org.apache.ode.axis2.ODEService] Timeout or
> execution error when waiting for response to MEX {MyRoleMex#632 [Client
> 96038a45-1409-4bda-ab33-81fd29de4a48-3] calling
> {http://www.intalio.com/bpms/workflow/ib4p_20051115}UIFWService.completeTask(...)}
> java.util.concurrent.TimeoutException: Message exchange
> org.apache.ode.bpel.engine.myrolemessageexchangeimpl$responsefut...@e8b20a
> timed out when waiting for a response!
> java.util.concurrent.TimeoutException: Message exchange
> org.apache.ode.bpel.engine.myrolemessageexchangeimpl$responsefut...@e8b20a
> timed out when waiting for a response!
> at
> org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture.get(MyRoleMessageExchangeImpl.java:241)
> at
> org.apache.ode.axis2.ODEService.onAxisMessageExchange(ODEService.java:152)
> at
> org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODEMessageReceiver.java:67)
> at
> org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODEMessageReceiver.java:50)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
> The proposal is to report back to the client any error during processing of
> the request (by default). This feature could be turned off for security
> reasons since it may create a risk of information disclosure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
