[jira] Reopened: (AXIS2-1991) ServiceGroupContextID re-created by second client calling in scope=soapsession making first client session fail with exception unknown ServiceGroupContextID

["Josef Stadelmann (JIRA)" <ji...@apache.org>]

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

Josef Stadelmann reopened AXIS2-1991:
-------------------------------------


I have applied the current fix within AXIS2.XML and set the time-out-constant to 30000 ms

 NOW: When client#1 times out for a subsequent call by using Thread.sleep(40000) after its primary call, the next and each following call will absolutly succeed and not result in a fault as one would expect in a time-out-condition. This is a problem.

Client#1 becomes only aware about the timed-out-condition it is in, when the next client#2 starts. 

When the new client#2 registers, the Service Group ID is found to be in a time-out-condition and is removed and client#1 will receive on it's next call "invalid Service Group ID", BUT client#2 loops now endless with or without going into a time-out-condition.

And this happens unless client#3 is launched when client#2 dies with the same effects as client#1 before. 

The problem is in my mind that no AXIS2 hous keeping service invalidates the timed-out service group ID's and that without a second client#2, client#1 is not sent back with an exception in time-out-conditions.

We need any client#x is made aware about "invalid Service group ID" and that AXIS2 calls destroy() for the client's service object which is found in a timed-out-condition. i.e. closing the DB for a client which has timed out and which is now in a broken session.

Josef Stadelmann

> ServiceGroupContextID re-created by second client calling in scope=soapsession making first client session fail with exception unknown ServiceGroupContextID 
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-1991
>                 URL: https://issues.apache.org/jira/browse/AXIS2-1991
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.1
>         Environment: Windows 2000, tomcat, axis2-1.1, 
>            Reporter: Josef Stadelmann
>         Assigned To: Deepal Jayasinghe
>         Attachments: MyService.java, services.xml, SOAPClient.java
>
>
> Hi session-managers, 
> I'm running my client and server with modules addressing-1.1, logging, soapmonitor-1.1 engaged and have set scope=soapsession
> MyService.java got the additional methods 
>   
>    public void init(ServiceContext sCtx) { 
>         this.sc = sCtx; 
>         this.log.info(sc.toString()+" init() called "); 
>     } 
>     
>     public void destroy(ServiceContext sCtx) { 
>         if(!this.sc.toString().equals(sCtx.toString())){ 
>             this.log.error("ServiceContext on init() and destroy() not equal in "); 
>         } 
>         this.log.info(sc.toString()+" destroy() called "); 
>     } 
>     public void setOperationContext(OperationContext oCtx) { 
>         this.oc = oCtx; 
>         this.log.info(oc.toString()+" setOperationContext() called ");        
>     } 
>   
> I start client #1 which has the effect that MyService.init() is called; so far so right! 
> Client #1 then loops and sends continously messages to MyService.echo() 
> I start client #2 which has the effect that MyService.destroy() is called followed by MyService.init() 
> This has the effect that client #1 fails with an "invalid group context id exception" 
> Josef 

-- 
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