Annotation @TransactionTimeout not honoured for asynchronous method using ejb timer service

[pdhaigh]

Hi,

I have found that if I have method that requires a longer transaction timeout, I can use

@TransactionTimeout(1500)

Unless the method is scheduled using the EJB timer service:

<async:timer-service-dispatcher/>

, in which instance the timout modifier appears to simply be ignored.

Is this a known limitation?

cheers

phil

[pmuir]

Ugh, might be a Seam/EJB3 interaction problem or just a EJB3 problem.

Can you chase up with the EJB3 guys whether it should work on a EJB3 timeout method if Seam isn't in the picture (post on their forum, check their JIRA). If it's not a known problem for them, put an issue in the Seam JIRA.

[admin.admin.email.tld]

have you tried using Quartz instead?  EJB timer is not clusterable.

[pdhaigh]

Thanks pete,

reference to post on ejb3 forum

[blabno]

Having the same problem. My thread : http://www.seamframework.org/Community/TransactionTimeoutGenericJDBCExceptionCannotOpenConnection

Have you solved the problem ?

[blabno]

Using Quartz helps.

[pdhaigh]

Yes, as my original question said - it works fine *except* when using the EJB Timer Service.

Actually I've found a number of issues with the EJB timer service, and have as a result just started using quartz by default.. not for any functional enhancements, but simply because it appears to work properly whereas the ejb one... doesn't..!

A list of a few problems I have experienced with the EJB timer service:

1. Ignores @TransactionTimeout annotation
2. Incorrectly sets next run time pf persisted timers after Application server restart (takes restart time + interval rather than working out interval from initial schedule time).  This was accepted by the ejb3 team as a bug. http://www.seamframework.org/Community/EJBTimersIgnoringStartDate
3. Sometimes just doesn't run scheduled events

All in all, quartz seems a better bet :)