Jboss AS 5.1.0.GA, JBOSS Tx 4.6.1.CP12

Using User Transaction's "set timeout" causes future new transactions, executed by the same thread, to ignore default transaction timeout settings.

Example:

1) Execute a EJB-CMT method: you can see a new transaction is started (Conteiner Managed) with default timeout settings, say 300 seconds

2) Execute a EJB-BMT method: you can see a new user transaction is started with user defined timeout, say 20 seconds

3) Execute a EJB-CMT method again....now I expect the new Tx running with default timeout (300) but I see it is started with a 20 sec. timeout!

Here's the log.

1)

2013-03-20 17:04:51,614 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (WorkerThread#0[127.0.0.1:51579]) TransactionReaper::insert ( BasicAction: -53eb99c6:c943:5149dcab:72 status: ActionStatus.RUNNING, 300 )

2013-03-20 17:04:51,614 INFO [it.eng.avcp.avcpass.service.operation.impl.ConsultaTipologicaServiceBean] (WorkerThread#0[127.0.0.1:51579]) avcpass-655jhfrr3-4243423435566OOJJ444-consultaListaTipologica::start

2013-03-20 17:04:51,614 INFO [it.eng.avcp.avcpass.service.operation.impl.ConsultaTipologicaServiceBean] (WorkerThread#0[127.0.0.1:51579]) avcpass-655jhfrr3-4243423435566OOJJ444-RisultatoConsultaListaTipologicaAsMap::stop

2)

2013-03-20 17:06:50,861 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (WorkerThread#0[127.0.0.1:51583]) TransactionReaper::insert ( BasicAction: -53eb99c6:c943:5149dcab:77 status: ActionStatus.RUNNING, 20 )

2013-03-20 17:06:50,861 DEBUG [it.avcp.spc.anagrafe.centralizzata.ejbImpl.servizi.GestioneCentralizzataSoggettoBean] (WorkerThread#0[127.0.0.1:51583]) <Enter>::[public] it.avcp.spc.anagrafe.centralizzata.ejbImpl.servizi.GestioneCentralizzataSoggettoBean.inserimentoSoggetto()

3)

2013-03-20 17:09:16,062 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (WorkerThread#0[127.0.0.1:51601]) TransactionReaper::insert ( BasicAction: -53eb99c6:c943:5149dcab:80 status: ActionStatus.RUNNING, 20 )

2013-03-20 17:09:16,062 INFO [it.eng.avcp.avcpass.service.operation.impl.ConsultaTipologicaServiceBean] (WorkerThread#0[127.0.0.1:51601]) avcpass-655jhfrr3-4243423435566OOJJ444-consultaListaTipologica::start

2013-03-20 17:09:16,062 INFO [it.eng.avcp.avcpass.service.operation.impl.ConsultaTipologicaServiceBean] (WorkerThread#0[127.0.0.1:51601]) avcpass-655jhfrr3-4243423435566OOJJ444-RisultatoConsultaListaTipologicaAsMap::stop

I see the working thread is the same WorkerThread#0, so I think it is related to some thread bound setting not cleaned after TX committ.

It seems to be a BUG or not?