Hello,
I did not customize the timeout of the transaction manager, I'm sorry,
how do I do that?
The transaction time is generally less than the @Schedule frequency,
unless something goes wrong, and then we have more and more items to
process the next time. Which makes this a worsening problem of
here it is
http://openejb.979440.n4.nabble.com/How-to-configure-default-transaction-timeout-in-TomEE-td4657383.html
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/10/31
Thank you for that information, I also find
https://tomee.apache.org/containers-and-resources.html
Now, when I make my conf/tomee.xml be this:
?xml version=1.0 encoding=UTF-8?
tomee
TransactionManager type=javax.transaction.TransactionManager
defaultTransactionTimeoutSeconds=3600
Nope..
?xml version=1.0 encoding=UTF-8?
tomee
TransactionManager id=transactionManager
type=javax.transaction.TransactionManager
defaultTransactionTimeoutSeconds=3600
/TransactionManager
/tomee
31-Oct-2013 12:47:16.990 SEVERE [main]
org.apache.openejb.config.ConfigurationFactory.configureService
weird I tested it before pasting it on trunk
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/10/31 jieryn jie...@gmail.com:
Nope..
?xml version=1.0 encoding=UTF-8?
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]
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)
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
Hi
1h? You customized the timeout of the transaction manager?
That said you have a biggest issue if you processing is longer than your
scheduling. In particular in write mode. We have a retry config but maybe
check you do what you want cause all technical solutions about this timeout
will be
