On Thu, 2011-11-17 at 22:29 -0800, Ishitori wrote: > It seems I found the problem. It was a well-known problem of .NET: Connect() > method of the socket class doesn't have timeout property. > http://www.codeproject.com/KB/IP/TimeOutSocket.aspx And it takes from 20 to > 30 seconds for .NET to understand that connection cannot be established. > > I've implemented a workaround in ActiveMQ.NMS client, so now it's working. > So problem is resolved, thanks to everyone. > > By the way, it is my second change in the source code of ActiveMQ.NMS > client. I am thinking about sharing it with the community. Where should I > send my changes for checking? Links/emails are welcomed :) >
You can create a jira issue and attach you patch file along with unit tests to show the issue and ensure it stays fixed once a fix is applied. Just make sure to tick the grant license to apache option when uploading you files: https://issues.apache.org/jira/browse/AMQNET Regards -- Tim Bish ------------ FuseSource Email: tim.b...@fusesource.com Web: http://fusesource.com Twitter: tabish121 Blog: http://timbish.blogspot.com/
