Yes, it should be as stable (or a little more). I'll be integrating it back
into jboss soon.
And I have seen the problems you have talked about with the OIL. I'm going
to have to research that more.
Oh yeah, MQSeries also supports XA now :)
Regards,
Hiram
>From: Jason Dillon <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: Re: [JBoss-dev] EntityInstanceInterceptor change
>Date: Mon, 16 Jul 2001 21:17:50 -0700 (PDT)
>
>Did you ever have a chance to look into this at all? I am going a little
>crazy, since our application is heavily JMS based. The previous version
>was
>using SwiftMQ, which I dropped so I could use MDBs.
>
>My options for a provider are:
>
> JBossMQ - This is what I want to use, but...
> OpenJMS - Does this even work? Never tried it.
> SonicMQ - This product angers me more than anything.
> WebLogic JMS - Only because we have a license for it.
>
>These are the only providers that I have found that support ASF & XA. I
>would really like to continue using JBossMQ, but I can not have it hanging.
>
>Is there anything that I could do to help get this fixed (sooner rather
>than
>later)?
>
>On a related note, is the jbossmq module stable as it is (with its new
>structure)?
>
>--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
_________________________________________________________________
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
