On Jun 29, 2007, at 3:11 AM, Felix Meschberger (JIRA) wrote:
[ https://issues.apache.org/jira/browse/FELIX-314?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel#action_12509034 ]
Felix Meschberger commented on FELIX-314:
-----------------------------------------
if you format the code to look like the existing code[1]
Hmm, looks like the blanks are not there (anymore ?) in parentheses
of arguments, right ? But of course, will do that alignment. No
problem :-)
I think that was the main thing that I saw. :-)
-> richard
EventDispatcher class not reusable in same class loader for
multiple Felix instances
---------------------------------------------------------------------
---------------
Key: FELIX-314
URL: https://issues.apache.org/jira/browse/FELIX-314
Project: Felix
Issue Type: Bug
Components: Framework
Affects Versions: 0.8.0
Reporter: Felix Meschberger
Fix For: 1.0.0
Attachments: FELIX-314.diff, FELIX-314_2.diff
Consider this use case:
Felix felix = new Felix();
felix.start(props, null);
felix.shutdown();
felix = new Felix();
felix.start(props, null);
felix.shutdown();
The first Felix instance will stop the EventDispatcher by calling
the static EventDispatcher.shutdown() method thus stopping the
event dispatcher thread and setting the static variables stopping
and stopped to true. The reference to the event dispatcher thread
in the static variable m_thread is not cleared on shutdown.
The second Felix instance will create an EventDispatcher instance
but the static fields are not reset. That is the event dispatcher
is assumed to be stopped and the event dispatcher thread will not
be newly created and started.
I will suggest a patch for this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
