Jason, I have no idea if this is relevant...
I discovered in the ConnectionManager/pool code that the scheduling is kind
of awful, and that under high load, if the pool gets emptied and a request
has to wait, that request is apt to wait more or less forever, since it is
blocking and new requests take any available connections without blocking.
(I discovered this by putting a blocking timeout in the pool and running
the high stress (10 threads, 1000 iterations) bank test. After a little
while I got a few exceptions from blocking timeout.) Is there any chance
this is happening to you? A crude fix that might work would be to make
every new request block if any request is blocking when the new one comes
in: this gives everyone a chance at intercepting the "returned"
notifyAll(). I've been wondering about how or if to implement strict
scheduling, and kind of forgot this code is used by jmsra in 2.4. If you
think this might be relevant and want me to suggest a more specific fix let
me know.
Thanks
david jencks
On 2001.09.25 16:31:44 -0400 Jason Dillon wrote:
> I ran some tests last night with the
> TransactionManager.TransactionTimeout
> set to Integer.MAX_VALUE, and I am still getting these messages:
>
> org.jboss.tm.TxCapsule [Thread-5] () - Transaction XidImpl [FormatId=257,
> GlobalId=eng-ecr5a//0, BranchQual=] timed out. status=STATUS_ACTIVE
>
> This is still off of a pre-3.0 release... I have been resistent to moving
> to
> 3.0 due to the months of work that I had to do (and the stress to
> stabilize
> the system) to make everything work with the jms ra, entity locking and
> so
> on.
>
> I guess I should probably look into this a little bit more though, since
> it
> is going to be very difficult to track down this problem on an old
> build...
> =(
>
> --jason
>
>
> On Mon, 24 Sep 2001, Hiram Chirino wrote:
>
> >
> > The problem is that I want to basicly use a local TX with a MQ
> XAConnection.
> > If knew how to generate vaid XIDs to feed the XAResource, then we
> could
> > emulate the TM. But I'm not 100% on
> > how to generate XIDs, so hacked a JBossMQ specific solution.
> >
> > Anybody know how to generate valid XIDs??? At least valid enough to
> control
> > a 1 phase commit resource???
> >
> > Regards,
> > Hiram
> >
> > >From: Jason Dillon <[EMAIL PROTECTED]>
> > >Reply-To: [EMAIL PROTECTED]
> > >To: <[EMAIL PROTECTED]>
> > >Subject: Re: [JBoss-dev] MDB non-xa cf & tx timeout
> > >Date: Mon, 24 Sep 2001 18:17:23 -0700 (PDT)
> > >
> > >Why does StdServerSession hard code JBossMQ specifics
> (JBossMQTXInterface
> > >& the related classnames and such)?
> > >
> > >--jason
> > >
> > >
> > >On Mon, 24 Sep 2001, Hiram Chirino wrote:
> > >
> > > >
> > > > No, Not yet... I guess I should also do the same for CMT that has
> > > > NotSupported right???
> > > >
> > > > Regards,
> > > > Hiram
> > > >
> > > > >From: Jason Dillon <[EMAIL PROTECTED]>
> > > > >Reply-To: [EMAIL PROTECTED]
> > > > >To: <[EMAIL PROTECTED]>
> > > > >Subject: Re: [JBoss-dev] MDB non-xa cf & tx timeout
> > > > >Date: Sun, 23 Sep 2001 20:06:12 -0700 (PDT)
> > > > >
> > > > >Hey, sorry for the late reply. What about CMT? Shouldn't CMT
> behave
> > >the
> > > > >same in this case?
> > > > >
> > > > >The system I run this under uses the old style config. Is this
> change
> > > > >relavent for integration with 2.4.x? I think I might switch over
> to
> > >that
> > > > >for production use... head is changing to quickly.
> > > > >
> > > > >--jason
> > > > >
> > > > >
> > > > >On Thu, 20 Sep 2001, Hiram Chirino wrote:
> > > > >
> > > > > > Hi Jason,
> > > > > >
> > > > > > >Anyways, I think there is still an issue with the tx recipts
> for an
> > > > >MDB. I
> > > > > > >have to set the default tx timeout insainly high to avoid this
> > >problem.
> > > > > > >
> > > > > > >I remember there were a few suggestions on how to fix this,
> but I
> > >am
> > > > >not
> > > > > > >sure what happend to them...
> > > > > > >
> > > > > >
> > > > > > I just commited chanages to HEAD that should fix this for MDB
> with
> > >BMT.
> > > > > > Pease test and let me know if it worked.
> > > > > >
> > > > > > Regards,
> > > > > > Hiram
> > > > > >
> > > > > > _________________________________________________________________
> > > > > > Get your FREE download of MSN Explorer at
> > > > >http://explorer.msn.com/intl.asp
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Jboss-development mailing list
> > > > > > [EMAIL PROTECTED]
> > > > > > https://lists.sourceforge.net/lists/listinfo/jboss-development
> > > > > >
> > > > >
> > > > >
> > > > >_______________________________________________
> > > > >Jboss-development mailing list
> > > > >[EMAIL PROTECTED]
> > > > >https://lists.sourceforge.net/lists/listinfo/jboss-development
> > > >
> > > >
> > > > _________________________________________________________________
> > > > Get your FREE download of MSN Explorer at
> > >http://explorer.msn.com/intl.asp
> > > >
> > > >
> > > > _______________________________________________
> > > > Jboss-development mailing list
> > > > [EMAIL PROTECTED]
> > > > https://lists.sourceforge.net/lists/listinfo/jboss-development
> > > >
> > >
> > >
> > >_______________________________________________
> > >Jboss-development mailing list
> > >[EMAIL PROTECTED]
> > >https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> >
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at
> http://explorer.msn.com/intl.asp
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
