[
http://issues.ops4j.org/jira/browse/PAXRUNNER-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_10763
]
David Leangen commented on PAXRUNNER-43:
----------------------------------------
Some more info...
I inserted some debug logs to test out what's happening here.
When I send the SIGINT (CTRL-C) from the shell, destroyFrameworkOnExit, and
therefore so does process.destroy();
When my daemon sends the SIGTERM signal, the signal is not being caught.
Normally, the JVM is supposed to treat SIGINT, SIGTERM, and SIGHUP the same
way, so I'm not sure what's happening here...
> Unblock platform so exit signals will stop runner
> -------------------------------------------------
>
> Key: PAXRUNNER-43
> URL: http://issues.ops4j.org/jira/browse/PAXRUNNER-43
> Project: Pax Runner
> Issue Type: Bug
> Reporter: David Leangen
> Assignee: Niclas Hedhman
>
> Line 244 of ProcessImpl is a problem:
>
> process.waitFor();
>
> This causes the Pax Runner process to block until the OSGi platform has
> completed it's work. The problem is that even when Pax Runner receives a
> shutdown signal from my daemon, the signal does not get passed to the
> platform process, so the platform continues to run indefinitely.
> Not sure how to fix this, since I don't have all that much experience with
> threads and such, but I'll look into this to provide some suggestions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
