You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by bu...@apache.org on 2004/02/06 21:37:41 UTC

DO NOT REPLY [Bug 26735] New: - Session not created when exception occurs in first call

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26735>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26735

Session not created when exception occurs in first call

           Summary: Session not created when exception occurs in first call
           Product: Axis
           Version: 1.1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Basic Architecture
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: tony.sloos@ict.nl


When an exception occurs during the first call there is no session created to 
maintain the conversational state. I use header-based sessions with a 
SimpleSession on both the server and client side. 

Observation:
In the current RPCProvider implementation processing of the response message is 
skipped when an exception occurs during method invocation.

Expected behaviour:
In any case a conversational state should be created to allow particular 
failures to be tracked. For example a user that fails to logon correctly after 
three attempts should be locked out.