Signal#trap doesn't handle failure of trapping gracefully.
----------------------------------------------------------
Key: JRUBY-1581
URL: http://jira.codehaus.org/browse/JRUBY-1581
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affects Versions: JRuby 1.1b1, JRuby 1.0.2
Reporter: Ola Bini
Assignee: Ola Bini
Fix For: JRuby 1.0.3, JRuby 1.1
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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
