Forceable termination of Felix instance leaves global EventDispatcher in
non-restartable state
----------------------------------------------------------------------------------------------
Key: FELIX-363
URL: https://issues.apache.org/jira/browse/FELIX-363
Project: Felix
Issue Type: Bug
Components: Framework
Reporter: Rob Walker
Assignee: Rob Walker
FELIX-314 fixed an issue where internal shutdown of the global EventDispatcher
thread left Felx in a state where new instances could not be started within the
same VM at a later time.
It seems in an Applet VM environment using JRE 1.6 and IE7 there is a variation
on this case where the Applet VM is forcibly killing VM threads not cleanly
terminated by the application itself e.g. a sloppily written Applet (like
ours!) which launched a Felix instance in the start() but didn't shut it down
in the stop().
Such a forceable termination is not tracked or detected, and hence leads to a
similar inability to start additional Felix instances as was being seen in
FELIX-314
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
