-
1. Re: 3.2.4 Release Tasks
adrian.brock Mar 30, 2004 9:43 PM (in response to starksm64)Hi Ivelin,
The idea is to add support for CMT transaction time-out config in jboss.xml
Something like:<assembly-descriptor> <container-transaction> <method> <ejb-name>StatelessSessionBean</ejb-name> <method-name>*</method-name> </method> <transaction-timeout>2000</transaction-timeout> </container-transaction> <container-transaction> <method> <ejb-name>StatelessSessionBean</ejb-name> <method-name>takesALongTime</method-name> </method> <transaction-timeout>10000</transaction-timeout> </container-transaction> </assembly-descriptor> </jboss>
You can use TransactionManager.setTransactionTimeout() to set the thread local
to accomplish this, but...
There is no portable mechanism to reset the value.
You cannot get the previous value or the default value.
This would require an alternate interface on our TxManager
and probably just drop the feature when a third party transaction manager
does not implement the interface.
e.g.
public interface org.jboss.tm.TransactionManagerExtensions
{
long getTransactionTImeout()
} -
2. Re: 3.2.4 Release Tasks
adrian.brock Apr 14, 2004 12:15 PM (in response to starksm64)CMT transaction timeout overrides is done.
It is configured using method attributes in jboss.xml (values are in seconds), e.g.<jboss> <enterprise-beans> <session> <ejb-name>TxTimeout</ejb-name> <jndi-name>jbosstest/tm/TxTimeout</jndi-name> <method-attributes> <method> <method-name>testOverriddenTimeoutExpires</method-name> <transaction-timeout>5</transaction-timeout> </method> <method> <method-name>testOverriddenTimeoutDoesNotExpire</method-name> <transaction-timeout>20</transaction-timeout> </method> </method-attributes> </session> </enterprise-beans> </jboss>
-
3. Re: 3.2.4 Release Tasks
adrian.brock May 27, 2004 3:42 AM (in response to starksm64)5 tests to fix in 3.2 testsuite
org.jboss.test.cache.test.replicated.SyncTxUnitTestCase
Is timing out - not investigated
org.jboss.test.management.test.JSR77SpecUnitTestCase#testNavigation
Is failing because Tomcat is returning a String when it should be returning an ObjectName
See Bug#961330
org.jboss.test.naming.test.SecurityUnitTestCase#testSecureHttpInvoker
Is failing because there is no login-config setup for "http-invoker"
org.jboss.test.naming.test.SimpleUnitTestCase#testNameChanges
Is failing because the Name is changed by the NamingContext
org.jboss.test.testbeancluster.test.BeanUnitTestCase#BeanUnitTestCase#testAllTypesBean
Is failing because the two serialized handles are different. This looks to be
something in the load balancing policy (possibly the new birth target?).
When I drill down into the Object graph they look the same (except for
different instances) but they do have different serialized bytes.