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 Benjamin Schmeling <Be...@gmx.de> on 2005/10/25 17:34:51 UTC
Sequence Identifier inconsistent?
Hi,
I'm a bit confused about the sequence identifiers and the order my
soapmonitor is showing the messages:
1. a createsequence is sent
2. the message to the called ws is sent with sequence element and
identifier
uuid:c12e71a0-4569-11da-84b9-bb6c79ed7b66
3. TerminateSequence is sent with id =
uuid:c12e71a0-4569-11da-84b9-bb6c79ed7b66
4. CreateSequenceResponse is sent with id =
uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
5. SequenceAknoledgement is sent with
uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
According to the specification, the CreateSequenceResponse carries the
Identifier for the created Sequence, but that differs:
c12e71a0-4569-11da-84b9-bb6c79ed7b66 !=
uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: Sequence Identifier inconsistent?
Posted by Benjamin Schmeling <Be...@gmx.de>.
It is a kind of request/response scenario. I have written a WS called
ReliabilityService with an operation AddExactlyOnceSemantics which takes
a String as an argument and returns this String again.
This ws is called in a reliable sequence with sandesha.
Why should there be two CreateSequence ?
I've added the full messages of my soap monitor as an attachement.
The relevant part of my server-config.wsdd is attached, too.
Thanks,
Benjamin
> Hi Benjamin,
>
> I think you are testing the request/response scenario (echo example)
> is this correct?
>
> If it is the case, then there are two create sequence messages that
> should appear in your soap monitor.
> One going from Client EPM to the server EPM before sending requests
> One from Sever EPM to the Client EPM before sending the responses.
>
> Check whether you are capturing all the messages in the communication.
> According to your configuration the CreateSequenceResponse for the
> first message may come in the same HTTP connection and you may have
> missed that in the SOAP monitor. Check this and let me know.
>
> Since we can see a terminate sequence with the correct Sequence ID I
> think those two messages corresponds to the first sequence and the
> last two corresponds to the second sequence that is used to send the
> responses.
>
> Configuring the SOAP monitor to capture all the messages is bit tricky
> and we normally use two SOAP monitors to check the request path and
> the response path.
>
> Let me know if this is not the case that you are experiencing.
>
> Thanks,
>
> Jaliya
>
>
> ----- Original Message ----- From: "Benjamin Schmeling"
> <Be...@gmx.de>
> To: <sa...@ws.apache.org>
> Sent: Tuesday, October 25, 2005 10:34 AM
> Subject: Sequence Identifier inconsistent?
>
>
>> Hi,
>>
>> I'm a bit confused about the sequence identifiers and the order my
>> soapmonitor is showing the messages:
>>
>> 1. a createsequence is sent
>> 2. the message to the called ws is sent with sequence element and
>> identifier uuid:c12e71a0-4569-11da-84b9-bb6c79ed7b66
>>
>> 3. TerminateSequence is sent with id =
>> uuid:c12e71a0-4569-11da-84b9-bb6c79ed7b66
>> 4. CreateSequenceResponse is sent with id =
>> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
>> 5. SequenceAknoledgement is sent with
>> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
>>
>> According to the specification, the CreateSequenceResponse carries
>> the Identifier for the created Sequence, but that differs:
>> c12e71a0-4569-11da-84b9-bb6c79ed7b66 !=
>> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
>>
>> Benjamin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>>
>>
>
>
>
Re: Sequence Identifier inconsistent?
Posted by Benjamin Schmeling <Be...@gmx.de>.
It is a kind of request/response scenario. I have written a WS called
ReliabilityService with an operation AddExactlyOnceSemantics which takes
a String as an argument and returns this String again.
This ws is called in a reliable sequence with sandesha.
Why should there be two CreateSequence ?
I've added the full messages of my soap monitor as an attachement.
The relevant part of my server-config.wsdd is attached, too.
Thanks,
Benjamin
> Hi Benjamin,
>
> I think you are testing the request/response scenario (echo example)
> is this correct?
>
> If it is the case, then there are two create sequence messages that
> should appear in your soap monitor.
> One going from Client EPM to the server EPM before sending requests
> One from Sever EPM to the Client EPM before sending the responses.
>
> Check whether you are capturing all the messages in the communication.
> According to your configuration the CreateSequenceResponse for the
> first message may come in the same HTTP connection and you may have
> missed that in the SOAP monitor. Check this and let me know.
>
> Since we can see a terminate sequence with the correct Sequence ID I
> think those two messages corresponds to the first sequence and the
> last two corresponds to the second sequence that is used to send the
> responses.
>
> Configuring the SOAP monitor to capture all the messages is bit tricky
> and we normally use two SOAP monitors to check the request path and
> the response path.
>
> Let me know if this is not the case that you are experiencing.
>
> Thanks,
>
> Jaliya
>
>
> ----- Original Message ----- From: "Benjamin Schmeling"
> <Be...@gmx.de>
> To: <sa...@ws.apache.org>
> Sent: Tuesday, October 25, 2005 10:34 AM
> Subject: Sequence Identifier inconsistent?
>
>
>> Hi,
>>
>> I'm a bit confused about the sequence identifiers and the order my
>> soapmonitor is showing the messages:
>>
>> 1. a createsequence is sent
>> 2. the message to the called ws is sent with sequence element and
>> identifier uuid:c12e71a0-4569-11da-84b9-bb6c79ed7b66
>>
>> 3. TerminateSequence is sent with id =
>> uuid:c12e71a0-4569-11da-84b9-bb6c79ed7b66
>> 4. CreateSequenceResponse is sent with id =
>> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
>> 5. SequenceAknoledgement is sent with
>> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
>>
>> According to the specification, the CreateSequenceResponse carries
>> the Identifier for the created Sequence, but that differs:
>> c12e71a0-4569-11da-84b9-bb6c79ed7b66 !=
>> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
>>
>> Benjamin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>>
>>
>
>
>
Re: Sequence Identifier inconsistent?
Posted by Jaliya Ekanayake <ja...@opensource.lk>.
Hi Benjamin,
I think you are testing the request/response scenario (echo example) is this
correct?
If it is the case, then there are two create sequence messages that should
appear in your soap monitor.
One going from Client EPM to the server EPM before sending requests
One from Sever EPM to the Client EPM before sending the responses.
Check whether you are capturing all the messages in the communication.
According to your configuration the CreateSequenceResponse for the first
message may come in the same HTTP connection and you may have missed that in
the SOAP monitor. Check this and let me know.
Since we can see a terminate sequence with the correct Sequence ID I think
those two messages corresponds to the first sequence and the last two
corresponds to the second sequence that is used to send the responses.
Configuring the SOAP monitor to capture all the messages is bit tricky and
we normally use two SOAP monitors to check the request path and the response
path.
Let me know if this is not the case that you are experiencing.
Thanks,
Jaliya
----- Original Message -----
From: "Benjamin Schmeling" <Be...@gmx.de>
To: <sa...@ws.apache.org>
Sent: Tuesday, October 25, 2005 10:34 AM
Subject: Sequence Identifier inconsistent?
> Hi,
>
> I'm a bit confused about the sequence identifiers and the order my
> soapmonitor is showing the messages:
>
> 1. a createsequence is sent
> 2. the message to the called ws is sent with sequence element and
> identifier uuid:c12e71a0-4569-11da-84b9-bb6c79ed7b66
>
> 3. TerminateSequence is sent with id =
> uuid:c12e71a0-4569-11da-84b9-bb6c79ed7b66
> 4. CreateSequenceResponse is sent with id =
> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
> 5. SequenceAknoledgement is sent with
> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
>
> According to the specification, the CreateSequenceResponse carries the
> Identifier for the created Sequence, but that differs:
> c12e71a0-4569-11da-84b9-bb6c79ed7b66 !=
> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
>
> Benjamin
>
> ---------------------------------------------------------------------
> 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: Sequence Identifier inconsistent?
Posted by Jaliya Ekanayake <ja...@opensource.lk>.
Hi Benjamin,
I think you are testing the request/response scenario (echo example) is this
correct?
If it is the case, then there are two create sequence messages that should
appear in your soap monitor.
One going from Client EPM to the server EPM before sending requests
One from Sever EPM to the Client EPM before sending the responses.
Check whether you are capturing all the messages in the communication.
According to your configuration the CreateSequenceResponse for the first
message may come in the same HTTP connection and you may have missed that in
the SOAP monitor. Check this and let me know.
Since we can see a terminate sequence with the correct Sequence ID I think
those two messages corresponds to the first sequence and the last two
corresponds to the second sequence that is used to send the responses.
Configuring the SOAP monitor to capture all the messages is bit tricky and
we normally use two SOAP monitors to check the request path and the response
path.
Let me know if this is not the case that you are experiencing.
Thanks,
Jaliya
----- Original Message -----
From: "Benjamin Schmeling" <Be...@gmx.de>
To: <sa...@ws.apache.org>
Sent: Tuesday, October 25, 2005 10:34 AM
Subject: Sequence Identifier inconsistent?
> Hi,
>
> I'm a bit confused about the sequence identifiers and the order my
> soapmonitor is showing the messages:
>
> 1. a createsequence is sent
> 2. the message to the called ws is sent with sequence element and
> identifier uuid:c12e71a0-4569-11da-84b9-bb6c79ed7b66
>
> 3. TerminateSequence is sent with id =
> uuid:c12e71a0-4569-11da-84b9-bb6c79ed7b66
> 4. CreateSequenceResponse is sent with id =
> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
> 5. SequenceAknoledgement is sent with
> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
>
> According to the specification, the CreateSequenceResponse carries the
> Identifier for the created Sequence, but that differs:
> c12e71a0-4569-11da-84b9-bb6c79ed7b66 !=
> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360
>
> Benjamin
>
> ---------------------------------------------------------------------
> 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