How to detect transaction timeout ?

[davidbalazic]

Sometimes during a business method call (in a stateless bean) the transaction times out and the changes are not committed.
The problem is, that the calling client does not receive any exception or other form of error indication.

Can the bean method get access to the transaction before it returns, so it can check its state ?

It is a Stateless bean with container managed transactions.
SW is jboss 4.0.4GA on windows with hibernate accessing Oracle DB.

I tried this :

@Resource SessionContext ejbContext;

public Object myMethod()
{
 do_something ();

 int status = ejbContext.getUserTransaction( ).getStatus();
 return evaluate(status);
}

But that does not work of course. It gives :

javax.ejb.EJBException: java.lang.IllegalStateException: Container ProductServiceMgmtFeatureWebAcBean: it is illegal to inject UserTransaction into a CMT bean

Is there any way for the client to be notified that the method did not successfully end ?

I read about the <exception-on-rollback> optin, but it does not seem to make any difference. ( I read about it here : http://jira.jboss.com/jira/browse/JBAS-1509 )

Regards,
David

[jhalliday]

I'm guessing that you are using EJB3 and the JBAS-1509 feature is only in the EJB2 container. However, the <exception-on-rollback> is the best (only) approach if the client does not manage (begin/commit/rollback) the transaction. Turn on TRACE level logging and see if the TxInterceptorCMT is working - according to the JIRA issue that is the code which implements the feature. If it's not firing, raise a new JIRA issue to have this behaviour fixed.

[davidbalazic]

As the bean code is full of annotations, I guess it is EJB3 :-)
How can I check for sure whether it is EJB2 or EJB3 ?

[davidbalazic]

I added to the log4j.xml these lines :




but there is nothing in the log from TxInterceptorCMT. (there are a few other unrelated TRACE lines).

[davidbalazic]

The forum ate my code :

 <category name="org.jboss.ejb">
 <priority value="TRACE" class="org.jboss.logging.XLevel"/>

[davidbalazic]

OK, I found out that I can detect the timeout with SessionContext.getRollbackOnly(), like this :

@Resource SessionContext ctx;

// and then check at the end of each business (public) method :

if (ctx.getRollbackOnly()) {
 throw new Some...Exception("Something happened, method failed");
 }
return result; // otherwise end normally

But adding that check to each method is really ugly. Is there no simpler method ?