Weird replacement of STDOUT by /dev/null
----------------------------------------
Key: JRUBY-4639
URL: http://jira.codehaus.org/browse/JRUBY-4639
Project: JRuby
Issue Type: Bug
Environment: # jruby --version
jruby 1.4.0 (ruby 1.8.7 patchlevel 174) (2009-12-14 943d51c) (Java HotSpot(TM)
64-Bit Server VM 1.6.0_16) [amd64-java]
Reporter: Xuân Baldauf
Assignee: Thomas E Enebo
A long running rails metal over jruby application using glassfish "stopped"
suddenly. Well, it did not quite stop, but it stopped doing output (and some
parts of the app stopped to, but this is not diagnosable, as output stopped).
The observation is that filedescriptor #1 (stdout) does not point to the log
file (as initially redirected), but to /dev/null. Note that this filedescriptor
does not appear to be simply closed, but somehow closed-and-replaced.
It happens on a multi-threading app running on 2 cores which does about
100'000'000 "puts" statements and needs a week's running time on average until
this issue appears, but then it is there. It has happened twice so far, on
different machines.
--
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
