-
-
-
3. Re: JMX Changes in 2.2.5?
jay.moss Jul 1, 2011 10:58 AM (in response to jay.moss)Clebert,
I'm guessing that it's perhaps something to do with security (since what I'm seeing matches in both MX4j & JConsole, I'm ruling out the JMX Console side of the equation). In hornetq-configuration.xml, i have the following:
<security-settings> <security-setting match="#"> <permission type="createTempQueue" roles="guest" /> <permission type="deleteTempQueue" roles="guest" /> <permission type="consume" roles="guest" /> <permission type="send" roles="guest" /> <permission type="manage" roles="guest" /> </security-setting> </security-settings> ...and:
<security-enabled>false</security-enabled>
I have a single user named guest with a password and the role of guest. Are there security changes between 2.1.2 & 2.2.5? I haven't seen anything in the Docs, but perhaps there's more enforcement now?
-
4. Re: JMX Changes in 2.2.5?
jay.moss Jul 1, 2011 11:59 AM (in response to jay.moss)OK, figured it out. Believe it or not, it's as simple deleting the data directory every time you change versions.
Switching from 2.1.2 to 2.2.5 without deleting the data directory doesn't give any errors, but the queues don't actually work right with the old data directory (can't connect or see the queueus).
When I switch back to 2.1.2 it throws an error and I have to delete the data directory to get it to start correctly.