New update on 9/5/01 by ###@###.###: Borland has just reported the same problem happens on Solaris as well.

-----------
Borland has hit a serious problem with the 1.3.1_01_20010807 pre-release we gave
them. This only occurs on Windows (we've tested on 2000), not Solaris. The
symptom is:

C:\Inprise\ejuju50b202\bin>"C:\Program
Files\JavaSoft\jdk1.3.1_01_20010807\bin\java"
"-Djava.class.path=C:\Inprise\ejuju50b202\lib\xmlrt.jar;C:\Inprise\ejuju50b2
02\lib\guicore.jar;C:\Inprise\ejuju50b202\lib\primetime.jar;C:\Inprise\ejuju
50b202\lib\console.jar" -Xrs com.borland.console.Console

java.lang.IllegalArgumentException: Signal already used by VM: SIGINT
        at sun.misc.Signal.handle(Signal.java:152)
        at java.lang.Terminator.setup(Terminator.java:42)
        at java.lang.Shutdown.add(Shutdown.java:88)
        at java.lang.Runtime.addShutdownHook(Runtime.java:193)
        at sun.awt.windows.WToolkit.run(WToolkit.java:174)
        at java.lang.Thread.run(Thread.java:484)

As you can see, this occurs with java.exe, not our launcher. The -Xrs flag
trips the exception.


Attached is a trivial 3-line test case that shows the problem. Simply javac
and run with -Xrs using jdk 1.3.1_01_20010807 on windows 2000 to see the
exception.

C:\Temp\sigint bug>"C:\Program
Files\JavaSoft\jdk1.3.1_01_20010807\bin\java" -classpath . -Xrs Test
Exception in thread "main" java.lang.IllegalArgumentException: Signal
already used by VM: SIGINT
        at sun.misc.Signal.handle(Signal.java:152)
        at java.lang.Terminator.setup(Terminator.java:42)
        at java.lang.Shutdown.add(Shutdown.java:88)
        at java.lang.Runtime.addShutdownHook(Runtime.java:193)
        at Test.main(test.java:6)