Aaron Mulder wrote:
>
> 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
Hi,
I get the same thing.
It seems the first call that fails doesn't remove the lock. Will see.
>
> 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.
I think this is another problem: if I only deploy the beans
(dbtest.jar), no client call, and hit Ctrl-C, the server hangs when jaws
fails to remove the table. Maybe a dependency problem (jaws gets a
broken pipe exception from hsql).
Sebastien
>
> Aaron
