[
https://issues.apache.org/jira/browse/QPID-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie updated QPID-272:
--------------------------------
Description:
If the client code fails with a non AMQException such as a RuntimeException
then this will cause Failover which in turn may cause an internal
FailoverException("Failing over starting") to be thrown to external client code.
Updated title as this is not a failover problem. The problem is the attainState
is not notify()ed when the connection is closed.
This can be seen as a failover problem because failover doesn't start but that
is due to the above underlying problem.
was:If the client code fails with a non AMQException such as a
RuntimeException then this will cause Failover which in turn may cause an
internal FailoverException("Failing over starting") to be thrown to external
client code.
Summary: Connection closure during Initial Connection will hang client
(was: Connection Failover during Initial Connection will hang client)
> Connection closure during Initial Connection will hang client
> -------------------------------------------------------------
>
> Key: QPID-272
> URL: https://issues.apache.org/jira/browse/QPID-272
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Martin Ritchie
> Priority: Critical
>
> If the client code fails with a non AMQException such as a RuntimeException
> then this will cause Failover which in turn may cause an internal
> FailoverException("Failing over starting") to be thrown to external client
> code.
> Updated title as this is not a failover problem. The problem is the
> attainState is not notify()ed when the connection is closed.
> This can be seen as a failover problem because failover doesn't start but
> that is due to the above underlying problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
