You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "james strachan (JIRA)" <ji...@apache.org> on 2007/02/27 11:39:03 UTC
[jira] Moved: (AMQNET-2) Leaving threads running if
Connection.Dispose fails.
[ https://issues.apache.org/activemq/browse/AMQNET-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
james strachan moved AMQ-990 to AMQNET-2:
-----------------------------------------
Fix Version/s: 1.0
Component/s: (was: NMS (C# client))
Key: AMQNET-2 (was: AMQ-990)
Project: ActiveMQ .Net (was: ActiveMQ)
> Leaving threads running if Connection.Dispose fails.
> ----------------------------------------------------
>
> Key: AMQNET-2
> URL: https://issues.apache.org/activemq/browse/AMQNET-2
> Project: ActiveMQ .Net
> Issue Type: Bug
> Reporter: Pawel Niewiadomski
> Assigned To: james strachan
> Fix For: 1.0
>
>
> I faced today following error - in Connection.Dispose call to DisposeOf(ConnectionId); fails with exception. This causes Connection.Dispose to be aborted leading to thread responsible for communication not to be joined. I'm talking about the thread created in TcpTransport.
> closing = true;
> DisposeOf(ConnectionId); // this causes exception and aborts further execution on this scope
> sessions.Clear();
> transport.Oneway(new ShutdownInfo());
> transport.Dispose(); // this is responsible for joining the thread and closing sockets
> closed = true;
> In summary - thread is still running and we can't get rid of it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.