[BUG] Monitoring and Profiling Page connection to JMX Servlet returns 403 Forbidden

[aljopainter]

Describe the bug
From the Elemental Menu Bar option "Open Monitoring and Profiling", a 403 error is returned by the attempted connection to the JMX Servlet.

Expected behavior
It seems that, as a result of the error in the JMX Servlet connection, no information is provided in the Monitoring page, either blank or with zero values. We should see that page populated with the different statistics.

To Reproduce

1. Start Elemental Server. (On my Mac, this is from, for example, Launchpad).
2. Select Elemental Menu Bar item "Open Monitoring and Profiling"
3. This item opens, in my installation, the URL: http://localhost:8080/exist/apps/doc/scheduler
4. When the browser page opens (on my Mac, either in Chrome or Safari), a red error text shows near the top of the page: Alert! Connection to server failed. Retrying ...
5. In the developer tools menu, the error connection URL is, on my Mac: http://localhost:8080/exist/status?c=instances&c=processes&c=locking&c=memory&c=caches&c=system&c=operatingsystem&token=false
6. In an attempt to obtain more information, I opened the URL in (5) in the browser directly, which displays:

HTTP ERROR 403 Access allowed for localhost, or when correct token has been provided.<
URI:403
Access allowed for localhost, or when correct token has been provided.
JMXServlet

Screenshots

Context (please always complete the following information)

• Version: [Elemental 7.1.0]
• Java: [Temurin-21.0.7+6 (build 21.0.7+6-LTS)
• OS: [macOS X 15.5]

Additional context

• How is Elemental installed? [e.g. JAR installer, DMG, … ]
  ** homebrew
• Any custom changes in e.g. conf.xml?
  ** none

[lguariento]

I do get that error as well from time to time; all I do is force-refresh and the connection is established. Did you compare with an installation with .dmg to se eif you get the same behaviour?

[aljopainter]

Force-refresh does not change anything for me (using Chrome and Safari). I do need to re-enter the admin credentials upon force refresh.

Just to be sure: the URL of the monitoring page is: http://localhost:8080/exist/apps/monex/index.html

[adamretter]

@aljopainter Thanks for your Bug Report. Two things were required to fix this:

1. Making Monex 100% compatible with Elemental (or eXist-db) 7.x.x - this was a non-trivial amount of work and we opened a PR against Monex for those fixes here: Make Monex compatible with eXist-db 6.x.x and 7.x.x eXist-db/monex#298
   It would be great if you could add your support to that issue!

2. Making sure the localhost is correctly recognised when retrieving JMX stats for Monex - [7.x.x] Fix issues with Monitoring and Profiling as used by tools like Monex #10

I do get that error as well from time to time; all I do is force-refresh and the connection is established.

@lguariento We also identified the cause of that issue and believe that we have now fixed that too, so it should now work both first time and every time in the next release of Elemental.

[aljopainter]

I'll give a try as soon as I can .. probably tomorrow. Thanks!