[
https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770583#action_12770583
]
Quintin Beukes commented on GERONIMO-4871:
------------------------------------------
Unless I imagined things, it looks like Geronimo is now capturing stdout/stderr
and sending it to the geronimo.log instead of geronimo.out. And also depending
on the output type it prints a progress bar. This wasn't the case in 2.1. I had
to look at all my System.out.println() statements in geronimo.out, where the
other day I found they were being sent to geronimo.log after the server
completed starting.
If this is programmatically, maybe it's related to this. It comes back to my
previous comment. Maybe it IS doing the thread dump, you just can't find to
where, or the pipe is broken and it goes into nothingness.
> Something blocking 'kill -3' signals?
> -------------------------------------
>
> Key: GERONIMO-4871
> URL: https://issues.apache.org/jira/browse/GERONIMO-4871
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Kevan Miller
> Fix For: 2.2.1
>
>
> I occasionally use 'kill -3' to cause a java process to dump all thread
> stacks. For some reason, this isn't working on Geronimo 2.2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
