JRebel support

^{from version 1.5}

All users that are using JRebel for hot-code replacement and inspectIT for performance diagnosis during development will be happy to hear that inspectIT now works 100% flawless when JRebel is active. The new version solved some issues that were raised when JRebel updates the class being monitored with inspectIT. In addition, the inspectIT now enables monitoring of all method and constructors when they are changed and updated by JRebel, even when new methods/constructors are added.

Setup

If you are using JRebel and inspectIT on the same application server, the only thing you need to do is add jRebel=true to the sensor definition. For example:

method-sensor-type timer info.novatec.inspectit.agent.sensor.method.timer.TimerSensor MAX jRebel=true

Monitoring of added/changed methods or constructors

With Jrebel option being active on the sensor you will be able to get performance data also from the methods/constructors that have been changed or added. However, please note that the class that executes these methods and constructors will not have the same name as the original class. In addition, the constructors will be noted with __init__ method, instead of classical class name method. The following image describes the updated class/method names when TestClass is being updated by JRebel.