I have performed some stress testing this weekend. One test is to kill
our database, which causes our HAPI code that ingests messages to fail.
Our strategy so far was simply to return a NACK, but we discovered that
the system that is sending us messages is taking ANY response as a
success indicator, thus swallowing the message and causing message loss.
The sending system expects the socket connection to simply be
terminated. We have tried a number of strategies such as:
- throwing an exception from the Application.processMessage() method
- returning NULL from the method
- implementing our own PipeParser and overriding the encode()
method to return "" when the message source was null
- etc....
All those strategies have failed because at the end of the day, the
sending system still receives something. Unfortunately, we are not able
to modify the sending system, and so, we have to fix this on our end and
we are not sure how to make HAPI simply drop the connection and not send
ANYTHING back.
Any advice?
Thank you,
------------------------------------------------------------------------
*Laurent Hasson*
Co-Founder, 360Fresh.com <https://360Fresh.com>
Cellphone: 646-283-2186
This email and any attachments thereto may contain private,
confidential, and privileged material for the sole use of the intended
recipient. Any review, copying, or distribution of this email (or any
attachments thereto) by others is strictly prohibited. If you are not
the intended recipient, please contact the sender immediately and
permanently delete the original and any copies of this email and any
attachments thereto.
------------------------------------------------------------------------------
Keep yourself connected to Go Parallel:
DESIGN Expert tips on starting your parallel project right.
http://goparallel.sourceforge.net/
_______________________________________________
Hl7api-devel mailing list
Hl7api-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
