[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640311#comment-13640311
]
Tom commented on AMQNET-338:
----------------------------
Can we reopon this one? We have the exact same issue but with .Net 4.5 and
Apache.NMS.ActiveMq 1.5.6. It's quite possible that we're doing something
wrong but we're seeing identical delays and the thread abort.
We're currently trying to isolate the conditions for this to occur but having
difficulty extracting a reliable test case.
>From our reading of the code it is not obvious under what conditions this
>timeout/abort will occur, closing the connection should cause the
>Socket.Receive in the unmarshal code to throw an exception causing the read
>loop to break and terminate.
http://svn.apache.org/viewvc/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/branches/1.5.x/src/main/csharp/Transport/Tcp/TcpTransport.cs?revision=1354734&view=markup#l281
Is there a reason the exception might not get thrown? There seem to be a
number of empty catch statements in TcpTransport.Close() could it be that some
more error handling is required in these cases.
Any help understanding this issue would be greatly appreciated.
> TcpTransport.cs - Close() taking 30 seconds
> -------------------------------------------
>
> Key: AMQNET-338
> URL: https://issues.apache.org/jira/browse/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: Timothy Bish
>
> 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:
> {noformat}
> if(null != readThread)
> {
> if(Thread.CurrentThread != readThread && readThread.IsAlive)
> {
> if(!readThread.Join((int) MAX_THREAD_WAIT.TotalMilliseconds))
> {
> readThread.Abort();
> }
> }
> readThread = null;
> }
> {noformat}
> 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.
> Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
