Troubleshooting issues with JRebel Broker

Detect problems with connected JVMs, debug, and view logs.

View connected JVMs via the admin UI

Monitor the broker’s state through its admin UI.

  1. In your browser, open the admin UI URL (for example, http://localhost:8000).

  2. Log in with your username (for example, admin) and password (the token value you defined in the config.admin-ui.token option in your config.yml file).

  3. View connected JVMs under View information.

Verify broker connections via the API

Use the following calls to debug via the API:

  • To list all zones, run:

curl -H "Authorization: Bearer <token>" http://localhost:8000/rest/zone

  • To list all connected JVMs, run:

curl -H "Authorization: Bearer <token>" http://localhost:8000/rest/agent/jvm

  • To list IDEs, run:

curl -H "Authorization: Bearer <token>" http://localhost:8000/rest/agent/ide

View Logs

View the following logs for more information:

  • JRebel Broker Log: the location is defined in -Dlogging.file.name (for example, /var/log/broker/broker.log).

  • JRebel Agent Log: the default location is ~/.jrebel/jrebel.log.