[
https://issues.jboss.org/browse/JBTM-852?page=com.atlassian.jira.plugin.s...
]
Andrew Dinn commented on JBTM-852:
----------------------------------
XTS writes both coordinator and participant recovery records to the recovery store
obtained by calling StoreManager.getRecoveryStore(). I don't believe changing the
config to use an in-memory store raises any special difficulties as far as XTS is
concerned -- other than the fact that the coordinator and participant web service may not
reside in the same JVM/on the same host (i.e. there may be more than one store in play
which you might need to reconfigure).
Setting SettingVolatile store still creates an ObjectStore directory
on the disk
---------------------------------------------------------------------------------
Key: JBTM-852
URL:
https://issues.jboss.org/browse/JBTM-852
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.15.0
Reporter: Mircea Markus
Priority: Minor
Even when configuring {code:java}
arjPropertyManager.getObjectStoreEnvironmentBean().setObjectStoreType(VolatileStore.class.getName())
{code} an "ObjectStore" directory is created on the disk. After discussing with
JTM team this doesn't cause any real problem in the sense that nothing is written to
the disk, but this is annoying and might create confusion between the users.
A workaround would be to add the following configuration together with the previously
mentioned one:
{code:java} BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class,
"communicationStore").setObjectStoreType(VolatileStore.class.getName()) {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira