[
https://issues.apache.org/jira/browse/QPID-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke updated QPID-2967:
------------------------------
Attachment: QPID-2967.patch
Comparing a linux broker to the windows broker the missing state trigger is
revealed.
In Linux [that works] the AsynchIOHandler calls (ignoring a ton of noise)
idle - eof - disconnect
In Windows [that fails] the same set of calls are
idle - disconnect
This patch adds the call to "eof". With the EOF callback the system behaves
itself better.
Any comments would be appreciated. I'll also move the discussion to ReviewBoard
> Windows broker fails to destroy connections if client exits abruptly
> --------------------------------------------------------------------
>
> Key: QPID-2967
> URL: https://issues.apache.org/jira/browse/QPID-2967
> Project: Qpid
> Issue Type: Bug
> Affects Versions: 0.8
> Environment: Windows 64- and 32-bit builds of cpp/qpidd
> Reporter: Chuck Rolke
> Attachments: QPID-2967.patch
>
>
> Start the broker with a small number of connections:
> qpidd --auth no --no-data-dir --max-connections 2
> Run a 'server' program, one that never exits on its own, and kill it with ^C.
> After doing this for the max-number of connections the server will not accept
> any more connections. Internally to the broker the Connection objects are
> never destroyed.
> If the broker's client exits normally then the connection is destroyed
> properly. You can run HelloWorld against the windows broker beyond the
> max-connections count with no problem.
> I know that "the broker is not supported on Windows" but the same problem is
> there for clients when the broker goes away abruptly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
