Transaction is not active during large DB activity process

[deanouk]

Hi all,

We've had this problem for a little while, but usually worked around it.
It's time we understood it a bit more instead of continously fudging our code to work around the problem.

Say we have 1 transaction. Within this transaction we're uploading a file with several thousand records.

Each record causes several DB look ups *each*, using standard EJB3 Entity beans each within their own EAO Session bean.

After all of this each row is then persisted as it represents an entity.


During the process, sometimes, but not always, we get:

ERROR org.hibernate.util.JDBCExceptionReporter - Transaction is not active: tx=TransactionImple < ac, BasicAction: 7f000002:95b7:49dcd694:8ff status: ActionStatus.ABORT_ONLY >; - nested throwable: (javax.resource.ResourceException: Transaction is not active: tx=TransactionImple < ac, BasicAction: 7f000002:95b7:49dcd694:8ff status: ActionStatus.ABORT_ONLY >)

This error will repeat indefinitely until JBoss is shut-down.

We're at a loss as to what's causing this. Transaction time-out is set to 20 mins at the moment, and this can happen 5 mins after submission.

Also, no transaction roll back exception appears (no exception is shown in the logs) to be thrown during the process.

Any help, advice, or pointers, would be appreciated.

Regards,

Dean.

[jaikiran]

Transaction time-out is set to 20 mins at the moment,

How have you set that? Can you post the relevant code/configuration?

and this can happen 5 mins after submission.

That makes me think that your custom transaction timeout isn't correctly set. 5 minutes is the default transaction timeout

[deanouk]

Within jboss-config.xml

<!-- JBoss Transactions JTA -->
 <mbean code="com.arjuna.ats.jbossatx.jta.TransactionManagerService"
 name="jboss:service=TransactionManager">
 <attribute name="TransactionTimeout">1200</attribute>
 <attribute name="ObjectStoreDir">${jboss.server.data.dir}/tx-object-store</attribute>
 </mbean>

[jaikiran]

Are you sure, your EJB3 beans/business methods are not overriding this value?

[deanouk]

Yes absolutely sure. When I said 5 minutes previously, it was a guess. The time was actually under 4 minutes. I don't think this is a transaction time-out problem.

[jaikiran]

You might want to enable TRACE level logs of com.arjuna to see what's going on.

[deanouk]

I have - it's been hard to reproduce though. Since then I've mainly seen some kind of time out issue, which I've posted a seperate issue here:

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=153839