[
https://issues.apache.org/jira/browse/QPID-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039057#comment-13039057
]
Gordon Sim commented on QPID-3264:
----------------------------------
"Why It is impossible to setup c++ client to create new session while reconnect
failure?" - it is not impossible, however it may not be sufficient either. If
the old session is still considered 'live' by the server than any
unacknowledged messages remain locked, any exclusive queues remain etc. In
other words I think choosing a new session name might simply be masking the
problem rather than solving it.
> Channel exception: session-busy: Session already attached
> ---------------------------------------------------------
>
> Key: QPID-3264
> URL: https://issues.apache.org/jira/browse/QPID-3264
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker, C++ Client
> Affects Versions: 0.8
> Environment: Broker on RedHat 5.6 64bit; Client on Windows 7.
> Reporter: Barys Ilyushonak
>
> While client reconnect we got:
> 2011-05-11 16:15:07 error Channel exception: session-busy: Session already
> attached: .a7235961-c1f9-4a76-923c-ff06b09ad0c5
> (qpid/broker/SessionManager.cpp:55)
> To reproduce:
> Start linux broker on default port 5672. Create durable queue and exchange.
> Start the broker. Start client. Client sent the first message. We sow this
> message on the broker. After that enable IPTABLES to reject the port. Client
> still sent messages, but there was no new messages on the broker. After that
> disable IPTABLES to reject the port.
> It is important do not restart the client.
> After that we have got the error in the broker log.
> On the client:
> std::auto_ptr<qpid::messaging::Connection> m_connection
> m_connection.reset(new Connection(m_url));
> m_connection->setOption("reconnect", true);
> We limit network access on the broker machine. To close the port we use:
> iptables -A INPUT -p tcp -s 10.30.24.181 --dport 5672 -j REJECT
> where 10.30.24.181 - windows client IP
> to enable access we use:
> iptables -D INPUT -p tcp -s 10.30.24.181 --dport 5672 -j REJECT
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
