[
https://issues.apache.org/jira/browse/FELIX-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770887#action_12770887
]
Karl Pauls commented on FELIX-1816:
-----------------------------------
This doesn't seem to be correct in the sense that the systembundle.stop isn't
the only thing contributing to the deadlock. The shutdownhook in the launcher
is running and causing your problems again. Are you ctrl-c'ing or sending kill
signals to the jvm externally? Just have a look at the stacktrace:
"SIGTERM handler" daemon prio=9 tid=0x0000000102830800 nid=0x114b94000 in
Object.wait() [0x0000000114b93000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x000000010637fa10> (a org.apache.felix.main.Main$1)
at java.lang.Thread.join(Thread.java:1167)
- locked <0x000000010637fa10> (a org.apache.felix.main.Main$1)
at java.lang.Thread.join(Thread.java:1220)
at
java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:79)
at
java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:24)
at java.lang.Shutdown.runHooks(Shutdown.java:79)
at java.lang.Shutdown.sequence(Shutdown.java:123)
at java.lang.Shutdown.exit(Shutdown.java:168)
- locked <0x000000010ba5b830> (a java.lang.Class for java.lang.Shutdown)
at java.lang.Terminator$1.handle(Terminator.java:35)
at sun.misc.Signal$1.run(Signal.java:195)
at java.lang.Thread.run(Thread.java:637)
The jvm is getting a SIGTERM. Notice, in the other issue the stacktrace didn't
contain a SIGTERM but just the call to system exit. If you don't do anything
externally please attach an example again so that i can try to reproduce.
Anyways, I will have to investigate as a control-c together with a
systembundle.stop shouldn't deadlock in the first place. Thanks for reporting
:-)
> deadlock on SystemBundle.stop()
> -------------------------------
>
> Key: FELIX-1816
> URL: https://issues.apache.org/jira/browse/FELIX-1816
> Project: Felix
> Issue Type: Bug
> Affects Versions: felix-2.0.1
> Reporter: Dennis Geurts
> Attachments: trace.log
>
>
> When one calls SystemBundle.stop within BundleActivator.start(BundleContext)
> a deadlock occurs.
> I will attach a stacktrace.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
