There are use cases where a Java method gets invoked via the Rexx Java proxy taking advantage of the unknown mechanism in BSF, which will cause on the Java side a call back into Rexx (e.g. Rexx event handler for a Java object in another RexxActivation) which then may cause a call from Rexx to Java using the same BSF object which will hang as the unknown method is by default a guarded method.
Fixed in [r405].
Related
Commit: [r405]