[
https://issues.apache.org/jira/browse/AXIS2-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1991.
--------------------------------------
Resolution: Invalid
When you deploy a service in soapsession it has time out period of 30s , if
client1 does not touch the service for about 30s , then the session will be
invalidated. That is why you are getting the above behavior , you can change
the timeout period in axis2.xml to change the bahaviour.
Change the following parameter as you like;
<parameter name="ConfigContextTimeoutInterval" locked="false">30</parameter>
> 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: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.1
> Environment: Windows 2000, tomcat, axis2-1.1,
> Reporter: Josef Stadelmann
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
