Possibility of stack overflow with IBM JVM and class loading delegation

I saw similar problems in the log but related to the reflectASM generated classes. We need to have a protection here that we never end in the loop. We can solve this with the thread local in the HookDelegationSensor so that we never enter the same method twice with same class name. It's also interesting why our class loader can not load the class needed here.

The class names are rocks.inspectit...ConstructorAcess but our class loader can not load it as they are not there. These are generated by the reflect asm