Red Hat Bugzilla – Bug 1010961
:reload operation does not activate hornetq object store to be used
Last modified: 2013-12-15 08:32:32 EST
I found out that reload operation on AS server does not activate hornetq object store to be used.
When I set in cli:
the XML config file contains correct element. The reload is required. But when I run reload the standard file system object store is still in usage.
There is no message like:
TRACE [com.arjuna.ats.arjuna] (MSC service thread 1-8) HornetqObjectStore.start()
I need to reboot server to get the hornetq store in action.
Checked for EAP 6.2.0.ER1.
To reproduce use settings of the logging like:
And run $JBOSS_HOME/bin/jboss-cli.sh.
You can compare the logs with case when you set tag
under transactions subsystem by hand in XML.
I am not sure what to expect here. I do:
git diff standalone/configuration/standalone.xml
Shows some formatting issues and
Is this not what we expect?
my problem is that when it seems that HornetQ is not started after reload. When I do reboot (stop jboss and start again) then the HornetQ object store is used.
But when I start jboss with standard file system store, set it as attribute and run reload then the standard file system object store is used and it's not switched to the hornetq object store after the restart.
This could be observed when you run some app and check the data directory or when you check the log with trace level. When hornetq is used then after start/reload you should see message HornetqObjectStore.start() somewhere in the log.
Ah, are you expecting to not need to reboot the server after changing the object store in use? This is not how Narayana works, the object store is set when the transaction manager launches and can't be altered without a restart of the transaction manager.
Ah, ok, then... I didn't realize that before. Sorry for creating this bug.
Summary: This is not a bug this is expected behavior. Narayana needs to be restarted to start to use new object store.