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 David <ds...@yahoo.com> on 2007/06/20 23:46:40 UTC
[Axis2] Interop with gSOAP - AxisFault: The server localhost failed to respond - calling void method
Hello,
I'm developing an app using gSOAP (C++) on the server
and Axis2-Java on the client. I have a SOAP call that
with a signature of "void myMethod(String)".
After gSOAP gets this call and processes the method,
it simply closes the socket. When I do a similar test
implementing a void-returning method using *Axis* on
the server, it instead returns an HTTP header (and
nothing else), which is apparently what the Axis
client code wants.
My problem, of course, is that I need to use gSOAP on
the server and Axis on the client, but the Axis client
chokes on the fact that the server closes the socket
for calls that return void (rather than returning an
HTTP response):
org.apache.axis2.AxisFault: The server localhost
failed to respond
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:221)
at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452)
at
org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyAxisOperation.java:255)
[...]
Looks like we may have differing interpretations of
some spec (or lack of a clear spec). In any case,
does anyone know how I can fix this?
Thanks,
David
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Interop with gSOAP - AxisFault: The server localhost failed to respond - calling void method
Posted by David <ds...@yahoo.com>.
Thanks for the info; I'll pass it along.
David
--- Anne Thomas Manes <at...@gmail.com> wrote:
> Here are two references to cite:
>
> WS-I Basic Profile [1]
>
> 3.4.4 HTTP Success Status Codes
>
> HTTP uses the 2xx series of status codes to
> communicate success. In
> particular, 200 is the default for successful
> messages, but 202 can be
> used to indicate that a message has been submitted
> for processing.
> Additionally, other 2xx status codes may be
> appropriate, depending on
> the nature of the HTTP interaction.
>
> R1124 An INSTANCE MUST use a 2xx HTTP status code on
> a response
> message that indicates the successful outcome of a
> HTTP request.
>
> R1111 An INSTANCE SHOULD use a "200 OK" HTTP status
> code on a response
> message that contains an envelope that is not a
> fault.
>
> R1112 An INSTANCE SHOULD use either a "200 OK" or
> "202 Accepted" HTTP
> status code for a response message that does not
> contain a SOAP
> envelope but indicates the successful outcome of a
> HTTP request.
>
> Despite the fact that the HTTP 1.1 assigns different
> meanings to
> response status codes "200" and "202", in the
> context of the Profile
> they should be considered equivalent by the
> initiator of the request.
> The Profile accepts both status codes because some
> SOAP
> implementations have little control over the HTTP
> protocol
> implementation and cannot control which of these
> response status codes
> is sent.
>
> HTTP 1.1 specification (RFC 2616) Section 9.5 [2]:
>
> The action performed by the POST method might not
> result in a resource
> that can be identified by a URI. In this case,
> either 200 (OK) or 204
> (No Content) is the appropriate response status,
> depending on whether
> or not the response includes an entity that
> describes the result.
>
> If a resource has been created on the origin server,
> the response
> SHOULD be 201 (Created) and contain an entity which
> describes the
> status of the request and refers to the new
> resource, and a Location
> header (see section 14.30).
>
> [1]
>
http://www.ws-i.org/Profiles/BasicProfile-1.1.html#SOAPHTTP
> [2]
>
http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html
>
> Anne
>
> On 6/20/07, Anne Thomas Manes <at...@gmail.com>
> wrote:
> > An HTTP POST should always return an HTTP
> response. This is a bug in gSOAP.
> >
> > Anne
> >
> > On 6/20/07, David <ds...@yahoo.com> wrote:
> > > Hello,
> > >
> > > I'm developing an app using gSOAP (C++) on the
> server
> > > and Axis2-Java on the client. I have a SOAP
> call that
> > > with a signature of "void myMethod(String)".
> > >
> > > After gSOAP gets this call and processes the
> method,
> > > it simply closes the socket. When I do a
> similar test
> > > implementing a void-returning method using
> *Axis* on
> > > the server, it instead returns an HTTP header
> (and
> > > nothing else), which is apparently what the Axis
> > > client code wants.
> > >
> > > My problem, of course, is that I need to use
> gSOAP on
> > > the server and Axis on the client, but the Axis
> client
> > > chokes on the fact that the server closes the
> socket
> > > for calls that return void (rather than
> returning an
> > > HTTP response):
> > >
> > > org.apache.axis2.AxisFault: The server localhost
> > > failed to respond
> > > at
> > >
>
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:221)
> > > at
> > >
>
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452)
> > > at
> > >
>
org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyAxisOperation.java:255)
> > > [...]
> > >
> > > Looks like we may have differing interpretations
> of
> > > some spec (or lack of a clear spec). In any
> case,
> > > does anyone know how I can fix this?
> > >
> > > Thanks,
> > > David
> > >
> > >
> > >
> > >
> > >
>
____________________________________________________________________________________
> > > Pinpoint customers who are looking for what you
> sell.
> > > http://searchmarketing.yahoo.com/
> > >
> > >
>
---------------------------------------------------------------------
> > > 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
>
>
____________________________________________________________________________________
Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Interop with gSOAP - AxisFault: The server localhost failed to respond - calling void method
Posted by Anne Thomas Manes <at...@gmail.com>.
Here are two references to cite:
WS-I Basic Profile [1]
3.4.4 HTTP Success Status Codes
HTTP uses the 2xx series of status codes to communicate success. In
particular, 200 is the default for successful messages, but 202 can be
used to indicate that a message has been submitted for processing.
Additionally, other 2xx status codes may be appropriate, depending on
the nature of the HTTP interaction.
R1124 An INSTANCE MUST use a 2xx HTTP status code on a response
message that indicates the successful outcome of a HTTP request.
R1111 An INSTANCE SHOULD use a "200 OK" HTTP status code on a response
message that contains an envelope that is not a fault.
R1112 An INSTANCE SHOULD use either a "200 OK" or "202 Accepted" HTTP
status code for a response message that does not contain a SOAP
envelope but indicates the successful outcome of a HTTP request.
Despite the fact that the HTTP 1.1 assigns different meanings to
response status codes "200" and "202", in the context of the Profile
they should be considered equivalent by the initiator of the request.
The Profile accepts both status codes because some SOAP
implementations have little control over the HTTP protocol
implementation and cannot control which of these response status codes
is sent.
HTTP 1.1 specification (RFC 2616) Section 9.5 [2]:
The action performed by the POST method might not result in a resource
that can be identified by a URI. In this case, either 200 (OK) or 204
(No Content) is the appropriate response status, depending on whether
or not the response includes an entity that describes the result.
If a resource has been created on the origin server, the response
SHOULD be 201 (Created) and contain an entity which describes the
status of the request and refers to the new resource, and a Location
header (see section 14.30).
[1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#SOAPHTTP
[2] http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html
Anne
On 6/20/07, Anne Thomas Manes <at...@gmail.com> wrote:
> An HTTP POST should always return an HTTP response. This is a bug in gSOAP.
>
> Anne
>
> On 6/20/07, David <ds...@yahoo.com> wrote:
> > Hello,
> >
> > I'm developing an app using gSOAP (C++) on the server
> > and Axis2-Java on the client. I have a SOAP call that
> > with a signature of "void myMethod(String)".
> >
> > After gSOAP gets this call and processes the method,
> > it simply closes the socket. When I do a similar test
> > implementing a void-returning method using *Axis* on
> > the server, it instead returns an HTTP header (and
> > nothing else), which is apparently what the Axis
> > client code wants.
> >
> > My problem, of course, is that I need to use gSOAP on
> > the server and Axis on the client, but the Axis client
> > chokes on the fact that the server closes the socket
> > for calls that return void (rather than returning an
> > HTTP response):
> >
> > org.apache.axis2.AxisFault: The server localhost
> > failed to respond
> > at
> > org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:221)
> > at
> > org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452)
> > at
> > org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyAxisOperation.java:255)
> > [...]
> >
> > Looks like we may have differing interpretations of
> > some spec (or lack of a clear spec). In any case,
> > does anyone know how I can fix this?
> >
> > Thanks,
> > David
> >
> >
> >
> >
> > ____________________________________________________________________________________
> > Pinpoint customers who are looking for what you sell.
> > http://searchmarketing.yahoo.com/
> >
> > ---------------------------------------------------------------------
> > 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
Re: [Axis2] Interop with gSOAP - AxisFault: The server localhost failed to respond - calling void method
Posted by Anne Thomas Manes <at...@gmail.com>.
An HTTP POST should always return an HTTP response. This is a bug in gSOAP.
Anne
On 6/20/07, David <ds...@yahoo.com> wrote:
> Hello,
>
> I'm developing an app using gSOAP (C++) on the server
> and Axis2-Java on the client. I have a SOAP call that
> with a signature of "void myMethod(String)".
>
> After gSOAP gets this call and processes the method,
> it simply closes the socket. When I do a similar test
> implementing a void-returning method using *Axis* on
> the server, it instead returns an HTTP header (and
> nothing else), which is apparently what the Axis
> client code wants.
>
> My problem, of course, is that I need to use gSOAP on
> the server and Axis on the client, but the Axis client
> chokes on the fact that the server closes the socket
> for calls that return void (rather than returning an
> HTTP response):
>
> org.apache.axis2.AxisFault: The server localhost
> failed to respond
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:221)
> at
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452)
> at
> org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyAxisOperation.java:255)
> [...]
>
> Looks like we may have differing interpretations of
> some spec (or lack of a clear spec). In any case,
> does anyone know how I can fix this?
>
> Thanks,
> David
>
>
>
>
> ____________________________________________________________________________________
> Pinpoint customers who are looking for what you sell.
> http://searchmarketing.yahoo.com/
>
> ---------------------------------------------------------------------
> 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