-1
The recent change made for AMQNET-218 seems to have introduced a problem.
In general, I am uneasy about having this type of threading-related code
change made right before a release. It would be better to let this kind of
change cook for a while.
Specifically, in CompositeTaskRunner.cs, line
On Tue, 2010-02-02 at 13:41 -0800, Jim Gomes wrote:
-1
The recent change made for AMQNET-218 seems to have introduced a problem.
In general, I am uneasy about having this type of threading-related code
change made right before a release. It would be better to let this kind of
change cook
On Tue, 2010-02-02 at 14:20 -0800, Jim Gomes wrote:
I searched the code for other areas where Thread.ResetAbort() was called
(three locations found), and I have made some changes on my local machine.
I am reconfiguring my application to use these custom versions so I can test
the changes.
Got your changes. They matched mine.
- Jim
-Original Message-
From: Timothy Bish tabish...@gmail.com
Date: Tue, 02 Feb 2010 17:28:39
To: dev@activemq.apache.org
Subject: Re: [VOTE] Release Apache.NMS.ActiveMQ 1.2.0 #3
On Tue, 2010-02-02 at 14:20 -0800, Jim Gomes wrote:
I searched
The issue found during the last voting cycle have all been resolved
so its time to try another vote.
Now that we've fixed the issue the Voting is open once again on the
Apache.NMS.ActiveMQ 1.2.0 release.
This release is based on the Apache.NMS API v1.2.0 and runs on .NET
frameworks 2.0+ and Mono
