[ https://issues.jboss.org/browse/ISPN-957?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-957: ------------------------------- Description: Suite runs faster with JBossTM (vs DummyTM). A explanation for JBossTM over performing DummyTM in spite keeping a tx log on the disk (which dummyTm doesn't) is the fact that it has 2PC optimisations for situations where only one resource is registered. In other words if there is only one cache participating in the transaction (most of our tests are like that) there won't be 2RPC but only one. It would be good to run the local test suite with JBossTM and CoordinatorEnvironmentBean.commitOnePhase=true and CoordinatorEnvironmentBean.commitOnePhase=false on the hudson environment. This would test transactions better. was: Suite runs faster with JBossTM (vs DummyTM). A explanation for JBossTM over performing DummyTM in spite keeping a tx log on the disk (which dummyTm doesn't) is the fact that it has 2PC optimisations for situations where only one resource is registered. In other words if there is only one cache participating in the transaction (most of our tests are like that) there won't be 2RPC but only one. It would be good to run the local test suite with JBossTM and CoordinatorEnvironmentBean.commitOnePhase=true and CoordinatorEnvironmentBean.commitOnePhase=false on the hudson environment. This would be good for performance. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-957?page=com.atlassian.jira.plugin.s... ] Manik Surtani commented on ISPN-957: ------------------------------------ No, we should *always* run with commitOnePhase=false even locally; otherwise you won't be trapping much. However, what we *should* do is disable writing tx logs to disk. That is a valid optimisation for using JBossTS in our test suite. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-957?page=com.atlassian.jira.plugin.s... ] Mircea Markus commented on ISPN-957: ------------------------------------ in-memory logging was added in JBossTS 4.9. This works only for test cases where you don't need crash recovery. Note that the config is frozen at system initialization time, so you need to set this before classloading the transaction system and can't change it within the same vm. junit setupClass or such should be fine. import com.arjuna.ats.arjuna.common.arjPropertyManager; arjPropertyManager.getCoordinatorEnvironmentBean().setActionStore(com.arjuna.ats.internal.arjuna.objectstore.VolatileStore.class.getName()); arjPropertyManager.getObjectStoreEnvironmentBean().setObjectStoreType(com.arjuna.ats.internal.arjuna.objectstore.VolatileStore.class.getName()); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-957?page=com.atlassian.jira.plugin.s... ] Manik Surtani resolved ISPN-957. -------------------------------- Resolution: Done -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira