[
https://issues.jboss.org/browse/JBTM-852?page=com.atlassian.jira.plugin.s...
]
Michael Musgrove resolved JBTM-852.
-----------------------------------
Resolution: Done
There is no fix because this is testing a condition that we haven't previously had a
fix for.
There was an issue with the test which I fix with commit
f6a9f949b3d01e7dc587d2a25eb0cb9fb6cabd20. The following job
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-java6/1170
shows the test passing so I am moving the jira back to resolved.
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
Assignee: Michael Musgrove
Priority: Minor
Fix For: 5.0.0.M2
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira