-
Notifications
You must be signed in to change notification settings - Fork 8
jmx-plugin - Tidy up JMX attribute dialog #7
Comments
@davsclaus wouldn't mind some feedback on this change also, switched this dialog to hawtio-form-2 and reworked it a bit so the value is show via hawtio-editor, so big values are easier to look at. |
I found this in jolokia 1.1 js error proxying to "http://localhost:8282/hawtio/jolokia/": Error: connect ECONNREFUSED I do not have any ENV setup that uses 8282 etc davsclaus: |
Have you tried clearing your local storage by any chance? On Thu, May 28, 2015, 3:51 AM Claus Ibsen notifications@github.com wrote:
|
Yes its still the same problem. I havent found a nice ui in chrome so I clear from the js console
|
So when running 'gulp' the gulpfile sets up a proxy for /jolokia, it's set up out of the box to hit an instance started from "hawtio-web" in the hawtio 1.x branch via "mvn exec java -DstartLR=false". Let me see if I can tidy up that error a bit now that I can see what's going on :-) Was just going to post that I haven't been able to reproduce it... |
Ah yeah I found the port 8282 which was hardcoded in the gulp settings file. So I kind though that that a Java JVM was needed to run along side. Though I recall using hawtio-jmx in the past without having a JVM running. |
Yeah, you should be able to and then use the connect dialog... about to push a fix for it + some improved logging. BTW, the local storage reset button is back in the preferences. |
@davsclaus should be better now... |
Hm, should probably not bother showing a jolokia url for any ObjectName attribute, those are calculated locally. |
+1 to not show the jolokia url - its more of a distraction for the end users / and maybe also a bit confusing for some users what it is. |
@gashcrumb this looks much better. |
The layout of this dialog could use some work, might just be a matter of switching it to the form2 plugin. Also perhaps using hawtio-editor instead of the textarea for any json that shows up would be good.
The text was updated successfully, but these errors were encountered: