Naming test timeout was Re: [jboss-dev] PUSH

Andrew Dinn adinn at redhat.com
Thu Jun 26 11:10:40 EDT 2008


Adrian Brock wrote:
  > This test passes for me locally, so there's obviously something
> happening different on the test machine.
> 
> . . .
> 2) TM Warnings (these are repeated)
> 
> 2008-06-26 04:05:18,631 WARN  [com.arjuna.ats.jta.logging.loggerI18N]
> (Thread-19)
> [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa]
> [com.arjuna.ats.inter
> nal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource
> to use for recovering non-serializable XAResource < 131075, 28, 26,
> 49459749504848565458989998
> 48585256545152521029758511015748974950484856545898999848585256545152521029758511015753 >

Hmm, this normally only happens after a crash and restart. Could a 
previous test have crashed and left entries in the tx object store?

> 2008-06-26 04:05:18,631 WARN
> [com.arjuna.ats.arjuna.logging.arjLoggerI18N] (Thread-19)
> [com.arjuna.ats.internal.arjuna.gandiva.inventory.StaticInventory_1] -
> cannot 
> find null implementation.

Oh boy, null is meant to be a classname -- the log was obviously hosed! 
This accounts for the rest of the messages -- garbage out garbage in. If 
the TX store is unreadable like this then there must have been a crash 
in the middle of writing it on a previous run or else something worse 
like running out of disk space or a disk error during the previous or 
current run. My money is on it not being a bug in the TX code :-)

regards,


Andrew Dinn
-----------






More information about the jboss-development mailing list