#21 JVM crash with java-side Exception in combination with Rexx-side 'SIGNAL ON ANY'

411.20130714
closed-invalid
None
5
2014-02-22
2013-10-04
Erik Duijs
No

We're seeing a JVM crash when a REXX script calls a java-method which throws an Exception, but only if there is a 'SIGNAL ON ANY' in the REXX script.

This issue seems to be introduced in 411.20130714 (previous versions work as expected in this case).

The attached java program demonstrates the issue.

1 Attachments

Discussion

  • This ran without a problem for me using 32-bit ooRexx and Java 1.6/6.0.

     
    • status: open --> closed-invalid
    • assigned_to: Rony G. Flatscher
     
  • Erik Duijs
    Erik Duijs
    2013-10-08

    Strange that it's not reproducible. Here I see a clear change between 411.20130714 (also yesterday's .dll) and its preceding version.

    I'm testing on 32bit XP, java 1.6.0_37, Open Object Rexx Version 4.1.1 (Build date: May 16 2012, Addressing Mode: 32), no system-wide BSF4ooRexx installation.

    I did notice that the problematic REXX script actually has an error (although that still shouldn't crash the process).

     
  • Erik,

    in my case exactly using 32-bit XP/SP3, java 1.6.0_45 and ooRexx 4.1.3.

    Your program did not crash the JVM on my machine, neither with the missing ANY label (which is a Rexx coding error), nor with one supplied, such that the Rexx code is syntactically correct.

    Also, please note that the Java stack trace for the thrown RuntimeException is shown by default. Requiring BSF.CLS or setting the appropriate flag (cf. the external function BsfShowErrorMessage(.true|.false) which is set to .false by default if requiring BSF.CLS).

    Maybe you could first try to update Java 1.6 to the latest version and see whether that has an effect. If not please try to replace ooRexx with 4.1.3.

    Please let me know ASAP whether you could get rid of the JVM crash one way or the other or not at all!

    Best regards,

    ---rony

    P.S.: Will add a new status "pending-invalid" and apply it to this bug to keep it open for the time being.

     
    • status: closed-invalid --> pending-invalid
     
  • Hi Erik,

    got some time, so I tested the program on 32-bit XP/SP3, with ooRexx 4.1.3 and the following Javas, each in a new command shell environment:

    • 1.4.2_12-b03
    • 1.5.0_10-b03
    • 1.6.0_45-b06
    • 1.7.0_25-b16 and 1.7.0_40-b43

    None crashed the JVM.

    HTH,

    ---rony

     
    • status: pending-invalid --> closed-invalid