[jira] Created: (FELIX-1057) stopping bundle causes NPE
stopping bundle causes NPE -- Key: FELIX-1057 URL: https://issues.apache.org/jira/browse/FELIX-1057 Project: Felix Issue Type: Bug Components: Remote Shell Affects Versions: shell.remote-1.0.4 Reporter: Peter Doornbosch Priority: Minor Stopping the remote shell bundle itself remotely, causes a NPE: Exception in thread telnetconsole.shell remote=/127.0.0.1:56512 java.lang.NullPointerException at org.apache.felix.shell.remote.TerminalPrintStream.print(TerminalPrintStream.java:52) I admit that stopping the bundle itself over the remote connection may seem like a silly use case, but under circumstances it is necessary (to release the socket). The NPE is causes by Activator.getServices() returning null. The fix is trivial: ServiceMediator services = Activator.getServices(); if (services != null) services.error(...) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1057) stopping bundle causes NPE
[ https://issues.apache.org/jira/browse/FELIX-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Doornbosch closed FELIX-1057. --- Yeah, i noticed the concurrency issues too, but didn't want to be a nag ;-). Thanks for fixing this. Keep up the good work! stopping bundle causes NPE -- Key: FELIX-1057 URL: https://issues.apache.org/jira/browse/FELIX-1057 Project: Felix Issue Type: Bug Components: Remote Shell Affects Versions: shell.remote-1.0.4 Reporter: Peter Doornbosch Assignee: Richard S. Hall Priority: Minor Fix For: shell.remote-1.0.5 Stopping the remote shell bundle itself remotely, causes a NPE: Exception in thread telnetconsole.shell remote=/127.0.0.1:56512 java.lang.NullPointerException at org.apache.felix.shell.remote.TerminalPrintStream.print(TerminalPrintStream.java:52) I admit that stopping the bundle itself over the remote connection may seem like a silly use case, but under circumstances it is necessary (to release the socket). The NPE is causes by Activator.getServices() returning null. The fix is trivial: ServiceMediator services = Activator.getServices(); if (services != null) services.error(...) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-740) ConfigurationManager throws NPE when bundle that registered service is uninstalled
ConfigurationManager throws NPE when bundle that registered service is
uninstalled
--
Key: FELIX-740
URL: https://issues.apache.org/jira/browse/FELIX-740
Project: Felix
Issue Type: Bug
Components: Configuration Admin
Affects Versions: configadmin-1.0.4
Reporter: Peter Doornbosch
Priority: Minor
Sometimes, a NullPointerException is thrown in the ConfigAdmin's update thread,
that is originating from the following piece of code (ConfigurationManager):
private class ManagedServiceFactoryUpdate implements Runnable
(...)
public void run()
{
Factory factory;
try
{
factory = getFactory( factoryPid );
}
catch ( IOException ioe )
{
log( LogService.LOG_ERROR, Cannot get factory mapping for
factory PID + factoryPid, ioe );
return;
}
String bundleLocation = sr.getBundle().getLocation();
The NPE occurs in the last line. From the context it is clear that sr is not
null, hence, sr.getBundle() returns null.
Probably, this is caused by a bundle that is stopped concurrently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-542) log a warning / error when a fragment bundle is installed or started
[ https://issues.apache.org/jira/browse/FELIX-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Doornbosch updated FELIX-542: --- Attachment: bundle-fragment-warning.patch suggested patch log a warning / error when a fragment bundle is installed or started Key: FELIX-542 URL: https://issues.apache.org/jira/browse/FELIX-542 Project: Felix Issue Type: Improvement Components: Framework Affects Versions: felix-1.0.3 Reporter: Peter Doornbosch Priority: Minor Attachments: bundle-fragment-warning.patch As discussed on the mailing list, it would be nice if Felix would warn that fragment bundles are not yet supported. This could save the ignorant user some time trying to find out why his fragment bundle doesn't work as expected. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
