You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Mancinelli Elodie <el...@bull.net> on 2006/06/13 10:52:50 UTC
Re: [Fwd: Re: user guide example]
Hi,
I have the same problem. I can access tomcat, the server met an internal
error which stopped the request (error: HTTP/1.1 500 Internal Error
Servlet).
I search where the error can comes from and I have questions on the
ports 8080,8070 and 6060. I don't understand the works of these? Con
you explain me the difference between ports 8080, 8070 and 6060?
Thanks for your time
Regards,
Elodie
> Charles Souillard wrote:
>
> I just missed to tell you that traces from onComplete and onError
> methods from TestCallBack class are never printed out.
> Can you explain me how messages are managed inside sandesha ?
> I put 8080 in the targetEPR, then 8070 in the TRANSPORT_URL and I get
> 6060 in the message sent...
> I am a bit confused about the routing of my message...
> Thanks,
> Charles
>
> Charles Souillard wrote:
>
>> Hi Chamikara,
>>
>> I have added the following option in my client :
>> clientOptions.setProperty(MessageContextConstants.TRANSPORT_URL,"http://localhost:8070/axis2/services/RMSampleService");
>>
>>
>> It doesn't change my problem. I never got a response so I can not
>> tell you if it is a 202 or 500 code.
>> I am waiting for this information in the client coe. Is that right ?
>> Or perhaps the Axis Engine is sending a message elsewhere ?
>>
>> I have followed all the steps described in the Sandesha User Guide
>> and it is not working... Is it possible that my proxy is causing
>> problems ? I do not have any other idea as it seems that this example
>> should run I can't find any other user having problems on the web.
>>
>> Can you please help me or give me any stuff I can try to help me
>> understanding what is going wrong.
>>
>> Thanks a lot
>> Regards
>> Charles
>>
>>
>> Chamikara Jayalath wrote:
>>
>>> Hi Charles,
>>>
>>> The create sequence response message is sent directly to the port
>>> 6060. So you wont see it in the tcp monitor. What is the HTTP
>>> response to ur Create Sequence request message. is it 202 OK or 500.
>>>
>>> The reason for the NullPointer is Axis2 client side trying to get
>>> the relatesTo value which is not present in the request you make
>>> through the browser.
>>>
>>> Chamikara
>>>
>>>
>>>
>>> On 6/2/06, *Charles Souillard* <Charles.Souillard@ext.bull.net
>>> <ma...@ext.bull.net>> wrote:
>>>
>>> Hi all,
>>>
>>> I just sent a message on axis user list for a problem concenring
>>> the use
>>> of sandesha2.
>>> I am trying to use the user-guide example but I am having problem
>>> during
>>> the creation of the first sequence.
>>> In fact I never get the ack of the createSequence.
>>>
>>> I can give you hereafter the mail I sent to axis user list.
>>>
>>> Please help me on that problem.
>>>
>>> Regards,
>>> Charles
>>>
>>>
>>> Hi all,
>>>
>>> I am trying to use the same example.
>>> I am encoutering the same problem. I have also caught the http
>>> request
>>> inside tcpmon.
>>> You can find it hereafter :
>>>
>>> POST /axis2/services/RMSampleService HTTP/1.1
>>> User-Agent: Axis2
>>> SOAPAction: http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence
>>> Host: localhost:13000
>>> Transfer-Encoding: chunked
>>> Content-Type: text/xml; charset=UTF-8
>>>
>>> 320
>>> <?xml version='1.0' encoding='UTF-8'?>
>>> <soapenv:Envelope
>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>>> xmlns:wsa="http://www.w3.org/2005/08/addressing
>>> <http://www.w3.org/2005/08/addressing>">
>>> <soapenv:Header>
>>>
>>> <wsa:To>http://localhost:13000/axis2/services/RMSampleService</wsa:To>
>>> <wsa:ReplyTo>
>>>
>>> <wsa:Address>http://129.183.18.65:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__</wsa:Address>
>>>
>>>
>>> </wsa:ReplyTo>
>>>
>>> <wsa:MessageID>urn:uuid:F568425CAF0692619511492482122053</wsa:MessageID>
>>>
>>> <wsa:Action>http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence
>>>
>>> <http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence></wsa:Action>
>>>
>>> </soapenv:Header>
>>> <soapenv:Body>
>>> <wsrm:CreateSequence
>>> xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
>>> <wsrm:AcksTo>
>>>
>>> <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
>>>
>>> </wsrm:AcksTo>
>>> </wsrm:CreateSequence>
>>> </soapenv:Body>
>>> </soapenv:Envelope>0
>>>
>>> I have entered the wsa adress into my web browser
>>>
>>> (http://129.183.18.65:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__
>>>
>>>
>>> <http://129.183.18.65:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__>)
>>>
>>> and I get the following SOAP message :
>>>
>>> -
>>> <soapenv:Envelope>
>>> -
>>> <soapenv:Header>
>>> -
>>> <wsa:ReplyTo>
>>> <wsa:Address>
>>> http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
>>> </wsa:ReplyTo>
>>>
>>> <wsa:MessageID>urn:uuid:46BED3F8855DCCC1B2114924808940114</wsa:MessageID>
>>>
>>> <wsa:Action>
>>> http://www.w3.org/2005/08/addressing/fault</wsa:Action>
>>> </soapenv:Header>
>>> -
>>> <soapenv:Body>
>>> -
>>> <soapenv:Fault>
>>> <faultcode>soapenv:Client</faultcode>
>>> <faultstring>unknown</faultstring>
>>> -
>>> <detail>
>>> -
>>> <Exception>
>>> java.lang.NullPointerException
>>> at
>>>
>>> org.apache.axis2.util.CallbackReceiver.receive(CallbackReceiver.java:32)
>>>
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java :454)
>>> at
>>>
>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPGetRequest(HTTPTransportUtils.java:138)
>>>
>>>
>>> at
>>>
>>> org.apache.axis2.transport.http.HTTPWorker.processRequest(HTTPWorker.java:226)
>>>
>>>
>>> at
>>>
>>> org.apache.axis2.transport.http.server.SimpleConnectionThread.run(SimpleConnectionThread.java:92)
>>>
>>>
>>> at
>>>
>>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>>>
>>>
>>> at
>>>
>>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>>>
>>>
>>> at java.lang.Thread.run(Thread.java:595)
>>> </Exception>
>>> </detail>
>>> </soapenv:Fault>
>>> </soapenv:Body>
>>> </soapenv:Envelope>
>>>
>>> Does anybody knows why I am getting a NPE into CallbackReceiver ?
>>> I tried to debug axis2 into eclipse but I never reached the
>>> breakpoint I
>>> put on the line 32...
>>>
>>> Can you help me please ?
>>>
>>> Thanks a lot for your answers.
>>> Regards,
>>> Charles
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>>> <ma...@ws.apache.org>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: [Fwd: Re: user guide example]
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Elodie,Charles,
Port 8080 which you set in the options object (using the setTo method), will
be reflected in the wsAddressing To address which goes within the SOAP
envelope.
The port 8070 which you set in the transport URL is used to derive the
transport address. I.e. even though the SOAP To address of the SOAP envelope
goes with the port 8080, in the transport level (for e.g. HTTP) the message
is sent to the port 8070. This is the feature of Axis2 that allows us to
send the message through the tcp monitor (where the tcpmonitor sends it to
the correct port - 8080).
Port 6060 is the default client listner port of Axis2. So Axis2 client start
a listner on this port. Any async response messages or RM control messages
that are comming from the server will come to this port. Unfortunately since
they are directly sent from the server to the client, you wont see them in
the tcp monitor.
First check weather you have confitured the server property. After doing
this the RMSampleService should be lister in the List Services page of
Axis2.
Then start a tcp mapping from the port 8070 to port 8080. (assuming tomcat
is running on the port 8080).
Now run the Sample clients.
Chamikara
On 6/13/06, Mancinelli Elodie <el...@bull.net> wrote:
>
> Hi,
>
> I have the same problem. I can access tomcat, the server met an internal
> error which stopped the request (error: HTTP/1.1 500 Internal Error
> Servlet).
>
> I search where the error can comes from and I have questions on the
> ports 8080,8070 and 6060. I don't understand the works of these? Con
> you explain me the difference between ports 8080, 8070 and 6060?
>
> Thanks for your time
>
> Regards,
> Elodie
>
>
> > Charles Souillard wrote:
> >
> > I just missed to tell you that traces from onComplete and onError
> > methods from TestCallBack class are never printed out.
> > Can you explain me how messages are managed inside sandesha ?
> > I put 8080 in the targetEPR, then 8070 in the TRANSPORT_URL and I get
> > 6060 in the message sent...
> > I am a bit confused about the routing of my message...
> > Thanks,
> > Charles
> >
> > Charles Souillard wrote:
> >
> >> Hi Chamikara,
> >>
> >> I have added the following option in my client :
> >> clientOptions.setProperty(MessageContextConstants.TRANSPORT_URL,"http://localhost:8070/axis2/services/RMSampleService
> ");
> >>
> >>
> >> It doesn't change my problem. I never got a response so I can not
> >> tell you if it is a 202 or 500 code.
> >> I am waiting for this information in the client coe. Is that right ?
> >> Or perhaps the Axis Engine is sending a message elsewhere ?
> >>
> >> I have followed all the steps described in the Sandesha User Guide
> >> and it is not working... Is it possible that my proxy is causing
> >> problems ? I do not have any other idea as it seems that this example
> >> should run I can't find any other user having problems on the web.
> >>
> >> Can you please help me or give me any stuff I can try to help me
> >> understanding what is going wrong.
> >>
> >> Thanks a lot
> >> Regards
> >> Charles
> >>
> >>
> >> Chamikara Jayalath wrote:
> >>
> >>> Hi Charles,
> >>>
> >>> The create sequence response message is sent directly to the port
> >>> 6060. So you wont see it in the tcp monitor. What is the HTTP
> >>> response to ur Create Sequence request message. is it 202 OK or 500.
> >>>
> >>> The reason for the NullPointer is Axis2 client side trying to get
> >>> the relatesTo value which is not present in the request you make
> >>> through the browser.
> >>>
> >>> Chamikara
> >>>
> >>>
> >>>
> >>> On 6/2/06, *Charles Souillard* <Charles.Souillard@ext.bull.net
> >>> <mailto: Charles.Souillard@ext.bull.net>> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I just sent a message on axis user list for a problem concenring
> >>> the use
> >>> of sandesha2.
> >>> I am trying to use the user-guide example but I am having problem
> >>> during
> >>> the creation of the first sequence.
> >>> In fact I never get the ack of the createSequence.
> >>>
> >>> I can give you hereafter the mail I sent to axis user list.
> >>>
> >>> Please help me on that problem.
> >>>
> >>> Regards,
> >>> Charles
> >>>
> >>>
> >>> Hi all,
> >>>
> >>> I am trying to use the same example.
> >>> I am encoutering the same problem. I have also caught the http
> >>> request
> >>> inside tcpmon.
> >>> You can find it hereafter :
> >>>
> >>> POST /axis2/services/RMSampleService HTTP/1.1
> >>> User-Agent: Axis2
> >>> SOAPAction:
> http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence
> >>> Host: localhost:13000
> >>> Transfer-Encoding: chunked
> >>> Content-Type: text/xml; charset=UTF-8
> >>>
> >>> 320
> >>> <?xml version='1.0' encoding='UTF-8'?>
> >>> <soapenv:Envelope
> >>> xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/"
> >>> xmlns:wsa="http://www.w3.org/2005/08/addressing
> >>> <http://www.w3.org/2005/08/addressing>">
> >>> <soapenv:Header>
> >>>
> >>> <wsa:To> http://localhost:13000/axis2/services/RMSampleService
> </wsa:To>
> >>> <wsa:ReplyTo>
> >>>
> >>> <wsa:Address>http://129.183.18.65:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__
> </wsa:Address>
> >>>
> >>>
> >>> </wsa:ReplyTo>
> >>>
> >>>
> <wsa:MessageID>urn:uuid:F568425CAF0692619511492482122053</wsa:MessageID>
> >>>
> >>> <wsa:Action>
> http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence
> >>>
> >>> < http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence
> ></wsa:Action>
> >>>
> >>> </soapenv:Header>
> >>> <soapenv:Body>
> >>> <wsrm:CreateSequence
> >>> xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
> >>> <wsrm:AcksTo>
> >>>
> >>> <wsa:Address> http://www.w3.org/2005/08/addressing/anonymous
> </wsa:Address>
> >>>
> >>> </wsrm:AcksTo>
> >>> </wsrm:CreateSequence>
> >>> </soapenv:Body>
> >>> </soapenv:Envelope>0
> >>>
> >>> I have entered the wsa adress into my web browser
> >>>
> >>> (http://129.183.18.65:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__
> >>>
> >>>
> >>> <http://129.183.18.65:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__
> >)
> >>>
> >>> and I get the following SOAP message :
> >>>
> >>> -
> >>> <soapenv:Envelope>
> >>> -
> >>> <soapenv:Header>
> >>> -
> >>> <wsa:ReplyTo>
> >>> <wsa:Address>
> >>> http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
> >>> </wsa:ReplyTo>
> >>>
> >>>
> <wsa:MessageID>urn:uuid:46BED3F8855DCCC1B2114924808940114</wsa:MessageID>
> >>>
> >>> <wsa:Action>
> >>> http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> >>> </soapenv:Header>
> >>> -
> >>> <soapenv:Body>
> >>> -
> >>> <soapenv:Fault>
> >>> <faultcode>soapenv:Client</faultcode>
> >>> <faultstring>unknown</faultstring>
> >>> -
> >>> <detail>
> >>> -
> >>> <Exception>
> >>> java.lang.NullPointerException
> >>> at
> >>>
> >>> org.apache.axis2.util.CallbackReceiver.receive(CallbackReceiver.java
> :32)
> >>>
> >>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
> >>> at
> >>>
> >>>
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPGetRequest(
> HTTPTransportUtils.java:138)
> >>>
> >>>
> >>> at
> >>>
> >>> org.apache.axis2.transport.http.HTTPWorker.processRequest (
> HTTPWorker.java:226)
> >>>
> >>>
> >>> at
> >>>
> >>> org.apache.axis2.transport.http.server.SimpleConnectionThread.run(
> SimpleConnectionThread.java:92)
> >>>
> >>>
> >>> at
> >>>
> >>>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:650)
> >>>
> >>>
> >>> at
> >>>
> >>>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:675)
> >>>
> >>>
> >>> at java.lang.Thread.run(Thread.java :595)
> >>> </Exception>
> >>> </detail>
> >>> </soapenv:Fault>
> >>> </soapenv:Body>
> >>> </soapenv:Envelope>
> >>>
> >>> Does anybody knows why I am getting a NPE into CallbackReceiver ?
> >>> I tried to debug axis2 into eclipse but I never reached the
> >>> breakpoint I
> >>> put on the line 32...
> >>>
> >>> Can you help me please ?
> >>>
> >>> Thanks a lot for your answers.
> >>> Regards,
> >>> Charles
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> >>> <ma...@ws.apache.org>
> >>> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
> >>> <ma...@ws.apache.org>
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
> >>
> >>
> >>
> >
>
>
Re: [Fwd: Re: user guide example]
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Elodie,Charles,
Port 8080 which you set in the options object (using the setTo method), will
be reflected in the wsAddressing To address which goes within the SOAP
envelope.
The port 8070 which you set in the transport URL is used to derive the
transport address. I.e. even though the SOAP To address of the SOAP envelope
goes with the port 8080, in the transport level (for e.g. HTTP) the message
is sent to the port 8070. This is the feature of Axis2 that allows us to
send the message through the tcp monitor (where the tcpmonitor sends it to
the correct port - 8080).
Port 6060 is the default client listner port of Axis2. So Axis2 client start
a listner on this port. Any async response messages or RM control messages
that are comming from the server will come to this port. Unfortunately since
they are directly sent from the server to the client, you wont see them in
the tcp monitor.
First check weather you have confitured the server property. After doing
this the RMSampleService should be lister in the List Services page of
Axis2.
Then start a tcp mapping from the port 8070 to port 8080. (assuming tomcat
is running on the port 8080).
Now run the Sample clients.
Chamikara
On 6/13/06, Mancinelli Elodie <el...@bull.net> wrote:
>
> Hi,
>
> I have the same problem. I can access tomcat, the server met an internal
> error which stopped the request (error: HTTP/1.1 500 Internal Error
> Servlet).
>
> I search where the error can comes from and I have questions on the
> ports 8080,8070 and 6060. I don't understand the works of these? Con
> you explain me the difference between ports 8080, 8070 and 6060?
>
> Thanks for your time
>
> Regards,
> Elodie
>
>
> > Charles Souillard wrote:
> >
> > I just missed to tell you that traces from onComplete and onError
> > methods from TestCallBack class are never printed out.
> > Can you explain me how messages are managed inside sandesha ?
> > I put 8080 in the targetEPR, then 8070 in the TRANSPORT_URL and I get
> > 6060 in the message sent...
> > I am a bit confused about the routing of my message...
> > Thanks,
> > Charles
> >
> > Charles Souillard wrote:
> >
> >> Hi Chamikara,
> >>
> >> I have added the following option in my client :
> >> clientOptions.setProperty(MessageContextConstants.TRANSPORT_URL,"http://localhost:8070/axis2/services/RMSampleService
> ");
> >>
> >>
> >> It doesn't change my problem. I never got a response so I can not
> >> tell you if it is a 202 or 500 code.
> >> I am waiting for this information in the client coe. Is that right ?
> >> Or perhaps the Axis Engine is sending a message elsewhere ?
> >>
> >> I have followed all the steps described in the Sandesha User Guide
> >> and it is not working... Is it possible that my proxy is causing
> >> problems ? I do not have any other idea as it seems that this example
> >> should run I can't find any other user having problems on the web.
> >>
> >> Can you please help me or give me any stuff I can try to help me
> >> understanding what is going wrong.
> >>
> >> Thanks a lot
> >> Regards
> >> Charles
> >>
> >>
> >> Chamikara Jayalath wrote:
> >>
> >>> Hi Charles,
> >>>
> >>> The create sequence response message is sent directly to the port
> >>> 6060. So you wont see it in the tcp monitor. What is the HTTP
> >>> response to ur Create Sequence request message. is it 202 OK or 500.
> >>>
> >>> The reason for the NullPointer is Axis2 client side trying to get
> >>> the relatesTo value which is not present in the request you make
> >>> through the browser.
> >>>
> >>> Chamikara
> >>>
> >>>
> >>>
> >>> On 6/2/06, *Charles Souillard* <Charles.Souillard@ext.bull.net
> >>> <mailto: Charles.Souillard@ext.bull.net>> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I just sent a message on axis user list for a problem concenring
> >>> the use
> >>> of sandesha2.
> >>> I am trying to use the user-guide example but I am having problem
> >>> during
> >>> the creation of the first sequence.
> >>> In fact I never get the ack of the createSequence.
> >>>
> >>> I can give you hereafter the mail I sent to axis user list.
> >>>
> >>> Please help me on that problem.
> >>>
> >>> Regards,
> >>> Charles
> >>>
> >>>
> >>> Hi all,
> >>>
> >>> I am trying to use the same example.
> >>> I am encoutering the same problem. I have also caught the http
> >>> request
> >>> inside tcpmon.
> >>> You can find it hereafter :
> >>>
> >>> POST /axis2/services/RMSampleService HTTP/1.1
> >>> User-Agent: Axis2
> >>> SOAPAction:
> http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence
> >>> Host: localhost:13000
> >>> Transfer-Encoding: chunked
> >>> Content-Type: text/xml; charset=UTF-8
> >>>
> >>> 320
> >>> <?xml version='1.0' encoding='UTF-8'?>
> >>> <soapenv:Envelope
> >>> xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/"
> >>> xmlns:wsa="http://www.w3.org/2005/08/addressing
> >>> <http://www.w3.org/2005/08/addressing>">
> >>> <soapenv:Header>
> >>>
> >>> <wsa:To> http://localhost:13000/axis2/services/RMSampleService
> </wsa:To>
> >>> <wsa:ReplyTo>
> >>>
> >>> <wsa:Address>http://129.183.18.65:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__
> </wsa:Address>
> >>>
> >>>
> >>> </wsa:ReplyTo>
> >>>
> >>>
> <wsa:MessageID>urn:uuid:F568425CAF0692619511492482122053</wsa:MessageID>
> >>>
> >>> <wsa:Action>
> http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence
> >>>
> >>> < http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence
> ></wsa:Action>
> >>>
> >>> </soapenv:Header>
> >>> <soapenv:Body>
> >>> <wsrm:CreateSequence
> >>> xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
> >>> <wsrm:AcksTo>
> >>>
> >>> <wsa:Address> http://www.w3.org/2005/08/addressing/anonymous
> </wsa:Address>
> >>>
> >>> </wsrm:AcksTo>
> >>> </wsrm:CreateSequence>
> >>> </soapenv:Body>
> >>> </soapenv:Envelope>0
> >>>
> >>> I have entered the wsa adress into my web browser
> >>>
> >>> (http://129.183.18.65:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__
> >>>
> >>>
> >>> <http://129.183.18.65:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__
> >)
> >>>
> >>> and I get the following SOAP message :
> >>>
> >>> -
> >>> <soapenv:Envelope>
> >>> -
> >>> <soapenv:Header>
> >>> -
> >>> <wsa:ReplyTo>
> >>> <wsa:Address>
> >>> http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
> >>> </wsa:ReplyTo>
> >>>
> >>>
> <wsa:MessageID>urn:uuid:46BED3F8855DCCC1B2114924808940114</wsa:MessageID>
> >>>
> >>> <wsa:Action>
> >>> http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> >>> </soapenv:Header>
> >>> -
> >>> <soapenv:Body>
> >>> -
> >>> <soapenv:Fault>
> >>> <faultcode>soapenv:Client</faultcode>
> >>> <faultstring>unknown</faultstring>
> >>> -
> >>> <detail>
> >>> -
> >>> <Exception>
> >>> java.lang.NullPointerException
> >>> at
> >>>
> >>> org.apache.axis2.util.CallbackReceiver.receive(CallbackReceiver.java
> :32)
> >>>
> >>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
> >>> at
> >>>
> >>>
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPGetRequest(
> HTTPTransportUtils.java:138)
> >>>
> >>>
> >>> at
> >>>
> >>> org.apache.axis2.transport.http.HTTPWorker.processRequest (
> HTTPWorker.java:226)
> >>>
> >>>
> >>> at
> >>>
> >>> org.apache.axis2.transport.http.server.SimpleConnectionThread.run(
> SimpleConnectionThread.java:92)
> >>>
> >>>
> >>> at
> >>>
> >>>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:650)
> >>>
> >>>
> >>> at
> >>>
> >>>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:675)
> >>>
> >>>
> >>> at java.lang.Thread.run(Thread.java :595)
> >>> </Exception>
> >>> </detail>
> >>> </soapenv:Fault>
> >>> </soapenv:Body>
> >>> </soapenv:Envelope>
> >>>
> >>> Does anybody knows why I am getting a NPE into CallbackReceiver ?
> >>> I tried to debug axis2 into eclipse but I never reached the
> >>> breakpoint I
> >>> put on the line 32...
> >>>
> >>> Can you help me please ?
> >>>
> >>> Thanks a lot for your answers.
> >>> Regards,
> >>> Charles
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> >>> <ma...@ws.apache.org>
> >>> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
> >>> <ma...@ws.apache.org>
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
> >>
> >>
> >>
> >
>
>