You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by Tomas Varsavsky <tv...@thoughtworks.com> on 2006/05/13 11:28:31 UTC
Problem: not getting acks
Hi All,
I've been tearing my hair out on this all day. I'm about ready to give up.
Any help would be greatly appreciated.
Basically the problem is that I can't seem to get my service with RM to
send any Acks. I'm using the sample service & clients provided with the
Sandesha distribution. I've hooked in the SOAP monitor in order to see
messages between the client and server. I've set up Axis 1.0 and Sandesha
1.0 on Tomcat 5.5 as per the tutorial on the user guide, which says:
>Getting Acknowledgements and Faults to a Given Endpoint
>In the default configuration, response path for acknowledgements and
faults related to a sequence is the anonymous endpoint. For example, HTTP
transport
>will send acknowledgements and faults in the HTTP response of request
messages.
I believe this is saying that If I don't set the AcksTo property, the acks
should come to the caller in the response.
In the protocol trace from SOAP monitor, I can see the sequence being
created and the ping messages from the client to the server but no acks.
If I get the outgoingSequenceReport, it shows that none of my messages
have completed. If I force an ack request via
SandeshaClient.sendAckRequest(), the server doesn't respond.
Any ideas? Thanks in advance.
Reagards,
Tomas Varsavsky
ThoughtWorks Australia
Re: Problem: not getting acks
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Tomas,
Yes. As explained in the user guide, if u do not set the AcksTo value it
will be set to the anonymous EPR. There is no need to call the
SandeshaClient.sendAckRequest () method in this scenario.
Sandesha2 sends acknowledgements to the AcksTo Address which is sent within
the Create Sequence message. What is the acksTo value u observe in the tcp
monitor.
Also what is the response to your Ping message. Is it a fault, or is it 202
OK.
It would be helpful if you can send the messages u observer in the tcp
monitor. (And your client code, if it is different from the one provided in
the user guide).
Chamikara
On 5/13/06, Tomas Varsavsky <tv...@thoughtworks.com> wrote:
>
>
> Hi All,
>
> I've been tearing my hair out on this all day. I'm about ready to give up.
> Any help would be greatly appreciated.
>
> Basically the problem is that I can't seem to get my service with RM to
> send any Acks. I'm using the sample service & clients provided with the
> Sandesha distribution. I've hooked in the SOAP monitor in order to see
> messages between the client and server. I've set up Axis 1.0 and Sandesha
> 1.0 on Tomcat 5.5 as per the tutorial on the user guide, which says:
>
> *>Getting Acknowledgements and Faults to a Given Endpoint*
>
> *>In the default configuration, response path for acknowledgements and
> faults related to a sequence is the anonymous endpoint. For example, HTTP
> transport *
>
> *>will send acknowledgements and faults in the HTTP response of request
> messages. *
>
> I believe this is saying that If I don't set the AcksTo property, the acks
> should come to the caller in the response.
>
> In the protocol trace from SOAP monitor, I can see the sequence being
> created and the ping messages from the client to the server but no acks. If
> I get the outgoingSequenceReport, it shows that none of my messages have
> completed. If I force an ack request via SandeshaClient.sendAckRequest(),
> the server doesn't respond.
>
> Any ideas? Thanks in advance.
>
> Reagards,
>
> Tomas Varsavsky
> ThoughtWorks Australia
>
>
Re: Problem: not getting acks
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Tomas,
Yes. As explained in the user guide, if u do not set the AcksTo value it
will be set to the anonymous EPR. There is no need to call the
SandeshaClient.sendAckRequest () method in this scenario.
Sandesha2 sends acknowledgements to the AcksTo Address which is sent within
the Create Sequence message. What is the acksTo value u observe in the tcp
monitor.
Also what is the response to your Ping message. Is it a fault, or is it 202
OK.
It would be helpful if you can send the messages u observer in the tcp
monitor. (And your client code, if it is different from the one provided in
the user guide).
Chamikara
On 5/13/06, Tomas Varsavsky <tv...@thoughtworks.com> wrote:
>
>
> Hi All,
>
> I've been tearing my hair out on this all day. I'm about ready to give up.
> Any help would be greatly appreciated.
>
> Basically the problem is that I can't seem to get my service with RM to
> send any Acks. I'm using the sample service & clients provided with the
> Sandesha distribution. I've hooked in the SOAP monitor in order to see
> messages between the client and server. I've set up Axis 1.0 and Sandesha
> 1.0 on Tomcat 5.5 as per the tutorial on the user guide, which says:
>
> *>Getting Acknowledgements and Faults to a Given Endpoint*
>
> *>In the default configuration, response path for acknowledgements and
> faults related to a sequence is the anonymous endpoint. For example, HTTP
> transport *
>
> *>will send acknowledgements and faults in the HTTP response of request
> messages. *
>
> I believe this is saying that If I don't set the AcksTo property, the acks
> should come to the caller in the response.
>
> In the protocol trace from SOAP monitor, I can see the sequence being
> created and the ping messages from the client to the server but no acks. If
> I get the outgoingSequenceReport, it shows that none of my messages have
> completed. If I force an ack request via SandeshaClient.sendAckRequest(),
> the server doesn't respond.
>
> Any ideas? Thanks in advance.
>
> Reagards,
>
> Tomas Varsavsky
> ThoughtWorks Australia
>
>