Thanks for that information, Howard. Even with @AccessTimeout(-1) which should cause it to wait forever, I still take the aforementioned Exception. It seems that some of my transactions can take upwards of an hour to complete and that Apache TomEE deems this unacceptable.
On Wed, Oct 30, 2013 at 8:54 AM, Howard W. Smith, Jr. <smithh032...@gmail.com> wrote: > i am doing the same (see the URLs below). > > /** > * > * http://tomee.apache.org/examples-trunk/access-timeout/README.html > * http://tomee.apache.org/examples-trunk/access-timeout-meta/ > * http://docs.oracle.com/cd/E19798-01/821-1841/gipsz/index.html > */ > @Singleton > @Lock(LockType.WRITE) > @AccessTimeout(value = 2, unit = TimeUnit.MINUTES) > public class EmailRequestBean { > > > > On Wed, Oct 30, 2013 at 8:38 AM, jieryn <jie...@gmail.com> wrote: > >> Greetings, I'm using Apache TomEE 1.6.0-SNAPSHOT from a couple of >> weeks ago. I am frequently seeing my @Lock(LockType.WRITE) @Singleton >> @Startup MySchedule { @Schedule(/**/) public void run() { /* slowish >> */ } } have the following error: >> >> WARNING [EjbTimerPool - 901] >> org.apache.openejb.core.timer.EjbTimerServiceImpl.ejbTimeout Failed to >> execute ejbTimeout on MySchedule successfully within 1 attempts >> >> And then the transaction is rolled back. How can I extend the timeout >> such that I have more time for MySchedule#run in order to do its >> processing? >>
