You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Wyn Easton <wy...@yahoo.com> on 2002/10/07 22:21:22 UTC
Catching a comm error
Hello:
This has probably been answered before. If there is
something in an archive, please point me there and
I'll read it.
I was wondering what happens if the SOAP response
never gets back to the client that invoked the SOAP
Call. In other words, the Java method that the SOAP
RPC router called returns, but the SOAP servlet never
gets to send the reply to the client. The client would
get a SOAP Fault, but does the service somehow get
informed that the client never got what was intended
to be returned? Can the web service register with the
SOAP servlet to be informed when the reply was not
returned to the client.
Thanks for your input.
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
Re: Catching a comm error
Posted by Wyn Easton <wy...@yahoo.com>.
Thanks for the input Mark.
In my situation it is the client that needs to know
what happened. We are sending XML documents and the
reply is also in an XML document. If the client gets
cut off before it can examine the XML, it does not
know
the result of the request.
I think I've got a solution, but any additional
comments on this type of problem would be welcomed.
--- Mark Childerson <ma...@childersoft.com> wrote:
> I think that you may be off track by having the
> client call and ask the
> server. Remember, in the client side code, the call
> will only complete
> without a SOAP fault if everything worked fine. So
> the client always knows
> whether the whole SOAP transaction worked or not.
> The real issue is whether
> the server (as opposed to the client) needs to know
> whether everything
> worked well. There is no really good solution to
> this problem. You can have
> the client contact the server after each successful
> request to say "Yes, I
> did receive the information", but then, of course,
> the acknowledgements
> could go astray, letting the server falsely believe
> in an error. You could
> also have the client tell the server "I got an
> error" in a separate SOAP
> call, but many connectivity errors will kill both
> SOAP calls, so that the
> server is never informed of the error.
>
> The gurus on the list can no doubt point you to lots
> of literature on this
> two-phase commit problem with distributed systems.
>
> Mark.
>
>
> At 02:34 PM 07/10/2002 -0700, you wrote:
> >I guess I better have a method exposed on my web
> >service that the client can call to ask about
> previous
> >requests or maybe retry the same request X times
> >before giving up. Anyway, I'll need to do something
> on
> >the client end. At least the client will get a SOAP
> >Fault indicating some sort of error happened.
> Thanks.
> >
> >--- Scott Nichol <sn...@scottnichol.com>
> wrote:
> > > There is no way for the service to know that a
> > > particular response has
> > > been successfully returned to the client.
> > >
> > > Note that even if the servlet writes all the
> output
> > > to the response
> > > stream without error, it cannot be certain that
> the
> > > client application
> > > receives it. In fact, I doubt you can even be
> sure
> > > that the data has
> > > made it past the Web server. The stream the
> servlet
> > > writes to is
> > > presumably read by the Web server, which in turn
> > > writes to the client
> > > (or, for that matter, some proxy the client
> request
> > > has passed through).
> > > Further, the lack of an error may not even mean
> the
> > > Web server has
> > > received the data. It probably just indicates
> that
> > > the TCP/IP stack has
> > > received the data on behalf of the Web server.
> > >
> > > Scott Nichol
> > >
> > > ----- Original Message -----
> > > From: "Wyn Easton" <wy...@yahoo.com>
> > > To: <so...@xml.apache.org>
> > > Sent: Monday, October 07, 2002 4:21 PM
> > > Subject: Catching a comm error
> > >
> > >
> > > > Hello:
> > > >
> > > > This has probably been answered before. If
> there
> > > is
> > > > something in an archive, please point me there
> and
> > > > I'll read it.
> > > >
> > > > I was wondering what happens if the SOAP
> response
> > > > never gets back to the client that invoked the
> > > SOAP
> > > > Call. In other words, the Java method that the
> > > SOAP
> > > > RPC router called returns, but the SOAP
> servlet
> > > never
> > > > gets to send the reply to the client. The
> client
> > > would
> > > > get a SOAP Fault, but does the service somehow
> get
> > > > informed that the client never got what was
> > > intended
> > > > to be returned? Can the web service register
> with
> > > the
> > > > SOAP servlet to be informed when the reply was
> not
> > > > returned to the client.
> > > > Thanks for your input.
> > > >
> > > >
> > > >
> > > >
> __________________________________________________
> > > > Do you Yahoo!?
> > > > Faith Hill - Exclusive Performances, Videos &
> More
> > > > http://faith.yahoo.com
> > > >
> > > > --
> > > > To unsubscribe, e-mail:
> > > <ma...@xml.apache.org>
> > > > For additional commands, e-mail:
> > > <ma...@xml.apache.org>
> > > >
> > > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > > <ma...@xml.apache.org>
> > > For additional commands, e-mail:
> > > <ma...@xml.apache.org>
> > >
> >
> >
> >__________________________________________________
> >Do you Yahoo!?
> >Faith Hill - Exclusive Performances, Videos & More
> >http://faith.yahoo.com
> >
> >--
> >To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> >For additional commands, e-mail:
> <ma...@xml.apache.org>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> For additional commands, e-mail:
> <ma...@xml.apache.org>
>
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
Re: Catching a comm error
Posted by Wyn Easton <wy...@yahoo.com>.
Thanks for the input Mark.
In my situation it is the client that needs to know
what happened. We are sending XML documents and the
reply is also in an XML document. If the client gets
cut off before it can examine the XML, it does not
know
the result of the request.
I think I've got a solution, but any additional
comments on this type of problem would be welcomed.
--- Mark Childerson <ma...@childersoft.com> wrote:
> I think that you may be off track by having the
> client call and ask the
> server. Remember, in the client side code, the call
> will only complete
> without a SOAP fault if everything worked fine. So
> the client always knows
> whether the whole SOAP transaction worked or not.
> The real issue is whether
> the server (as opposed to the client) needs to know
> whether everything
> worked well. There is no really good solution to
> this problem. You can have
> the client contact the server after each successful
> request to say "Yes, I
> did receive the information", but then, of course,
> the acknowledgements
> could go astray, letting the server falsely believe
> in an error. You could
> also have the client tell the server "I got an
> error" in a separate SOAP
> call, but many connectivity errors will kill both
> SOAP calls, so that the
> server is never informed of the error.
>
> The gurus on the list can no doubt point you to lots
> of literature on this
> two-phase commit problem with distributed systems.
>
> Mark.
>
>
> At 02:34 PM 07/10/2002 -0700, you wrote:
> >I guess I better have a method exposed on my web
> >service that the client can call to ask about
> previous
> >requests or maybe retry the same request X times
> >before giving up. Anyway, I'll need to do something
> on
> >the client end. At least the client will get a SOAP
> >Fault indicating some sort of error happened.
> Thanks.
> >
> >--- Scott Nichol <sn...@scottnichol.com>
> wrote:
> > > There is no way for the service to know that a
> > > particular response has
> > > been successfully returned to the client.
> > >
> > > Note that even if the servlet writes all the
> output
> > > to the response
> > > stream without error, it cannot be certain that
> the
> > > client application
> > > receives it. In fact, I doubt you can even be
> sure
> > > that the data has
> > > made it past the Web server. The stream the
> servlet
> > > writes to is
> > > presumably read by the Web server, which in turn
> > > writes to the client
> > > (or, for that matter, some proxy the client
> request
> > > has passed through).
> > > Further, the lack of an error may not even mean
> the
> > > Web server has
> > > received the data. It probably just indicates
> that
> > > the TCP/IP stack has
> > > received the data on behalf of the Web server.
> > >
> > > Scott Nichol
> > >
> > > ----- Original Message -----
> > > From: "Wyn Easton" <wy...@yahoo.com>
> > > To: <so...@xml.apache.org>
> > > Sent: Monday, October 07, 2002 4:21 PM
> > > Subject: Catching a comm error
> > >
> > >
> > > > Hello:
> > > >
> > > > This has probably been answered before. If
> there
> > > is
> > > > something in an archive, please point me there
> and
> > > > I'll read it.
> > > >
> > > > I was wondering what happens if the SOAP
> response
> > > > never gets back to the client that invoked the
> > > SOAP
> > > > Call. In other words, the Java method that the
> > > SOAP
> > > > RPC router called returns, but the SOAP
> servlet
> > > never
> > > > gets to send the reply to the client. The
> client
> > > would
> > > > get a SOAP Fault, but does the service somehow
> get
> > > > informed that the client never got what was
> > > intended
> > > > to be returned? Can the web service register
> with
> > > the
> > > > SOAP servlet to be informed when the reply was
> not
> > > > returned to the client.
> > > > Thanks for your input.
> > > >
> > > >
> > > >
> > > >
> __________________________________________________
> > > > Do you Yahoo!?
> > > > Faith Hill - Exclusive Performances, Videos &
> More
> > > > http://faith.yahoo.com
> > > >
> > > > --
> > > > To unsubscribe, e-mail:
> > > <ma...@xml.apache.org>
> > > > For additional commands, e-mail:
> > > <ma...@xml.apache.org>
> > > >
> > > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > > <ma...@xml.apache.org>
> > > For additional commands, e-mail:
> > > <ma...@xml.apache.org>
> > >
> >
> >
> >__________________________________________________
> >Do you Yahoo!?
> >Faith Hill - Exclusive Performances, Videos & More
> >http://faith.yahoo.com
> >
> >--
> >To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> >For additional commands, e-mail:
> <ma...@xml.apache.org>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> For additional commands, e-mail:
> <ma...@xml.apache.org>
>
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Catching a comm error
Posted by Mark Childerson <ma...@childersoft.com>.
I think that you may be off track by having the client call and ask the
server. Remember, in the client side code, the call will only complete
without a SOAP fault if everything worked fine. So the client always knows
whether the whole SOAP transaction worked or not. The real issue is whether
the server (as opposed to the client) needs to know whether everything
worked well. There is no really good solution to this problem. You can have
the client contact the server after each successful request to say "Yes, I
did receive the information", but then, of course, the acknowledgements
could go astray, letting the server falsely believe in an error. You could
also have the client tell the server "I got an error" in a separate SOAP
call, but many connectivity errors will kill both SOAP calls, so that the
server is never informed of the error.
The gurus on the list can no doubt point you to lots of literature on this
two-phase commit problem with distributed systems.
Mark.
At 02:34 PM 07/10/2002 -0700, you wrote:
>I guess I better have a method exposed on my web
>service that the client can call to ask about previous
>requests or maybe retry the same request X times
>before giving up. Anyway, I'll need to do something on
>the client end. At least the client will get a SOAP
>Fault indicating some sort of error happened. Thanks.
>
>--- Scott Nichol <sn...@scottnichol.com> wrote:
> > There is no way for the service to know that a
> > particular response has
> > been successfully returned to the client.
> >
> > Note that even if the servlet writes all the output
> > to the response
> > stream without error, it cannot be certain that the
> > client application
> > receives it. In fact, I doubt you can even be sure
> > that the data has
> > made it past the Web server. The stream the servlet
> > writes to is
> > presumably read by the Web server, which in turn
> > writes to the client
> > (or, for that matter, some proxy the client request
> > has passed through).
> > Further, the lack of an error may not even mean the
> > Web server has
> > received the data. It probably just indicates that
> > the TCP/IP stack has
> > received the data on behalf of the Web server.
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Wyn Easton" <wy...@yahoo.com>
> > To: <so...@xml.apache.org>
> > Sent: Monday, October 07, 2002 4:21 PM
> > Subject: Catching a comm error
> >
> >
> > > Hello:
> > >
> > > This has probably been answered before. If there
> > is
> > > something in an archive, please point me there and
> > > I'll read it.
> > >
> > > I was wondering what happens if the SOAP response
> > > never gets back to the client that invoked the
> > SOAP
> > > Call. In other words, the Java method that the
> > SOAP
> > > RPC router called returns, but the SOAP servlet
> > never
> > > gets to send the reply to the client. The client
> > would
> > > get a SOAP Fault, but does the service somehow get
> > > informed that the client never got what was
> > intended
> > > to be returned? Can the web service register with
> > the
> > > SOAP servlet to be informed when the reply was not
> > > returned to the client.
> > > Thanks for your input.
> > >
> > >
> > >
> > > __________________________________________________
> > > Do you Yahoo!?
> > > Faith Hill - Exclusive Performances, Videos & More
> > > http://faith.yahoo.com
> > >
> > > --
> > > To unsubscribe, e-mail:
> > <ma...@xml.apache.org>
> > > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@xml.apache.org>
> > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> >
>
>
>__________________________________________________
>Do you Yahoo!?
>Faith Hill - Exclusive Performances, Videos & More
>http://faith.yahoo.com
>
>--
>To unsubscribe, e-mail: <ma...@xml.apache.org>
>For additional commands, e-mail: <ma...@xml.apache.org>
Re: Catching a comm error
Posted by Mark Childerson <ma...@childersoft.com>.
I think that you may be off track by having the client call and ask the
server. Remember, in the client side code, the call will only complete
without a SOAP fault if everything worked fine. So the client always knows
whether the whole SOAP transaction worked or not. The real issue is whether
the server (as opposed to the client) needs to know whether everything
worked well. There is no really good solution to this problem. You can have
the client contact the server after each successful request to say "Yes, I
did receive the information", but then, of course, the acknowledgements
could go astray, letting the server falsely believe in an error. You could
also have the client tell the server "I got an error" in a separate SOAP
call, but many connectivity errors will kill both SOAP calls, so that the
server is never informed of the error.
The gurus on the list can no doubt point you to lots of literature on this
two-phase commit problem with distributed systems.
Mark.
At 02:34 PM 07/10/2002 -0700, you wrote:
>I guess I better have a method exposed on my web
>service that the client can call to ask about previous
>requests or maybe retry the same request X times
>before giving up. Anyway, I'll need to do something on
>the client end. At least the client will get a SOAP
>Fault indicating some sort of error happened. Thanks.
>
>--- Scott Nichol <sn...@scottnichol.com> wrote:
> > There is no way for the service to know that a
> > particular response has
> > been successfully returned to the client.
> >
> > Note that even if the servlet writes all the output
> > to the response
> > stream without error, it cannot be certain that the
> > client application
> > receives it. In fact, I doubt you can even be sure
> > that the data has
> > made it past the Web server. The stream the servlet
> > writes to is
> > presumably read by the Web server, which in turn
> > writes to the client
> > (or, for that matter, some proxy the client request
> > has passed through).
> > Further, the lack of an error may not even mean the
> > Web server has
> > received the data. It probably just indicates that
> > the TCP/IP stack has
> > received the data on behalf of the Web server.
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Wyn Easton" <wy...@yahoo.com>
> > To: <so...@xml.apache.org>
> > Sent: Monday, October 07, 2002 4:21 PM
> > Subject: Catching a comm error
> >
> >
> > > Hello:
> > >
> > > This has probably been answered before. If there
> > is
> > > something in an archive, please point me there and
> > > I'll read it.
> > >
> > > I was wondering what happens if the SOAP response
> > > never gets back to the client that invoked the
> > SOAP
> > > Call. In other words, the Java method that the
> > SOAP
> > > RPC router called returns, but the SOAP servlet
> > never
> > > gets to send the reply to the client. The client
> > would
> > > get a SOAP Fault, but does the service somehow get
> > > informed that the client never got what was
> > intended
> > > to be returned? Can the web service register with
> > the
> > > SOAP servlet to be informed when the reply was not
> > > returned to the client.
> > > Thanks for your input.
> > >
> > >
> > >
> > > __________________________________________________
> > > Do you Yahoo!?
> > > Faith Hill - Exclusive Performances, Videos & More
> > > http://faith.yahoo.com
> > >
> > > --
> > > To unsubscribe, e-mail:
> > <ma...@xml.apache.org>
> > > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@xml.apache.org>
> > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> >
>
>
>__________________________________________________
>Do you Yahoo!?
>Faith Hill - Exclusive Performances, Videos & More
>http://faith.yahoo.com
>
>--
>To unsubscribe, e-mail: <ma...@xml.apache.org>
>For additional commands, e-mail: <ma...@xml.apache.org>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Catching a comm error
Posted by Scott Nichol <sn...@scottnichol.com>.
If you really need a handshake, I think you are right to take the
approach of having your service expose that functionality.
Scott Nichol
----- Original Message -----
From: "Wyn Easton" <wy...@yahoo.com>
To: <so...@xml.apache.org>
Sent: Monday, October 07, 2002 5:34 PM
Subject: Re: Catching a comm error
> I guess I better have a method exposed on my web
> service that the client can call to ask about previous
> requests or maybe retry the same request X times
> before giving up. Anyway, I'll need to do something on
> the client end. At least the client will get a SOAP
> Fault indicating some sort of error happened. Thanks.
>
> --- Scott Nichol <sn...@scottnichol.com> wrote:
> > There is no way for the service to know that a
> > particular response has
> > been successfully returned to the client.
> >
> > Note that even if the servlet writes all the output
> > to the response
> > stream without error, it cannot be certain that the
> > client application
> > receives it. In fact, I doubt you can even be sure
> > that the data has
> > made it past the Web server. The stream the servlet
> > writes to is
> > presumably read by the Web server, which in turn
> > writes to the client
> > (or, for that matter, some proxy the client request
> > has passed through).
> > Further, the lack of an error may not even mean the
> > Web server has
> > received the data. It probably just indicates that
> > the TCP/IP stack has
> > received the data on behalf of the Web server.
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Wyn Easton" <wy...@yahoo.com>
> > To: <so...@xml.apache.org>
> > Sent: Monday, October 07, 2002 4:21 PM
> > Subject: Catching a comm error
> >
> >
> > > Hello:
> > >
> > > This has probably been answered before. If there
> > is
> > > something in an archive, please point me there and
> > > I'll read it.
> > >
> > > I was wondering what happens if the SOAP response
> > > never gets back to the client that invoked the
> > SOAP
> > > Call. In other words, the Java method that the
> > SOAP
> > > RPC router called returns, but the SOAP servlet
> > never
> > > gets to send the reply to the client. The client
> > would
> > > get a SOAP Fault, but does the service somehow get
> > > informed that the client never got what was
> > intended
> > > to be returned? Can the web service register with
> > the
> > > SOAP servlet to be informed when the reply was not
> > > returned to the client.
> > > Thanks for your input.
> > >
> > >
> > >
> > > __________________________________________________
> > > Do you Yahoo!?
> > > Faith Hill - Exclusive Performances, Videos & More
> > > http://faith.yahoo.com
> > >
> > > --
> > > To unsubscribe, e-mail:
> > <ma...@xml.apache.org>
> > > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@xml.apache.org>
> > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> >
>
>
> __________________________________________________
> Do you Yahoo!?
> Faith Hill - Exclusive Performances, Videos & More
> http://faith.yahoo.com
>
> --
> To unsubscribe, e-mail:
<ma...@xml.apache.org>
> For additional commands, e-mail:
<ma...@xml.apache.org>
>
>
Re: Catching a comm error
Posted by Scott Nichol <sn...@scottnichol.com>.
If you really need a handshake, I think you are right to take the
approach of having your service expose that functionality.
Scott Nichol
----- Original Message -----
From: "Wyn Easton" <wy...@yahoo.com>
To: <so...@xml.apache.org>
Sent: Monday, October 07, 2002 5:34 PM
Subject: Re: Catching a comm error
> I guess I better have a method exposed on my web
> service that the client can call to ask about previous
> requests or maybe retry the same request X times
> before giving up. Anyway, I'll need to do something on
> the client end. At least the client will get a SOAP
> Fault indicating some sort of error happened. Thanks.
>
> --- Scott Nichol <sn...@scottnichol.com> wrote:
> > There is no way for the service to know that a
> > particular response has
> > been successfully returned to the client.
> >
> > Note that even if the servlet writes all the output
> > to the response
> > stream without error, it cannot be certain that the
> > client application
> > receives it. In fact, I doubt you can even be sure
> > that the data has
> > made it past the Web server. The stream the servlet
> > writes to is
> > presumably read by the Web server, which in turn
> > writes to the client
> > (or, for that matter, some proxy the client request
> > has passed through).
> > Further, the lack of an error may not even mean the
> > Web server has
> > received the data. It probably just indicates that
> > the TCP/IP stack has
> > received the data on behalf of the Web server.
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Wyn Easton" <wy...@yahoo.com>
> > To: <so...@xml.apache.org>
> > Sent: Monday, October 07, 2002 4:21 PM
> > Subject: Catching a comm error
> >
> >
> > > Hello:
> > >
> > > This has probably been answered before. If there
> > is
> > > something in an archive, please point me there and
> > > I'll read it.
> > >
> > > I was wondering what happens if the SOAP response
> > > never gets back to the client that invoked the
> > SOAP
> > > Call. In other words, the Java method that the
> > SOAP
> > > RPC router called returns, but the SOAP servlet
> > never
> > > gets to send the reply to the client. The client
> > would
> > > get a SOAP Fault, but does the service somehow get
> > > informed that the client never got what was
> > intended
> > > to be returned? Can the web service register with
> > the
> > > SOAP servlet to be informed when the reply was not
> > > returned to the client.
> > > Thanks for your input.
> > >
> > >
> > >
> > > __________________________________________________
> > > Do you Yahoo!?
> > > Faith Hill - Exclusive Performances, Videos & More
> > > http://faith.yahoo.com
> > >
> > > --
> > > To unsubscribe, e-mail:
> > <ma...@xml.apache.org>
> > > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@xml.apache.org>
> > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> >
>
>
> __________________________________________________
> Do you Yahoo!?
> Faith Hill - Exclusive Performances, Videos & More
> http://faith.yahoo.com
>
> --
> To unsubscribe, e-mail:
<ma...@xml.apache.org>
> For additional commands, e-mail:
<ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Catching a comm error
Posted by Wyn Easton <wy...@yahoo.com>.
I guess I better have a method exposed on my web
service that the client can call to ask about previous
requests or maybe retry the same request X times
before giving up. Anyway, I'll need to do something on
the client end. At least the client will get a SOAP
Fault indicating some sort of error happened. Thanks.
--- Scott Nichol <sn...@scottnichol.com> wrote:
> There is no way for the service to know that a
> particular response has
> been successfully returned to the client.
>
> Note that even if the servlet writes all the output
> to the response
> stream without error, it cannot be certain that the
> client application
> receives it. In fact, I doubt you can even be sure
> that the data has
> made it past the Web server. The stream the servlet
> writes to is
> presumably read by the Web server, which in turn
> writes to the client
> (or, for that matter, some proxy the client request
> has passed through).
> Further, the lack of an error may not even mean the
> Web server has
> received the data. It probably just indicates that
> the TCP/IP stack has
> received the data on behalf of the Web server.
>
> Scott Nichol
>
> ----- Original Message -----
> From: "Wyn Easton" <wy...@yahoo.com>
> To: <so...@xml.apache.org>
> Sent: Monday, October 07, 2002 4:21 PM
> Subject: Catching a comm error
>
>
> > Hello:
> >
> > This has probably been answered before. If there
> is
> > something in an archive, please point me there and
> > I'll read it.
> >
> > I was wondering what happens if the SOAP response
> > never gets back to the client that invoked the
> SOAP
> > Call. In other words, the Java method that the
> SOAP
> > RPC router called returns, but the SOAP servlet
> never
> > gets to send the reply to the client. The client
> would
> > get a SOAP Fault, but does the service somehow get
> > informed that the client never got what was
> intended
> > to be returned? Can the web service register with
> the
> > SOAP servlet to be informed when the reply was not
> > returned to the client.
> > Thanks for your input.
> >
> >
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Faith Hill - Exclusive Performances, Videos & More
> > http://faith.yahoo.com
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> > For additional commands, e-mail:
> <ma...@xml.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> For additional commands, e-mail:
> <ma...@xml.apache.org>
>
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
Re: Catching a comm error
Posted by Wyn Easton <wy...@yahoo.com>.
I guess I better have a method exposed on my web
service that the client can call to ask about previous
requests or maybe retry the same request X times
before giving up. Anyway, I'll need to do something on
the client end. At least the client will get a SOAP
Fault indicating some sort of error happened. Thanks.
--- Scott Nichol <sn...@scottnichol.com> wrote:
> There is no way for the service to know that a
> particular response has
> been successfully returned to the client.
>
> Note that even if the servlet writes all the output
> to the response
> stream without error, it cannot be certain that the
> client application
> receives it. In fact, I doubt you can even be sure
> that the data has
> made it past the Web server. The stream the servlet
> writes to is
> presumably read by the Web server, which in turn
> writes to the client
> (or, for that matter, some proxy the client request
> has passed through).
> Further, the lack of an error may not even mean the
> Web server has
> received the data. It probably just indicates that
> the TCP/IP stack has
> received the data on behalf of the Web server.
>
> Scott Nichol
>
> ----- Original Message -----
> From: "Wyn Easton" <wy...@yahoo.com>
> To: <so...@xml.apache.org>
> Sent: Monday, October 07, 2002 4:21 PM
> Subject: Catching a comm error
>
>
> > Hello:
> >
> > This has probably been answered before. If there
> is
> > something in an archive, please point me there and
> > I'll read it.
> >
> > I was wondering what happens if the SOAP response
> > never gets back to the client that invoked the
> SOAP
> > Call. In other words, the Java method that the
> SOAP
> > RPC router called returns, but the SOAP servlet
> never
> > gets to send the reply to the client. The client
> would
> > get a SOAP Fault, but does the service somehow get
> > informed that the client never got what was
> intended
> > to be returned? Can the web service register with
> the
> > SOAP servlet to be informed when the reply was not
> > returned to the client.
> > Thanks for your input.
> >
> >
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Faith Hill - Exclusive Performances, Videos & More
> > http://faith.yahoo.com
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> > For additional commands, e-mail:
> <ma...@xml.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> For additional commands, e-mail:
> <ma...@xml.apache.org>
>
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Catching a comm error
Posted by Scott Nichol <sn...@scottnichol.com>.
There is no way for the service to know that a particular response has
been successfully returned to the client.
Note that even if the servlet writes all the output to the response
stream without error, it cannot be certain that the client application
receives it. In fact, I doubt you can even be sure that the data has
made it past the Web server. The stream the servlet writes to is
presumably read by the Web server, which in turn writes to the client
(or, for that matter, some proxy the client request has passed through).
Further, the lack of an error may not even mean the Web server has
received the data. It probably just indicates that the TCP/IP stack has
received the data on behalf of the Web server.
Scott Nichol
----- Original Message -----
From: "Wyn Easton" <wy...@yahoo.com>
To: <so...@xml.apache.org>
Sent: Monday, October 07, 2002 4:21 PM
Subject: Catching a comm error
> Hello:
>
> This has probably been answered before. If there is
> something in an archive, please point me there and
> I'll read it.
>
> I was wondering what happens if the SOAP response
> never gets back to the client that invoked the SOAP
> Call. In other words, the Java method that the SOAP
> RPC router called returns, but the SOAP servlet never
> gets to send the reply to the client. The client would
> get a SOAP Fault, but does the service somehow get
> informed that the client never got what was intended
> to be returned? Can the web service register with the
> SOAP servlet to be informed when the reply was not
> returned to the client.
> Thanks for your input.
>
>
>
> __________________________________________________
> Do you Yahoo!?
> Faith Hill - Exclusive Performances, Videos & More
> http://faith.yahoo.com
>
> --
> To unsubscribe, e-mail:
<ma...@xml.apache.org>
> For additional commands, e-mail:
<ma...@xml.apache.org>
>
>
Re: Catching a comm error
Posted by Scott Nichol <sn...@scottnichol.com>.
There is no way for the service to know that a particular response has
been successfully returned to the client.
Note that even if the servlet writes all the output to the response
stream without error, it cannot be certain that the client application
receives it. In fact, I doubt you can even be sure that the data has
made it past the Web server. The stream the servlet writes to is
presumably read by the Web server, which in turn writes to the client
(or, for that matter, some proxy the client request has passed through).
Further, the lack of an error may not even mean the Web server has
received the data. It probably just indicates that the TCP/IP stack has
received the data on behalf of the Web server.
Scott Nichol
----- Original Message -----
From: "Wyn Easton" <wy...@yahoo.com>
To: <so...@xml.apache.org>
Sent: Monday, October 07, 2002 4:21 PM
Subject: Catching a comm error
> Hello:
>
> This has probably been answered before. If there is
> something in an archive, please point me there and
> I'll read it.
>
> I was wondering what happens if the SOAP response
> never gets back to the client that invoked the SOAP
> Call. In other words, the Java method that the SOAP
> RPC router called returns, but the SOAP servlet never
> gets to send the reply to the client. The client would
> get a SOAP Fault, but does the service somehow get
> informed that the client never got what was intended
> to be returned? Can the web service register with the
> SOAP servlet to be informed when the reply was not
> returned to the client.
> Thanks for your input.
>
>
>
> __________________________________________________
> Do you Yahoo!?
> Faith Hill - Exclusive Performances, Videos & More
> http://faith.yahoo.com
>
> --
> To unsubscribe, e-mail:
<ma...@xml.apache.org>
> For additional commands, e-mail:
<ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>