You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2008/10/30 12:15:44 UTC
[jira] Updated: (QPID-585) Client protocol state is maintiained
between connections when the connection fails during initial connection
[ https://issues.apache.org/jira/browse/QPID-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack updated QPID-585:
----------------------------------
Fix Version/s: (was: M4)
Descoping items not being worked on for M4 into Unknown Fix Version for now
> Client protocol state is maintiained between connections when the connection fails during initial connection
> ------------------------------------------------------------------------------------------------------------
>
> Key: QPID-585
> URL: https://issues.apache.org/jira/browse/QPID-585
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: M2
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
>
> When the first connection is being established the stateManager is not replaced for each new connection attempt. This leads the client to get out of sync.
> This can be seen if you place an old log4j at the start of the classpath. The client will throw a NoSuchMethod (isTraceEnabled) exception wich is wrapped in a ProtocolCodecException. When AMQConnection loops and tries to reconnect the state is now stale and needs reset.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.