activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eddie Fast (JIRA)" <>
Subject [jira] [Created] (AMQNET-338) TcpTransport.cs - Close() taking 30 seconds
Date Thu, 04 Aug 2011 22:43:27 GMT
TcpTransport.cs - Close() taking 30 seconds

                 Key: AMQNET-338
             Project: ActiveMQ .Net
          Issue Type: Bug
          Components: NMS
    Affects Versions: 1.5.1
         Environment: Windows 7, .NET 2.0, Visual Studio 2008, Unity 3.4
            Reporter: Eddie Fast
            Assignee: Jim Gomes

We've been noticing a random freeze on exit for 30 seconds.  The frequency is different per
machine, but it happens about 10-30% of the time, sometimes more.  We've traced it down to
TcpTransport.Close(), in this block:

if(null != readThread)
	if(Thread.CurrentThread != readThread && readThread.IsAlive)
		if(!readThread.Join((int) MAX_THREAD_WAIT.TotalMilliseconds))

	readThread = null;

We're running this in the Unity game engine, which run C# script in a Mono environment.

I understand that reproducing this on your end would be difficult, but I'm reporting this
in the hopes that I can gain some insight why this is happening.

- What thread is this code waiting for?
- What would be some of the causes of the deadlock?

No messages are being sent or received.  It's basically starting up and closing down.

Our temporary workaround is to reduce this wait time from 30 seconds to 5 seconds, but I'd
like to eventually find a cause.


This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message