lsalamon / nhin-d

Automatically exported from code.google.com/p/nhin-d
0 stars 0 forks source link

Java RI duplciation state for timely and reliable not working #196

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Send a message from HISP A to HISP B requesting timely and reliable messaging
2. The receiving HISP only sends the MDN processed message
3. The sending HISP times out due to not receiving the MDN processed message 
and sends a DSN failure message to the edge client.
4. The receiving HISP finally sends an MDN dispatched message, buy only after 
step 3 has completed.

What is the expected output? What do you see instead?
The sending HISP should "suppress" the dispatched MDN message and not delivery 
it to the edge client (in accordance to the delivery notification 
implementation guide).  Instead, the MDN dispatched message is being sent to 
the edge client.

This issue was discovered while executing the test scripts from the Direct Labs 
of Direct pilot toolkit.

Original issue reported on code.google.com by gm2...@cerner.com on 10 Dec 2012 at 4:22

GoogleCodeExporter commented 9 years ago
The issue has been verified in a test lab and debugger.  The root cause is due 
to an improper assertion of how the Camel aggregation pattern works when 
messages are timed out.  The aggreator removed the messages from the 
aggregation store before the DSN error message is sent.  When the DSN message 
is received by the message monitor, all context to the original message has 
been deleted, and the message is not properly added to the duplication store.

The solution will detect timeout conditions and add the message to the 
duplication store immediately upon timeout instead of waiting for the DSN 
failure message to be tracked (assuming that the message has requested the 
timely and reliable protocol).

Original comment by gm2...@cerner.com on 10 Dec 2012 at 4:25

GoogleCodeExporter commented 9 years ago
Issue resolved and tested internal test lab.  Need to retest with previous test 
partner and validate.

Original comment by gm2...@cerner.com on 13 Dec 2012 at 2:31

GoogleCodeExporter commented 9 years ago
Closing after testing with partner.

Original comment by gm2...@cerner.com on 25 Jun 2013 at 2:23