AW: [axis2] session management fails with invalidServiceGroupID Exception

[Stadelmann Josef <jo...@winterthur.ch>]

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