<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 13: ACK leads to indefinite loop of sending messages</title><link href="https://sourceforge.net/p/hl7socketreader/bugs/13/" rel="alternate"/><link href="https://sourceforge.net/p/hl7socketreader/bugs/13/feed.atom" rel="self"/><id>https://sourceforge.net/p/hl7socketreader/bugs/13/</id><updated>2015-12-21T15:42:31.470000Z</updated><subtitle>Recent changes to 13: ACK leads to indefinite loop of sending messages</subtitle><entry><title>ACK leads to indefinite loop of sending messages</title><link href="https://sourceforge.net/p/hl7socketreader/bugs/13/" rel="alternate"/><published>2015-12-21T15:42:31.470000Z</published><updated>2015-12-21T15:42:31.470000Z</updated><author><name>Linus Betschart</name><uri>https://sourceforge.net/u/linusbetschart/</uri></author><id>https://sourceforge.net53b476f55e275a4b8158cf42bd948fa3fe07dd82</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;if you have multiple Out-Sockets which deliver the very same HL7 message, after the first successfull ACK the self.messageCtrlId is going to be set to None. This leads to the problem that the next ACK can not be handled anymore as it compares to None instead to the actual message ID. This leads to an indefinite loop of sending the very same HL7 message over and over again.&lt;/p&gt;
&lt;p&gt;To fix this, comment line 1249 of workerThreads.py out (#self._ _messageCtrlId = None)&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>