You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <qp...@incubator.apache.org> on 2008/06/26 14:29:45 UTC
[jira] Resolved: (QPID-1137) [C++] It is required to call
Connection::close even if it fails to connect to the broker using
Connection::open
[ https://issues.apache.org/jira/browse/QPID-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim resolved QPID-1137.
------------------------------
Resolution: Fixed
Fix Version/s: M3
Assignee: Gordon Sim
Resolved as r671877. Danushka, could you verify this addresses the example you were working on?
> [C++] It is required to call Connection::close even if it fails to connect to the broker using Connection::open
> ---------------------------------------------------------------------------------------------------------------
>
> Key: QPID-1137
> URL: https://issues.apache.org/jira/browse/QPID-1137
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Reporter: Danushka Menikkumbura
> Assignee: Gordon Sim
> Fix For: M3
>
>
> I found this flaw when I was using Qpid/C++ to implement AMQP transport for Axis2/C.
> There I wanted to make the Axis2/C AMQP transport receiver such that it checks for the availability of the Qpid broker and waits in a loop until the broker is up.For this I used a class level Connection object. But with that implementation, when the broker comes up after some time, the Connection object still fails to establish the connection and gives the "Connection refused ... " error. [Socket.cpp:158]. As a remedy for this I had to call Connection::close inside the exception handler.
> I dont think this is acceptable unless there is a really solid reason behind it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.