You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Stadelmann Josef <jo...@winterthur.ch> on 2007/03/14 11:32:01 UTC
AW: [axis2] session management fails with invalidServiceGroupID Exception
Jochen
**** BTW - what scope= are you using? The original problem I had was with scope=soapsession only.
with scope=application your talking to only one instance of your service-class and not to a statefull-objects.
The problem with the invalidServiceGroupeContextID is because after timeout the ID is no longer valid!
client-threads calling afterr timeoutn with the same previous used sender-handle will because they send the wrong timed out ID
client-threads calling with a fresh sender-handle will not fail because the do not pass an ID but receive one in the reply-message
Regarding Instances of Service Classes (also called statefull-Objects, objects are instances of a class) be sure that you can cleanly
tell a) when you talk to different instances of a service-object (instance of a service-class) or b) when you talk to the same instance of a service-object (singelton).
Sometimes just a matter of having certain variables defined as static, and since variables in jave defined static are shared among objects!
I was once running into the same trap. Be aware that you know the real instance your talking to, maybe identify each object by unique hash value or UUID.
Josef
-----Ursprüngliche Nachricht-----
Von: Jochen Zink [mailto:jochenlist@web.de]
Gesendet: Mittwoch, 14. März 2007 10:40
An: axis-user@ws.apache.org
Betreff: Re: [axis2] session management fails with invalidServiceGroupID
Exception
A big Thank you!!!! I don't believe it... in axis2.xml the ConfigContextTimeout are milliseconds and not seconds like the comment tells.
But... there is another thing, which I don't understand.
Know, the ConfigContextTimeout Parameter has the value 30000 (30seconds).
My client invokes the login method, sleeps 60000 milliseconds (1min) and after this wait period, it invokes a second method. It works... but why?! Normally I think, the session run into a timeout. The client has not touch the service over a minute and can successfully call a method. ...
Thanks!
> -----Ursprüngliche Nachricht-----
> Von: axis-user@ws.apache.org
> Gesendet: 14.03.07 10:19:22
> An: <ax...@ws.apache.org>
> Betreff: AW: [axis2] session management fails with invalidServiceGroupID Exception
> Hi Jochen,
>
> Maybe you have the same problem then I had.
> For that I have had logged a JIRA and meanwhile it' sfixed. Look at
>
>
> [ https://issues.apache.org/jira/browse/AXIS2-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
>
> and more in the e-mail thread at
>
> http://marc.theaimsgroup.com/?l=axis-user&m=117316427720305&w=2
>
>
> I hope for you that it is that easy to fix your problem.
>
> Regards
> Josef
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Jochen Zink [mailto:jochenlist@web.de]
> Gesendet: Mittwoch, 14. März 2007 10:01
> An: axis-user@ws.apache.org
> Betreff: [axis2] session management fails with invalidServiceGroupID
> Exception
>
>
> Hello at all,
>
> I have a session based Webservice with three Methods. A client has 2 threads with 2 different clients, which use the webservice. Only the second client can invoke more than the first method of the service.
>
> Example:
> Client 1 invoke Method login -> everything okay.
> Client 2 invole Method login -> invoking works fine BUT on the service class, that is created by the call of client 1, the destroy method is called
>
> Client 1 invokes method transfer -> The following exception is thrown on client side:
> org.apache.axis2.AxisFault: Invalid Service Group Id urn:uuid:4489A6CEFA71AF964F1173862161488
> at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:271)
> at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
> at de.nepatec.edocbox.comserver.client.DocumentTransferServiceStub.transferDocument(DocumentTransferServiceStub.java:212)
> at de.nepatec.edocbox.comserver.client.Client.run(Client.java:84)
>
> Client 2 invokes Method transfer -> everything okay
>
>
> It seems that only the last instance of the service class is alive.
>
> The service is correct state full. With only one client, all member attributes are available over all method calls.
>
> Here is the services.xml:
> <service name="DocumentTransferService" scope="soapsession">
>
> <parameter name="enableMTOM" locked="false">true</parameter>
>
>
> <!-- Message Receivers -->
>
> <parameter locked="false" name="ServiceClass">
> de.nepatec.edocbox.comserver.comchannel.serviceimpl.DocumentTransferServiceSkeleton
> </parameter>
>
> <!-- Operations -->
>
>
> </service>
> </serviceGroup>
>
> In the servers axis2.xml addressing module is engaged.
>
> On client side the Sessionmanagement is enabled:
> serviceStub._getServiceClient().getOptions().setManageSession(true);
>
>
>
> I found the same problem in the mailinglist ( http://marc.theaimsgroup.com/?t=116282349800006&r=1&w=2) but without a solution.
>
> Is this a axis2 Bug or did I something wrong? What can I do, to have a session based webservice that can handle mutltiple clients?
>
> Thanks for all!
>
>
>
> _______________________________________________________________________
> Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos.
> Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=022222
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
_________________________________________________________________________
In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten!
Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org