The message may be normal - but the fact that the client hanga
immediately after it appears is (I hope!) not normal. The only activity
thereafter on either the client or server side is the timeout message -
but the client stays hung even after that message.
I'll give you steps to reproduce if you'll tell me what DBs you
have access to.
Aaron
On Fri, 20 Oct 2000, marc fleury wrote:
> btw the locking messages are
>
> ABSOLUTELY NORMAL
>
> now...
>
> that you are not notified on a "time-out" is not normal, since the new code
> does test for that, something else is going on, it means the timeout thread
> is not awaken by the exceptions (???) I will double check that.
>
> marc
>
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> |Sent: Friday, October 20, 2000 8:18 PM
> |To: jBoss Developer
> |Subject: RE: [jBoss-Dev] Lockup on DB test
> |
> |
> |relax, you know better than that.
> |
> |We test with the commits for now, and the stuff is flying (separate mail on
> |what we did at SUN, amazing!!!)
> |
> |I do need to test extensively with the rollback and all the
> |craziness coming
> |from your XA stuff ;-)... don't worry.
> |
> |marc
> |
> |
> ||-----Original Message-----
> ||From: [EMAIL PROTECTED]
> ||[mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
> ||Sent: Friday, October 20, 2000 5:33 PM
> ||To: jBoss Developer
> ||Subject: [jBoss-Dev] Lockup on DB test
> ||
> ||
> || Running with the current CVS jBoss source and the jBoss Test
> ||"dbtest", I get a lockup with the message:
> ||
> ||[AllTypes] LOCKING-WAITING (TRANSACTION) for id seb ctx.hash 2062088
> ||tx:TransactionImpl:XidImpl:mesa.mearaworks.com/35
> ||
> || Then after a while I get
> ||
> ||[Container factory] Transaction XidImpl:mesa.mearaworks.com/36 timed
> ||out. status=STATUS_ACTIVE
> ||
> || But the client is still hung. I don't think we've ironed out all
> ||the kinks yet... But I'm starting to wonder whether we don't have some
> ||larger problem (like not doing a rollback properly) when you generate a
> ||SQLException during an ejbLoad or ejbStore, since this makes the 3rd
> ||consecutive DB product to have continuous explosions under certain
> ||circumstances after you try to write a value that's out of range for a
> ||double or float column.
> ||
> ||Aaron
> ||
> ||
> ||
> |
> |
> |
>
>
