[ https://issues.apache.org/jira/browse/QPID-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-8234: ----------------------------- Fix Version/s: (was: qpid-java-broker-7.0.7) > [Broker-J] Return amqp error "amqp:connection:forced" on opening connections > to non-existing or not-active virtual hosts > ------------------------------------------------------------------------------------------------------------------------ > > Key: QPID-8234 > URL: https://issues.apache.org/jira/browse/QPID-8234 > Project: Qpid > Issue Type: Bug > Components: Broker-J > Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, > qpid-java-broker-7.0.0, qpid-java-broker-7.0.1, qpid-java-broker-7.0.4, > qpid-java-broker-7.0.5, qpid-java-broker-7.0.6 > Reporter: Alex Rudyy > Priority: Major > > On attempt to open connection to non-existing or not available virtual host, > it would be better to use {{amqp:connection:forced}} error conditions rather > than {{amqp:not-found}} > As per spec {{amqp:connection:forced}} is defined as {quote} An operator > intervened to close the connection for some reason. The client could retry at > some later date.{quote}. It allows retrying whilst {{amqp:not-found}} can be > interpreted on the client to stop reconnecting. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org