Multiple CALL dbms.queryJmx("org.neo4j:*") queries slowing down database

[inersha (Greg Walker)]

This appears to be due to a bit of a serious browser bug. Here is the explanation by Max De Marzi from the Slack channel:

Restart Neo4j with all browser tabs closed.

That jmx query is sent to the server for every query you send via the browser and every 20 seconds.

The jmx query requests everything, it shouldn’t. Fix goes out next Monday.

If the jmx query runs into a heavy write transaction, it asks for which nodes/rels are locked and the lock manager created a billion strings for each one and it basically makes so much garbage memory it kills Neo4j.

Run queries via the shell until the browser update.