Skip to main content

[Question] Why a solo AckResuested from the client sometimes appears sometings not?

1 reply [Last post]
Anonymous

Hi Marek,

When we do Metro to Metro RequestReply-withMC scenarios,
we use exactly the same client and the same endpoint, run several times,
sometimes, the client sends solo AckResuested message, sometimes not.

For example,
sometimes, the messages go between client and server are:

1. CreateSequence Http202
2. MakeConnection CreateSequenceResponse
3. echo(with AckRequested) Http202
4. AckRequested Http202
5. MakeConnection echoResponse(with SequenceAcknowledgement and
AckRequested)
6. CloseSequence(with SequenceAcknowledgement) ......
7. ......

sometimes, the messages are:

1. CreateSequence Http202
2. MakeConnection CreateSequenceResponse
3. echo(with AckRequested) Http202
4. MakeConnection echoResponse(with SequenceAcknowledgement and
AckRequested)
5. CloseSequence(with SequenceAcknowledgement) ......
6. ......

The appearance of AckRequested message makes some of the test reports
contain failed assertions.

Will you please take a look at this issue?
Is it because we miss some specifications in our policy configuration?

Thank you very much!
[att1.html]

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Potociar Marek

Hi Xingrui,
standalone AckRequested messages are not against any specification
IMHO. Therefore I don't think it is correct that those scenarios fail
and probably it is the test that should be fixed.

Anyway, the standalone AckRequested messages are sent only if there
are unacknowledged messages and the interval between two standalone
AckRequested messages is controlled by a Metro-specific WS-Policy
assertion (default value is 2000 ms):

If you want to make sure that standalone AckRequested messages are
sent less frequently, you may try to increase the interval to a higher
value (e.g. 60000 ms should be enough).

Regards,
Marek

P.S. More info on RM configuration in Metro can be found on my blog[1]
or in the Metro user guide[2].

[1] http://marek.potociar.net/2009/11/23/metro-reliable-messaging-configurat...
[2] https://metro.dev.java.net/guide/Configurable_features_summary.html

On 7.1.2010, at 8:24, Xingrui Pei wrote:

> Hi Marek,
>
> When we do Metro to Metro RequestReply-withMC scenarios,
> we use exactly the same client and the same endpoint, run several
> times,
> sometimes, the client sends solo AckResuested message, sometimes not.
>
>
> For example,
> sometimes, the messages go between client and server are:
> CreateSequence Http202
> MakeConnection
> CreateSequenceResponse
> echo(with AckRequested) Http202
> AckRequested Http202
> MakeConnection
> echoResponse(with SequenceAcknowledgement and AckRequested)
> CloseSequence(with SequenceAcknowledgement) ......
> ......
> sometimes, the messages are:
> CreateSequence Http202
> MakeConnection
> CreateSequenceResponse
> echo(with AckRequested) Http202
> MakeConnection
> echoResponse(with SequenceAcknowledgement and AckRequested)
> CloseSequence(with SequenceAcknowledgement) ......
> ......
> The appearance of AckRequested message makes some of the test
> reports contain failed assertions.
>
>
> Will you please take a look at this issue?
> Is it because we miss some specifications in our policy configuration?
>
>
> Thank you very much!

[att1.html]