geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Quintin Beukes (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-4871) Something blocking 'kill -3' signals?
Date Tue, 27 Oct 2009 17:16:59 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770581#action_12770581
] 

Quintin Beukes commented on GERONIMO-4871:
------------------------------------------

One final note.

Perhaps the logging level is configured differently. Try setting the log levels to trace on
the Geronimo logging and the JRE logging - in fact, on all logging frameworks accessible.
Maybe somehow it logs to another file somewhere.

I had a look around on google, and it does seem like there are cases where people had to change
their logging levels in order to see the thread dumps.


> 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.


Mime
View raw message