WebSphere Transaction Timeout
Problem
ILOG reports the transaction timeout issue
WTRN0006W: Transaction XYZ has timed out after 300 seconds.
0000000f TimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 6,5,main]. The stack trace of this thread when the timeout occurred was:
org.springframework.beans.factory.support.AbstractBeanDefinition.validate(AbstractBeanDefinition.java:929)
org.springframework.beans.factory.support.DefaultListableBeanFactory.registerBeanDefinition(DefaultListableBeanFactory.java:577)
org.springframework.beans.factory.support.BeanDefinitionReaderUtils.registerBeanDefinition(BeanDefinitionReaderUtils.java:148)
Solution
To set transaction timeout in WebSphere, navigate to Server -> Server Types -> WebSphere Application Servers -> Server Name -> Container Services -> Transaction Service -> Maximum transaction timeout.
The default is 300s. You can change the value as desired.
posted by Jayanthi Krishnamurthy @ 4:53 PM
2 Comments
2 Comments:
Thanks for that!!
Websphere transaction timeouts are passive, meaning nothing is interrupted, the thread continues. You just suppress the warning. When the thread reaches the transaction boundary then the rollback occurs. You postphoned it. And you postphoned it globally. Meaning that websphere will now will perform commits on resources where it previously would perform rollbacks. These external resources have their own transaction timeouts. So, I am not sure what you have solved.
Post a Comment
Subscribe to Post Comments [Atom]
<< Home