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