You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2007/09/10 14:37:29 UTC
[jira] Created: (QPID-585) Client protocol state is maintiained
between connections when the connection fails during initial connection
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
Fix For: M2.1
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.
[jira] Commented: (QPID-585) Client protocol state is maintiained
between connections when the connection fails during initial connection
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749870#action_12749870 ]
Martin Ritchie commented on QPID-585:
-------------------------------------
Think that this is only half a problem now. The StateManager is not rest between initial connection attempts but the state is also not adjusted during that attempt.
One obscure test that might highlight the problem is using the round robin failover mechanism to connection to broker 1 then 2.
Where the user does not have permission to access broker 1. This should leave the StateManager in a funny state.
The half of the problem where the ProtocolHandler only had a reference to another StateManager has been resolved by having the PH have the StateManager and all other uses refer to that instance.
So when it changes it is only one update that is requried.
> 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.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-585) Client protocol state is maintiained
between connections when the connection fails during initial connection
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-585:
--------------------------------
Fix Version/s: (was: M2.1)
M3
> 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
> Fix For: M3
>
>
> 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.
[jira] Updated: (QPID-585) Client protocol state is maintiained
between connections when the connection fails during initial connection
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ 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.