Re: [Wrapper-user] wrapper process is hung

[Leif M. <lei...@ta...>]

Cade,
I am sorry for the trouble.
I replied to you on Stack Overflow.
Please let me know the version of the Wrapper, OS, and content of your
syslog when the JVM was killed.
http://stackoverflow.com/questions/35283549/java-service-wrapper-parent-process-is-hung/35306109

Thanks,
Leif


On Tue, Feb 9, 2016 at 1:41 PM, Cade Thacker <ca...@ca...> wrote:

> Hello All,
> I'm not sure how to figure this out so figured I would turn to the
> experts.
>
> I documented everything here:
>
>
> http://stackoverflow.com/questions/35283549/java-service-wrapper-parent-process-is-hung
>
> But the simple summary is that when I issue a kill $pid (SIGTERM/15) on
> the wrapper process (the JVM is long dead via something else killing it
> with SIGKILL/9) nothing happens. (this is the same call from stopit() in
> the wrapper.sh distributed by you all.
>
> As documented in the other question, that causes other issues downstream
> because without the wrapper dying correctling, I can't restart them both.
>
> Any ideas on how to best trouble shoot this?  I'm not sure what would be
> "stuck" in the wrapper C code so that a SIGTERM would not be properly
> processed? SIGKILL/9 works as expected.
>
> If this was a Java process, I'd get a thread dump and a heap dump, but not
> sure how to attack this C code.  Maybe dig through something in /proc/$pid?
>
> Any help is incredibly appreciated!
>
>
> --
>
> --cade
>