Not sure. I think a start might be to seperate the JBossMQService into a
seperate VM when running tests. So run the testsuite in one vm, with its
JMS config pointed to the vm running JBossMQService.
I do not know if just by doing that if you will see the problem, but it
might get you closer.
On a similar note, I think that it might be a good idea to setup some
multi-vm tests, but I am stuck on what the best way to do that would be. I
am thinking that we could define a few extra config's like test1...testn (or
something like that).
Perhaps the current default config would remain the same for running all
invm test, then test1 through testn would be used for multi vm tests. We
will definatly have to come up with something to test distributed
transactions and such.
There are some tricky bits, like how to deploy (do you just deploy to one
vm, leaving the other vanilla from its startup config). I think as a start
this might work and possibly even produce the problem that I am seeing,
though I am not sure. It might be that I need to deploy to at least to
2 vm's with a total of 3, one for the seperate JMS server).
I am going to ponder this some more, if you or anyone has any ideas I would
like to hear them.
In the mean time I am going to backport some parts of my app to the previous
version of JBoss, which might take some time, but will releave some stress.
I also wanted to write up something on the build system that I started using
here at work and with some of my other projects, which I think will fit in
perfectly here. I was going to write that sooner, but then I ran into this
wall. =|
--jason
On Sat, 14 Jul 2001, Hiram Chirino wrote:
>
> Jason,
>
> then I have a feeling that this could have something to do with the changes
> that I recently made to the threading model that JBossMQ uses.
>
> What's the easiest way you think I could reproduce the bug on my systems??
>
> Regards,
> Hiram
>
> >From: Jason Dillon <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: <[EMAIL PROTECTED]>
> >Subject: Re: [JBoss-dev] EntityInstanceInterceptor change
> >Date: Fri, 13 Jul 2001 19:38:42 -0700 (PDT)
> >
> >Ok, I have verified that if the jbossmq.jar (and jbossmq-client.jar) from
> >the 2.1-BETA-Mar-26-2001 build are used that everything works fine. The
> >only thing I had to change was the router jboss.jcml changing INVM stuff to
> >RMI (which it was not even using) and remove the INVM stuff from
> >jbossmq.xml.
> >
> >I ran the exact same test and it finished flawlessly.
> >
> >--jason
> >
> >
> >On Fri, 13 Jul 2001, Scott M Stark wrote:
> >
> > > Do you have the timeout msg that is logged?
> > >
> > > >
> > > > The first odd thing is that when it times out a message is logged, but
> >the
> > > > thread still hangs. Should it be interrupted or something?
> > > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Jboss-development mailing list
> > > [EMAIL PROTECTED]
> > > http://lists.sourceforge.net/lists/listinfo/jboss-development
> > >
> >
> >
> >_______________________________________________
> >Jboss-development mailing list
> >[EMAIL PROTECTED]
> >http://lists.sourceforge.net/lists/listinfo/jboss-development
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
