Hi, I've got a question about thread dumps from background processes and log4j.
In our product we redirect System.err and System.out through our debugging class and on to log4j so that any output the program produces is logged for debugging purposes. We are having some problems with the JVM thread dump information going missing. The Sun docs state that when a thread dump is generated (by sending a SIGQUIT to the process) it should be printed on the standard error device. This is fine if the product is being run as the foreground process in a console window. However, the thread dump information is printed to the console window. If the product is being run as a background process and a SIGQUIT is sent, the thread dump information is lost. It is not printed out in the window that started the process and it isn't redirected to the log. Is there any way to redirect this information to the log? Is there some other error device that I have overlooked in this case that we should be redirecting to the log? Any help would be appreciated. Paul -- Paul Graham Software Engineer Prismtech Ltd, UK http://www.prismtechnologies.com -- To unsubscribe, e-mail: <mailto:log4j-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:log4j-dev-help@;jakarta.apache.org>
