Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: JRuby 1.0.2, JRuby 1.1b1
-
Fix Version/s: JRuby 1.0.3, JRuby 1.1RC2
-
Component/s: Core Classes/Modules
-
Labels:None
-
Number of attachments :
Description
So, on Windows 2003 Server, trying to run trap("TERM") will cause a lovely IllegalArgumentException, since the JVM on Win32 already uses SIGTERM. This actually makes Rails break totally, since Rails transaction implementation uses TERM for each transaction. Kaboom.
The good answer here is to rescue all exceptions and print a generic warning that that signal isn't supported on the platform. This allows other signals to work, and isn't worse than not having signals. (Remember, we're using Sun's internal Signal implementation - not really supported).
Issue Links
| This issue duplicates: | ||||
| JRUBY-1277 | Mongrel clashes with JVM for the right to handle SIGUSR1 |
|
|
|
Fixed.