I'm using ActiveMQ 5.9.0 that has a amazing HawtIO interface. So when 5.10.0 has come, I migrated my system too. Now I see that the HawtIO interface doesn't exist inside it... It just disappeared from webapps folder from 5.9.0 to 5.10.0, so I tried the tutorial ActiveMQ and HawtIO but it doesn't work... How to configure the interface?
相关问题
- slurm: use a control node also for computing
- JFX scale image up and down to parent
- How to read a string array in appSettings.json?
- Swing Font Rendering
- Visual Studio 2015 : SQL Data Source : Unable to r
相关文章
- Algorithm for maximizing coverage of rectangular a
- Is there a way to hide the new HTML5 spinbox contr
- Can keyboard of type UIKeyboardTypeNamePhonePad be
- PropertyGrid - Possible to have a file/directory s
- Programming a touch screen application with SWING
- Can WM_NEXTDLGCTL be used with non-dialog windows?
- How can I create a small IDLE-like Python Shell in
- How to use relative line numbering universally in
As stated in Erik Williams answer:
change jetty.xml to include this webapp as a folder
On the default 5.10.0 standalone setup we also had to add three security paramaters to enable the brokers security. This can be done in the activmemq or activemq.bat file. Add these settings to the ACTIVEMQ_OPTS variable:
We did not have to remove the slf4j jar, it was not present.
Alternatively, you can use HawtIO as a standalone web-app, that connects to ActiveMQ through Jolokia (pre 5.9 way of doing it).
java -jar hawtio-app-1.4.37.jar
(put the command in a .bat-script and add a scheduled task if you want it to run on startup..)your server
:8080/hawtiolocalhost
as host,8161
as port andapi/jolokia
as path.Connect, and enjoy!
Yeah I'm not entirely sure why they choose to do this, as it was a pretty big feature they'd been touting.
In any case, its pretty simple to set up yourself by downloading hawt-io itself and installing it as it was in 5.9 if you cannot get the stand alone method to work.
You'll need to decompress (or at least this is how I did it) the WAR and set up the jetty.xml as it was set up in 5.9 to include hawt.io as an application.
If I recall, I think I also ran into some class-loading conflicts due to some classes that come included with hawt.io that were newer than what was installed with the broker.