You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Hans G Knudsen (JIRA)" <ji...@apache.org> on 2007/12/18 13:49:44 UTC
[jira] Created: (SANDESHA2-130) Exceptions in Axis stack not
reported to client
Exceptions in Axis stack not reported to client
-----------------------------------------------
Key: SANDESHA2-130
URL: https://issues.apache.org/jira/browse/SANDESHA2-130
Project: Sandesha2
Issue Type: Bug
Affects Versions: 1.3
Environment: Axis2/Rampart/Sandesha2 v 1.3
Reporter: Hans G Knudsen
Hi!
If errors occurs in the Axis stack after Sandesha has taken over handling - the exception is not handed back to the calling client.
Eg. if an error occur in Rampart trying to do the outgoing security handling.
Testcase:
- misspell
<ramp:passwordCallbackClass>wrong.class.Name</ramp:passwordCallbackClass>
Sandesha does not recognize the error situation - and continues according to sending policy. And the session times out with the following error :
Sandesha2 could not send the message on sequence <URL> as the sequence has timed out.
I have only had time to test on version 1.3.
/hans
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Resolved: (SANDESHA2-130) Exceptions in Axis stack not
reported to client
Posted by "David Illsley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Illsley resolved SANDESHA2-130.
-------------------------------------
Resolution: Won't Fix
I'm not sure this is really a bug. If the RM implementation has accepted the message then there is a failure, then the expected behaviour is that the send is re-tried. There isn't a way for sandesha2 to identify whether an exception is transient or permanent, and whether it is an infrastructure bug or transport failure, or something else. I think that the current behaviour is perhaps the best we can expect, except perhaps for additional tracing in Sandesha2 and Rampart...
> Exceptions in Axis stack not reported to client
> -----------------------------------------------
>
> Key: SANDESHA2-130
> URL: https://issues.apache.org/jira/browse/SANDESHA2-130
> Project: Sandesha2
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Axis2/Rampart/Sandesha2 v 1.3
> Reporter: Hans G Knudsen
> Priority: Blocker
>
> Hi!
> If errors occurs in the Axis stack after Sandesha has taken over handling - the exception is not handed back to the calling client.
> Eg. if an error occur in Rampart trying to do the outgoing security handling.
> Testcase:
> - misspell
> <ramp:passwordCallbackClass>wrong.class.Name</ramp:passwordCallbackClass>
> Sandesha does not recognize the error situation - and continues according to sending policy. And the session times out with the following error :
> Sandesha2 could not send the message on sequence <URL> as the sequence has timed out.
> I have only had time to test on version 1.3.
> /hans
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Updated: (SANDESHA2-130) Exceptions in Axis stack not
reported to client
Posted by "Hans G Knudsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hans G Knudsen updated SANDESHA2-130:
-------------------------------------
Priority: Blocker (was: Major)
Change to Blocker for 1.4 as suggested by David Illsley.
> Exceptions in Axis stack not reported to client
> -----------------------------------------------
>
> Key: SANDESHA2-130
> URL: https://issues.apache.org/jira/browse/SANDESHA2-130
> Project: Sandesha2
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Axis2/Rampart/Sandesha2 v 1.3
> Reporter: Hans G Knudsen
> Priority: Blocker
>
> Hi!
> If errors occurs in the Axis stack after Sandesha has taken over handling - the exception is not handed back to the calling client.
> Eg. if an error occur in Rampart trying to do the outgoing security handling.
> Testcase:
> - misspell
> <ramp:passwordCallbackClass>wrong.class.Name</ramp:passwordCallbackClass>
> Sandesha does not recognize the error situation - and continues according to sending policy. And the session times out with the following error :
> Sandesha2 could not send the message on sequence <URL> as the sequence has timed out.
> I have only had time to test on version 1.3.
> /hans
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org