I can look in to backporting the changes from the trunk into the branch versions.
On Thu, Apr 17, 2014 at 6:52 AM, Timothy Bish <tabish...@gmail.com> wrote: > On 04/17/2014 03:12 AM, GoodLuck wrote: > > I met the same problem "TcpTransport.cs - close() taking 30 seconds" in > my program with Apache.NMS.ActiveMQ 1.6.2. > > My C# client is using .NET 4.0, ActiveMQ 5.6.0 and NMS 1.6.0 in Windows > 7 64 bits OS. > > > > In the forum, I read the message said version 1.6.2 fix it, but I read > the source code for 1.6.2, find it haven't change the source > > code for it,and the time for MAX_THREAD_WAIT is still 30 seconds. I read > the message wrote by Jim Gomes at 10/Apr/14: > > "Resolving the issue based on previous check-in fix" and said it already > fix in version 1.7. > > But I find the newest version in the activemq website is 1.6.2, How can > I find version 1.7? or when is the version 1.7 release? > > If I upgrade Apache.NMS.ActiveMQ to version 1.7, do I need upgrade my > ActiveMQ? thanks. > > > > > > > > > I don't believe anyone ever said this was in the 1.6.2 release, and the > issue only tags it as being in the 1.7.0 tree. There is no 1.7.0 release > yet as that is the future development release and there's not been any > talks of releasing it yet. I suppose the fix could be backported to the > 1.6.x codebase and a 1.6.3 release cut but it comes down to someone > having the time to do it. > > You don't need to upgrade broker when you update the client. > You can merge the fix into a local checkout of the 1.6.x code and build > you own copy of the libs easily enough if you need it right away. > > -- > Tim Bish > Sr Software Engineer | RedHat Inc. > tim.b...@redhat.com | www.fusesource.com | www.redhat.com > skype: tabish121 | twitter: @tabish121 > blog: http://timbish.blogspot.com/ > >
