[
https://issues.apache.org/activemq/browse/AMQNET-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50128#action_50128
]
Daniel Ellis commented on AMQNET-147:
-------------------------------------
I have given that code snippet a try and I still feel a Trace output is
necessary. Maybe the trace could be added just before calling OnException.
Here is the results of the unit tests when removing the
CloseSessionAfterEverythingElse patch:
ActiveMQ transport:
DisposeConnectionWithoutDisposingConsumer passes with no indication in the
trace of a problem.
Failover transport:
DisposeConnectionWithoutDisposingConsumer fails (never returns) and no error in
the trace log.
I think including the trace output here is very important for diagnostics.
> Connection fails to close if a producer or consumer has not been disposed
> (only when using the failover transport).
> -------------------------------------------------------------------------------------------------------------------
>
> Key: AMQNET-147
> URL: https://issues.apache.org/activemq/browse/AMQNET-147
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: ActiveMQ Client
> Affects Versions: 1.1
> Environment: Using failover transport
> Reporter: Daniel Ellis
> Assignee: Timothy Bish
> Fix For: 1.1
>
> Attachments: CloseSessionAfterEverythingElse.patch,
> ConnectionError.patch, ConnectionsTests.patch
>
>
> When using the failover transport such as:-
> <defaultURI
> value="activemq:failover:(tcp://activemqhost:61616,tcp://activemqhost:61616)"/>
> A connection will fail to close if you dispose a connection before disposing
> a consumer or producer that is associated with the connection. The dispose
> call never returns because the failover transport is continually reconnecting
> due to a KeyNotFoundException. The KeyNotfoundException is thrown because a
> session no longer exists in the connection state.
> A number of the existing unit tests fail (actually they never return) when
> using the failover transport. When in debug, a DebugAssert is displayed for
> each error that causes the reconnect.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
