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 "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2007/05/08 18:25:15 UTC

[jira] Resolved: (AXIS2-2073) soap session not thread safe?

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

Deepal Jayasinghe resolved AXIS2-2073.
--------------------------------------

    Resolution: Fixed

The problem can be simply solved by changing the following parameter in server side axis2.xml

 <parameter name="ConfigContextTimeoutInterval">30000</parameter>

N.B - value is in millisecond 

> soap session not thread safe?
> -----------------------------
>
>                 Key: AXIS2-2073
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2073
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: Addressing, kernel
>    Affects Versions: 1.1.1
>         Environment: windows XP, axis2-1.1.1, JBoss 4.0.4 GA
>            Reporter: Sining Li
>         Attachments: faulthandling.zip
>
>
> I have modified sample project faulthandling to implement soap session.  
> The problem happens at the client side.  If I create two instance of the clientstub and sending requests to the service one after another, I got an AxisFault: Invalid Service Group Id.  This makes me think that if the addressing module is running in a single instance. I'll try to upload my code. 

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