This is interesting,
so the transaction is active and it then locks... i suspect it gets
passivated as it works... does the passivation check for usage??? (ole?), if
not that could be it
Aaron do you see a "transaction timedout" before, also add a
transaction.hashcode() in the lock waiting so we can see what is happening
there (man this timeout thing is a pain)
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
|Sent: Tuesday, October 24, 2000 9:57 AM
|To: jBoss Developer
|Subject: [jBoss-Dev] More DB Test Woes
|
|
| Hate to be the bearer of bad news, but... I'm getting another
|lockup during the DB test. Can you guys (who are working on the locking
|and stuff) build the current CVS of jBoss and the test suite, and run the
|dbtest with everything exactly as it is in CVS? That should run it
|against Hypersonic, and fail when it tries to write the extreme Longs.
|After it fails, I get a bunch of messages like:
|
|[AllTypes] LOCKING-WAITING (TRANSACTION) for id seb ctx.hash 3593899
|tx:TransactionImpl:XidImpl:[B@789869
|
| Even worse, after I hit Ctrl-C, when the server tries to shut
|down, it gets more of those messages and does not exit. There's no way to
|stop it without killing the process. This is unfortunate.
|
|Aaron
|
|
|
|
