Remote console (websockets) regression

[joewiz]

Problem: Requests to ws://localhost:8080/exist/rconsole fail return a 404 with monex 1.0.0 and 1.0.1, whereas the 0.9.16 release does not exhibit this error.

Background: As reported on exist-open by @craigberry and confirmed by @simar0at:

I'm trying to debug something with eXist-db 4.7.0 which apparently comes with monex 1.0.1. Any attempt to open the remote console fails and leaves something like the following in the JavaScript console:

WebSocket connection to 'ws://localhost:8080/exist/rconsole' failed: Unexpected response code: 404

I can reproduce the exact same problem with eXist 4.7.0 running on macOS Mojave, RHEL 7.6, and Ubuntu 16.04.

@simar0at added:

I also saw that problem yesterday with our instances of exist-db 4.3.1 which offered 1.0.1 as an upgrade to Monex which I installed... I installed the 0.9.16 monex xar and things work as expected.

@craigberry confirmed:

Thanks. That trick worked for me as well with eXist 4.7.0. First I uninstalled monex, then installed the 0.9.16 monex xar, then restarted eXist. I now have a functioning remote console.

[craigberry]

monex 1.0.0 has the same error. And it is downgrading to 0.9.16, not 0.9.6, that has been confirmed to work.

[duncdrum]

see eXist-db/e2e-core#24 and the community call notes, this is the 404 behaviour i see on docker as well

[joewiz]

@duncdrum During the community call, I thought we were talking about monex 2.x. I couldn't reproduce any problems with the rconsole/websockets on monex 2.x with 5.0.0-develop. Are you seeing problems in 2.x too, or just 1.x?

[duncdrum]

as you can see in the logs both on 4.7 and 5.0.0-RC8-Snapshot

[duncdrum]

see eXist-db/exist#2880

[joewiz]

I can reproduce the report of the remote console pane not working under monex 1.0.1 + eXist 4.7.0. Also, I can confirm that downgrading to monex 0.9.16 (by downloading it from the public-repo's website and installing the xar via Package Manager) and restarting eXist restores the remote console pane functionality of monex.

However, with monex 2.0.2 + eXist develop (5.0.0), the console pane works fine.

Could it be that the more severe problems we're seeing with monex 1.0.1 are because we didn't backport #88 to the monex-1.x branch?

[line-o]

@joewiz what is the status of this issue? Was it fixed in the meantime?

[joewiz]

@line-o It's awaiting resources for a fix by someone invested in using monex under eXist 4.x.

[line-o]

@joewiz can we close this issue now that exist 4 is no longer maintained?

[line-o]

However, with monex 2.0.2 + eXist develop (5.0.0), the console pane works fine.

We might check how many times monex 1.x.x is still downloaded.

[pherk]

download numbers might not represent the user base still have to use 4.x.x (betterforms ;-)

I recently upgraded from 4.4.3 to 4.12-snapshot.
Monex console showed the known problems to connect to rconsole (see above).
Today I tried downgrading Monex to 0.9.16, after restarting existdb Firefox console shows:
Uncaught TypeError: Unable to process binding "with: function(){return findByName($data.jmx.CacheManager(),'org.exist.management.exist:type=CacheManager') }"
Message: $data.jmx.CacheManager is not a function
... from knockout-3.1.0

regards
Peter