JRebel Remote Server Troubleshooter

This chapter details the most common problems with JRebel remote server support.


Modifying the configuration must be followed by a redeploy

Whenever you change the JRebel remote server support configuration, you should redeploy your application to the server. Why? Because your configuration changes need to be reflected on the remote server. Unless your workstation and the remote server are in sync, remote server support will not work properly.


Enabling JRebel remote server support debug level log

When experiencing issues, it would be wise to enable debug level logging for JRebel remote server support. Follow the IDE manual chapters for instructions on how to do this.


Common error messages

The following is a list of the most common error messages encountered when using JRebel remote server support. We have provided the error message as well as the most common solution for resolving it.

  • JRebel remote server did not respond - this error message can occur in multiple situations. For starters, try disabling encryption (where enabled). Disabling encryption allows you to get more information on error states.

  • Encryption not enabled on server side - this can occur when you enable encryption on the client/IDE side and do not redeploy the new configuration to the server. Simply ensure that you have redeployed your fresh configuration to the server.

  • Encryption not enabled on client side - this happens when the server has been configured to encrypt data and the client side hasn’t. Enable JRebel remote server support data encryption in your IDE to resolve this.