DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25232>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25232 [procrun] Problems if forked program redirects console handles Summary: [procrun] Problems if forked program redirects console handles Product: Commons Version: 1.0 Alpha Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: Daemon AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] At least in certain cases, when you are running with the forked option, and the client program redirects it's output by itself, procrun will start to spin wildly. The problem is that the stdout_thread and/or the stderr_thread terminates and signals the main thread. This signal is never reset, so the program goes into a tight WaitForMultipleObject loop (since one is always signaled). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
