Jochen
my comment +++>
starts right here, and you are pretty right with your observation because ....
I found : my problem reported in JIRA-1991 is not fixed
when I add (as you do) Thread.sleep(40000) into an endless client-side
sending-loop, enforcing a time-out at the server, for this-thread
Was I said in earlier e-mails: I am continously looping, sending as fast as
possible.
With that beeing true and axis2.xml timeout-constant set to 30000 the problem
was gone. BUT now it reappears the same way as Jochen describes it.
If I suspend clinet#1-thread by 40 second (Thread.sleep(40000)) inbetween calls
to the server, calls with all required header infos for scope=soapsession, then
this thread does in fact not end in a fault! no fault is raised at the server
to client#1 for the existing time-out-condition and sends continues endless
every 40 seconds perfect for client#1.
The trouble with client#1 starts only when I launch in a different thread my
next (SOAP) client#2 which does the same. As soon as this client#2 starts,
client#1 on it's next send fails with the error shown in the attachment, and
client#2 even itself in a time-out after 30 seconds works perfect until
client#3 is launched. and so on.
invalid Service Groupe ID
Under this circumstances and considerations, I would like to reopen JIRA-1991,
unless one of the developers has a more precise explanation about what we can
do or what the aim of the time.-out is. BUT the problem as such is not fixed
but but was shifted a bit.
only a launch of client#2 makes client#1 fail with invalid Service Grouop ID if
client#1 is in a time-out-condition, and client#1 runs perfectly even in
time-out-condition as Jochen explains, unless client#2 starts. The same is true
for client#2 to client#3 etc.
I ask, time-out for what?
What is the aim of this time-out in regard to client#1, I do not
undestand the model?
In my mind axis2 should invoke destroy() immediately for the
session/thread/object in time-out-condition.
Josef <+++
My thread runs continously perfect even
-----Ursprüngliche Nachricht-----
Von: Jochen Zink [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 14. März 2007 16:08
An: axis-user@ws.apache.org
Betreff: Re: [axis2] session management fails with invalidServiceGroupID
Exception
Yes, the clients sends the ServiceGroupID,
I take a look to the soapmessages. The servers respons looks also good
..
<soapenv:Body>
<soapenv:Fault>
<soapenv:Code>
<soapenv:Value>soapenv:Sender</soapenv:Value>
</soapenv:Code>
<soapenv:Reason>
<soapenv:Text xml:lang="en-US">Invalid Service Group Id
urn:uuid:F6AFB3268FA47142F11173882794098</soapenv:Text>
</soapenv:Reason>
<soapenv:Detail></soapenv:Detail>
</soapenv:Fault>
</soapenv:Body>
..
But I don't know why I get an nullpointer on Clientside... But that is another
problem, and not the reason why I have posted ;)
I wonder about this. If only one client uses the Services. The Session on the
Server never(!) expired, If no client sends a Message to the services.
+++> if no client sends as msg .... to time out at the server the server would
need to perform some kind of house keeping to realise which sessions, context
or hwat ever it is or is under a time-out-constraint has run meanwhile into a
time-out. I think it should be up to the team to reply and explain about what
we have here. <+++
Client sends its first message: Everything okay, a service Instance is created
Client waits longer, than the configured Timeout
Clients sends its second message: The same service instance is invoked
correctly.
Only after the second message, the destroy message is called and all messages
send to servers sends a message, that the servicegroupid ist not valid.
+++> what about the logger. If the logger takes output from several threads and
consolidates it into one stream, then that could potentially lead to a
presentation which is some-how out-of-sequence with elements presented <+++
I seems, that axis first handle the invoking method and after that it checks if
a session is run into a timeout.
thx
Jochen
> -----Ursprüngliche Nachricht-----
> Von: axis-user@ws.apache.org
> Gesendet: 14.03.07 15:12:33
> An: <axis-user@ws.apache.org>
> Betreff: AW: [axis2] session management fails with invalidServiceGroupID
> Exception
> Jochen,
>
> my comment in +++> ... <+++ below
>
> -----Ursprüngliche Nachricht-----
> Von: Jochen Zink [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 14. März 2007 12:28
> An: axis-user@ws.apache.org
> Betreff: Re: [axis2] session management fails with invalidServiceGroupID
> Exception
>
>
> I use soapsession scope.
>
>
> I'm sure that every client invokes a creation of a new ServicesClass. I
> control it with hashcodes of the instances. Every client talks to another
> instance. A single client talks, every method call to is own Service Instance.
>
> The Timeout on the service is set to 30000.
>
> After the first method call, the Client waits 40seconds before he calls the
> next method.
>
>
>
> +++> Jochen, can you check that the message sent with the 2nd call of
> client#1 which has timed-out still sends the ServiceGroupId?
>
> also we migth talk about similar not exactly equal problems.
>
> does your clinet#1 second message look similar like (carry a ServiceGroupID)?
>
> - <soapenv:Header>
> <wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:To>
> - <wsa:ReplyTo>
> <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
> - <wsa:ReferenceParameters>
> <axis2:ServiceGroupId
> xmlns:axis2="http://ws.apache.org/namespaces/axis2";>urn:uuid:AEDE11BE4497D9478F117316759348254</axis2:ServiceGroupId>
>
> </wsa:ReferenceParameters>
> </wsa:ReplyTo>
> <wsa:MessageID>urn:uuid:AEDE11BE4497D9478F117316759399760</wsa:MessageID>
> <wsa:Action>urn:echo</wsa:Action>
> <wsa:RelatesTo
> wsa:RelationshipType="http://www.w3.org/2005/08/addressing/reply";>urn:uuid:C1D5F6754451BC782111731675939823</wsa:RelatesTo>
>
> </soapenv:Header>
>
>
> if a ServiceGroupID is sent to a timed-out service-object in a ServiceGroup
> your initial fault should show up.
>
> if no ServiceGroupId is sent, that would explain why no fault "invalid
> Service Group ID", is raised.
> in this case, I would expect that a new ServicegroupID is created and that
> the old ServiceGroupID is removed and hence destroy() is called on the first
> service-object. is this the case?
>
> And the question to the developers would remain: is this intended behaviour?
>
> Josef <+++
>
>
>
>
>
> The servers log messages are:
> init [EMAIL PROTECTED]
> openTransferSession [EMAIL PROTECTED]
> // Here is the client waiting
> closetransferSession [EMAIL PROTECTED]
> last touching Time 40031
>
>
>
> As you can see, it is always the same Instance.
>
> The strange thing is, if I invoke another client, the service Instance of the
> first client should be destroyed after the 30 seconds.
>
>
>
>
> Example:
> Client1.firstMethod:
> Client1.wait:
> Client2.firstMethod:
> Know, the destroy Method is invoked
> Client 2.wait:
> Client1.secondMethod:
>
> java.lang.NullPointerException
> at
> org.apache.axis2.context.MessageContext.isHeaderPresent(MessageContext.java:1054)
> at
> org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(AddressingInHandler.java:72)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:382)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:522)
> at org.apache.axis2.engine.AxisEngine.receiveFault(AxisEngine.java:600)
> at
> org.apache.axis2.description.RobustOutOnlyAxisOperation$RobustOperationClient.send(RobustOutOnlyAxisOperation.java:99)
> at
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
> at
> de.nepatec.edocbox.comserver.client.DocumentTransferServiceStub.closeTransferSession(DocumentTransferServiceStub.java:561)
> at de.nepatec.edocbox.comserver.client.Client.run(Client.java:99)
>
> Client2.secondMethod: Works fine, but the TimeOut is expired.
>
> A session runs only in timeout, if a other client invokes his own Instance.
> Do you understnad what I mean?!
>
> The log messages on the server wich printent with invoking the above example
>
> init [EMAIL PROTECTED]
> openTransferSession [EMAIL PROTECTED]
> destroy [EMAIL PROTECTED]
> init [EMAIL PROTECTED]
> openTransferSession [EMAIL PROTECTED]
> transferDocument [EMAIL PROTECTED]
> closetransferSession [EMAIL PROTECTED]
> last touching Time 50016
>
>
> +++> Yes, I have seen the same sequence, destroy() before init() but on two
> different service-objects,
>
> in case you reset the axis2 value to 30 then you have nearly constant a
> time-out condition, as explained by rob, which made my client#n fail as soon
> as client#n+1 was starting. Since axis2.xml raised this value to 30000 this
> my problem is gone, and perhaps similra problems too.
>
> Josef <+++
>
>
>
>
>
> The Client Code is like this:
>
> ConfigurationContext ctx =
> ConfigurationContextFactory.createConfigurationContextFromFileSystem("repos",
> "repos/conf/axis2.xml");
>
> DocumentTransferServiceStub serviceStub = new DocumentTransferServiceStub(
> ctx,
>
> "http://localhost:8080/comchannel/services/DocumentTransferService";);
>
> serviceStub._getServiceClient().getOptions().setManageSession(true);
>
> serviceStub._getServiceClient().getOptions().setProperty(Constants.Configuration.ENABLE_MTOM,
> Constants.VALUE_TRUE);
> serviceStub._getServiceClient().getOptions().setTimeOutInMilliSeconds(100000);
>
>
>
> DocumentTransferServiceStub.OpenTransferSession open = new
> DocumentTransferServiceStub.OpenTransferSession();
>
> // ... some stuff
>
> // call first method
> serviceStub.openTransferSession(open);
>
> // wait 40 seconds
> Thread.sleep(40000);
> // call next Method
> serviceStub.closeTransferSession();
>
>
> Thanks!
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: axis-user@ws.apache.org
> > Gesendet: 14.03.07 11:32:46
> > An: <axis-user@ws.apache.org>
> > Betreff: 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:[EMAIL PROTECTED]
> > 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: <axis-user@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:[EMAIL PROTECTED]
> > > 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: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > _________________________________________________________________________
> > 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: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> _______________________________________________________________________
> 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
INFO: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope
xmlns:wsa="http://www.w3.org/2005/08/addressing";
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header><wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:To><wsa:ReplyTo><wsa:Address>http://www.w3.org/2005/08/addressing/none</wsa:Address></wsa:ReplyTo><wsa:MessageID>urn:uuid:CE9E77B0B47B25FCA9117388659732546</wsa:MessageID><wsa:Action>http://www.w3.org/2005/08/addressing/soap/fault</wsa:Action><wsa:RelatesTo
wsa:RelationshipType="http://www.w3.org/2005/08/addressing/reply";>urn:uuid:DD2830964FC41BFEA411738865973095</wsa:RelatesTo></soapenv:Header><soapenv:Body><soapenv:Fault><faultcode>soapenv:Client</faultcode><faultstring>Invalid
Service Group Id
urn:uuid:CE9E77B0B47B25FCA9117388647671138</faultstring><detail><Exception>org.apache.axis2.AxisFault:
Invalid Service Group Id urn:uuid:CE9E77B0B47B25FCA9117388647671138
at
org.apache.axis2.engine.InstanceDispatcher.extractServiceGroupContextId(InstanceDispatcher.java:163)
at
org.apache.axis2.engine.InstanceDispatcher.invoke(InstanceDispatcher.java:61)
at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:518)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:483)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:319)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:247)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
</Exception></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
14.03.2007 16:36:37 userguide.loggingmodule.LogHandler invoke
INFO: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope
xmlns:wsa="http://www.w3.org/2005/08/addressing";
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header><wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:To><wsa:ReplyTo><wsa:Address>http://www.w3.org/2005/08/addressing/none</wsa:Address></wsa:ReplyTo><wsa:MessageID>urn:uuid:CE9E77B0B47B25FCA9117388659732546</wsa:MessageID><wsa:Action>http://www.w3.org/2005/08/addressing/soap/fault</wsa:Action><wsa:RelatesTo
wsa:RelationshipType="http://www.w3.org/2005/08/addressing/reply";>urn:uuid:DD2830964FC41BFEA411738865973095</wsa:RelatesTo></soapenv:Header><soapenv:Body><soapenv:Fault><faultcode>soapenv:Client</faultcode><faultstring>Invalid
Service Group Id
urn:uuid:CE9E77B0B47B25FCA9117388647671138</faultstring><detail><Exception>org.apache.axis2.AxisFault:
Invalid Service Group Id urn:uuid:CE9E77B0B47B25FCA9117388647671138
at
org.apache.axis2.engine.InstanceDispatcher.extractServiceGroupContextId(InstanceDispatcher.java:163)
at
org.apache.axis2.engine.InstanceDispatcher.invoke(InstanceDispatcher.java:61)
at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:518)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:483)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:319)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:247)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
</Exception></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
org.apache.axis2.AxisFault: Invalid Service Group Id
urn:uuid:CE9E77B0B47B25FCA9117388647671138
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:308)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:579)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508)
at userguide.clients.SOAPClient.main(SOAPClient.java:142)
Caused by: java.lang.Exception: org.apache.axis2.AxisFault: Invalid Service
Group Id urn:uuid:CE9E77B0B47B25FCA9117388647671138
at
org.apache.axis2.engine.InstanceDispatcher.extractServiceGroupContextId(InstanceDispatcher.java:163)
at
org.apache.axis2.engine.InstanceDispatcher.invoke(InstanceDispatcher.java:61)
at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:518)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:483)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:319)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:247)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
at org.apache.axis2.AxisFault.<init>(AxisFault.java:159)
... 4 more
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
