Hi Stefan,
Thanks for testing those changes. I am glad they solved the problem.
As far as the unit tests go, many of them have been broken (i.e.,
failing) for a long time. I have been meaning to go back and take a
look at them to find out where the problems are. They have been
neglected for too
Hi Jim,
Your correction works brilliantly, thanks for quick resolution.
Some additional questions.
What is the test status in e.g. Apache.NMS.ActiveMQ.Test. Should they
work..?
I currently get 7 tc's in error, have tried both on 4.1 and 5.0 broker.
Also when I end my application I get some exce
Stefan,
I checked in a change that should fix this problem. Looks like it was
an incomplete change. Would you grab the latest and see if that fixes
your problem?
Thanks!
-Jim
On 4/23/08, James Strachan <[EMAIL PROTECTED]> wrote:
> On 23/04/2008, StefanL <[EMAIL PROTECTED]> wrote:
> >
> > I
On 23/04/2008, StefanL <[EMAIL PROTECTED]> wrote:
>
> I'm trying to upgrade our activemq-dotnet from September 2007 to current
> revision.
> I though get an error in our code which creates multiple connections to the
> broker and I get the
> javax.jms.InvalidClientIDException: Client: already
I'm trying to upgrade our activemq-dotnet from September 2007 to current
revision.
I though get an error in our code which creates multiple connections to the
broker and I get the
javax.jms.InvalidClientIDException: Client: already connected from
I can easily reproduce the error with this simp
