You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2009/09/13 23:02:57 UTC
[jira] Created: (GERONIMO-4871) Something blocking 'kill -3'
signals?
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
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.
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3'
signals?
Posted by "Quintin Beukes (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (GERONIMO-4871) Something blocking 'kill -3'
signals?
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Miller closed GERONIMO-4871.
----------------------------------
Resolution: Cannot Reproduce
Not seeing this problem on 2.2 with Java 6. Java 5 doesn't work, but Java 5 isn't supported on snow leopard, anyway...
> 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.
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3'
signals?
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755016#action_12755016 ]
Kevan Miller commented on GERONIMO-4871:
----------------------------------------
That's good, I guess, but strange. I'm on Mac OS. kill -3 works just fine on G 2.1 (both java 5 and 6), but doesn't work on G 2.2. I'm using geronimo.sh to start (in case that makes a difference).
> 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
>
>
> 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.
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3'
signals?
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770384#action_12770384 ]
Jarek Gawor commented on GERONIMO-4871:
---------------------------------------
I wonder if it is because of jline stuff. Try disabling jline and see if kill -3 works. To disable jline set -Djline.terminal=jline.UnsupportedTerminal property
> 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
>
>
> 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.
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3'
signals?
Posted by "Quintin Beukes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770567#action_12770567 ]
Quintin Beukes commented on GERONIMO-4871:
------------------------------------------
It has to be something that changed between that 2. I'm sure that part is obvious for anyone reading this.
It has to also be something the 2 does different. Perhaps related to a JavaAgent or JMX? Something else that captures the signal?
Have you tried echoing the command geronimo.sh uses to start and then running it manually, removing arguments until you find on that could possibly trigger this? Does the same happen when you run the minimal server? Have you tried to remove modules until you could perhaps find one, which without it everything works?
If I had a Mac I would have a look at it, but ... :>
> 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.
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3'
signals?
Posted by "Quintin Beukes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765170#action_12765170 ]
Quintin Beukes commented on GERONIMO-4871:
------------------------------------------
Works for me on Ubuntu 8.04 with Java6 as well (also started with "sudo geronimo.sh start").
> 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
>
>
> 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.
[jira] Reopened: (GERONIMO-4871) Something blocking 'kill -3'
signals?
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Miller reopened GERONIMO-4871:
------------------------------------
> 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.
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3'
signals?
Posted by "Quintin Beukes (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (GERONIMO-4871) Something blocking 'kill -3'
signals?
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Miller updated GERONIMO-4871:
-----------------------------------
Fix Version/s: (was: 2.2)
2.2.1
Good guess, but doesn't seem to help. Since I created a 2.2.1 release in Jira, moving the fix version to there...
> 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.
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3'
signals?
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770596#action_12770596 ]
Kevan Miller commented on GERONIMO-4871:
----------------------------------------
Thanks for the ideas Quintin.
Agreed that there's something unique in G 2.2. I don't know of any javaagent changes in 2.2. JMX changed, but current branches/2.1 has also changed the way that JMX is started in a 2.1.5-SNAPSHOT server. There are some new/updated libraries in 2.2, also. I'm running geronimo in foreground (geronimo.sh run) and we don't capture STDOUT or redirect to file.
The same Geronimo binary works fine on Linux using the same command to start (i.e. prints thread stacks), testing on Mac OS doesn't work. So, something in 2.2 seems to cause different behavior unique to Mac OS.
In the scheme of things, this is relatively minor. And may well be a Mac OS JDK bug... Will leave it open for now...
> 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.
[jira] Closed: (GERONIMO-4871) Something blocking 'kill -3'
signals?
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Miller closed GERONIMO-4871.
----------------------------------
Resolution: Invalid
Not sure what's going on. I verified that kill -QUIT works on Geronimo 2.2 running on Ubuntu. However, it doesn't work on Mac OS w/ Geronimo 2.2.
Mac OS + G 2.1 works fine, but G 2.2 does not.
> 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
>
>
> 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.
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3'
signals?
Posted by "Quintin Beukes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770576#action_12770576 ]
Quintin Beukes commented on GERONIMO-4871:
------------------------------------------
Check if the -Xrs option is specified perhaps, by echoing the final command used to start the JVM. -Xrs disables this.
Further, try adding a shutdown hook and the doing a SIGTERM. Check if the shutdown hooks execute, but the thread dump doesn't work, or if neither work.
Q
> 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.
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3'
signals?
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755004#action_12755004 ]
Jarek Gawor commented on GERONIMO-4871:
---------------------------------------
Works for me on Ubuntu (with Sun Java 5).
> 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
>
>
> 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.