[jira] Resolved: (FELIX-2417) NPE in Filter
[ https://issues.apache.org/jira/browse/FELIX-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zdila resolved FELIX-2417. - Fix Version/s: framework-3.0.1 Resolution: Fixed Thanks for fixing. > NPE in Filter > -- > > Key: FELIX-2417 > URL: https://issues.apache.org/jira/browse/FELIX-2417 > Project: Felix > Issue Type: Bug >Affects Versions: framework-3.0.0 > Environment: java version "1.6.0_20" > Java(TM) SE Runtime Environment (build 1.6.0_20-b02) > Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing) >Reporter: Martin Zdila > Fix For: framework-3.0.1 > > > After upgrading framework from 2.0.5 to 3.0.0 I am getting many NPE > exceptions "Cannot register Component". > I can't identify the core of the problem, but from what I see: in the > org.apache.felix.framework.FilterImpl on line 145 the name = > "service.factoryPid" but m_map doesn't contain such entry and so the key is > set to null. The next call on the line 147 fails because key cannot be null > in Hashtable.get(key). > ERROR: my-cool-bundle (110): [my.cool.ServiceImpl] Cannot register Component > java.lang.NullPointerException > at java.util.Hashtable.get(Hashtable.java:334) > at > org.apache.felix.framework.FilterImpl$DictionaryCapability.getAttribute(FilterImpl.java:147) > at > org.apache.felix.framework.capabilityset.CapabilitySet.matchesInternal(CapabilitySet.java:269) > at > org.apache.felix.framework.capabilityset.CapabilitySet.matches(CapabilitySet.java:226) > at org.apache.felix.framework.FilterImpl.match(FilterImpl.java:59) > at > org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:538) > at > org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:124) > at > org.apache.felix.scr.impl.config.ConfigurationComponentRegistry.findConfigurations(ConfigurationComponentRegistry.java:267) > at > org.apache.felix.scr.impl.config.ConfigurationComponentRegistry.findFactoryConfigurations(ConfigurationComponentRegistry.java:259) > at > org.apache.felix.scr.impl.config.ConfigurationComponentRegistry.createComponentHolder(ConfigurationComponentRegistry.java:107) > at > org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:244) > at > org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:147) > at > org.apache.felix.scr.impl.BundleComponentActivator.(BundleComponentActivator.java:111) > at > org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:255) > at org.apache.felix.scr.impl.Activator.bundleChanged(Activator.java:173) > at > org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:800) > at > org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:728) > at > org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:610) > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3734) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1807) > at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1188) > at > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2446) [Gogo] The bundle context command is not registered with a scope in gosh_profile
[
https://issues.apache.org/jira/browse/FELIX-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882337#action_12882337
]
Derek Baum commented on FELIX-2446:
---
the whole gosh_profile is now enclosed in a try {} block, so it doesn't abort
startup if an error occurs:
$ java -jar bin/felix.jar
bundle://4.0:1/gosh_profile: ERROR: java.io.IOException: Resource does not
exist: bundle://4.0:1/motdx
> [Gogo] The bundle context command is not registered with a scope in
> gosh_profile
>
>
> Key: FELIX-2446
> URL: https://issues.apache.org/jira/browse/FELIX-2446
> Project: Felix
> Issue Type: Bug
> Components: Gogo Shell
>Affects Versions: gogo-0.6.0
>Reporter: Richard S. Hall
>Assignee: Derek Baum
> Fix For: gogo-0.8.0
>
>
> The default gosh_profile shell registers the bundle context as a command, but
> it is not assigned any scope. This apparently is problematic for anyone else
> registering a command with overlapping names as what is on bundle context.
> For example, registering a command named "bundle" causes the following
> gosh_profile line to fail:
> addcommand system ((bundle 1) loadclass java.lang.System)
> I am not sure why or how it is shadowing it, since it seems like the order
> should favor the built-in commands, but apparently. Regardless, if we had a
> scope assigned to this we could be precise in our gosh_profile shell (e.g.,
> gogo:bundle) to avoid this issue altogether.
> To make matters worse, this causes the entire shell bundle to die...it might
> be nice if it continued to function even if there are errors in the
> gosh_profile.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2445) [Gogo] Default gosh_profile should be updated to use system bundle to load java.lang.System
[ https://issues.apache.org/jira/browse/FELIX-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Baum resolved FELIX-2445. --- Resolution: Fixed now load java.lang.System using bundle 0 > [Gogo] Default gosh_profile should be updated to use system bundle to load > java.lang.System > --- > > Key: FELIX-2445 > URL: https://issues.apache.org/jira/browse/FELIX-2445 > Project: Felix > Issue Type: Improvement > Components: Gogo Shell >Affects Versions: gogo-0.6.0 >Reporter: Richard S. Hall > Fix For: gogo-0.8.0 > > > The default gosh_profile file uses bundle 1 to load class because there was > an issue with using bundle 0 (FELIX-2335), but that issue has reportedly been > fixed, so in theory it should work now. Using bundle 1 is a bad idea, since > there is no guarantee that such a bundle will exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2446) [Gogo] The bundle context command is not registered with a scope in gosh_profile
[
https://issues.apache.org/jira/browse/FELIX-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Derek Baum resolved FELIX-2446.
---
Resolution: Fixed
The context commands are registered into a scope - the first argument of
addcommand is the scope:
addcommand context ${.context}
I have however fixed gosh_profile to explicitly use this scope when referencing
the bundle command:
# add methods on System object as commands
addcommand system ((context:bundle 0) loadclass java.lang.System
since the bundle context is also set as a session variable, we could have
written the above as:
addcommand system (${.context} bundle 0) loadclass java.lang.System
We could protect errors in the whole gosh_profile from aborting startup by
enclosing them in a try block, as is used for displaying the message of the day
- rather than test whether the file exists, we just eclose it in a try block:
# print welcome message
try {
cat ($0 resolve motd)
}
> [Gogo] The bundle context command is not registered with a scope in
> gosh_profile
>
>
> Key: FELIX-2446
> URL: https://issues.apache.org/jira/browse/FELIX-2446
> Project: Felix
> Issue Type: Bug
> Components: Gogo Shell
>Affects Versions: gogo-0.6.0
>Reporter: Richard S. Hall
>Assignee: Derek Baum
> Fix For: gogo-0.8.0
>
>
> The default gosh_profile shell registers the bundle context as a command, but
> it is not assigned any scope. This apparently is problematic for anyone else
> registering a command with overlapping names as what is on bundle context.
> For example, registering a command named "bundle" causes the following
> gosh_profile line to fail:
> addcommand system ((bundle 1) loadclass java.lang.System)
> I am not sure why or how it is shadowing it, since it seems like the order
> should favor the built-in commands, but apparently. Regardless, if we had a
> scope assigned to this we could be precise in our gosh_profile shell (e.g.,
> gogo:bundle) to avoid this issue altogether.
> To make matters worse, this causes the entire shell bundle to die...it might
> be nice if it continued to function even if there are errors in the
> gosh_profile.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-2446) [Gogo] The bundle context command is not registered with a scope in gosh_profile
[ https://issues.apache.org/jira/browse/FELIX-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Baum reassigned FELIX-2446: - Assignee: Derek Baum > [Gogo] The bundle context command is not registered with a scope in > gosh_profile > > > Key: FELIX-2446 > URL: https://issues.apache.org/jira/browse/FELIX-2446 > Project: Felix > Issue Type: Bug > Components: Gogo Shell >Affects Versions: gogo-0.6.0 >Reporter: Richard S. Hall >Assignee: Derek Baum > Fix For: gogo-0.8.0 > > > The default gosh_profile shell registers the bundle context as a command, but > it is not assigned any scope. This apparently is problematic for anyone else > registering a command with overlapping names as what is on bundle context. > For example, registering a command named "bundle" causes the following > gosh_profile line to fail: > addcommand system ((bundle 1) loadclass java.lang.System) > I am not sure why or how it is shadowing it, since it seems like the order > should favor the built-in commands, but apparently. Regardless, if we had a > scope assigned to this we could be precise in our gosh_profile shell (e.g., > gogo:bundle) to avoid this issue altogether. > To make matters worse, this causes the entire shell bundle to die...it might > be nice if it continued to function even if there are errors in the > gosh_profile. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2446) [Gogo] The bundle context command is not registered with a scope in gosh_profile
[Gogo] The bundle context command is not registered with a scope in gosh_profile Key: FELIX-2446 URL: https://issues.apache.org/jira/browse/FELIX-2446 Project: Felix Issue Type: Bug Components: Gogo Shell Affects Versions: gogo-0.6.0 Reporter: Richard S. Hall Fix For: gogo-0.8.0 The default gosh_profile shell registers the bundle context as a command, but it is not assigned any scope. This apparently is problematic for anyone else registering a command with overlapping names as what is on bundle context. For example, registering a command named "bundle" causes the following gosh_profile line to fail: addcommand system ((bundle 1) loadclass java.lang.System) I am not sure why or how it is shadowing it, since it seems like the order should favor the built-in commands, but apparently. Regardless, if we had a scope assigned to this we could be precise in our gosh_profile shell (e.g., gogo:bundle) to avoid this issue altogether. To make matters worse, this causes the entire shell bundle to die...it might be nice if it continued to function even if there are errors in the gosh_profile. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2445) [Gogo] Default gosh_profile should be updated to use system bundle to load java.lang.System
[Gogo] Default gosh_profile should be updated to use system bundle to load java.lang.System --- Key: FELIX-2445 URL: https://issues.apache.org/jira/browse/FELIX-2445 Project: Felix Issue Type: Improvement Components: Gogo Shell Affects Versions: gogo-0.6.0 Reporter: Richard S. Hall Fix For: gogo-0.8.0 The default gosh_profile file uses bundle 1 to load class because there was an issue with using bundle 0 (FELIX-2335), but that issue has reportedly been fixed, so in theory it should work now. Using bundle 1 is a bad idea, since there is no guarantee that such a bundle will exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1657) Add option in fileinstall to start bundles transiently (START_TRANSIENT)
[ https://issues.apache.org/jira/browse/FELIX-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahoo updated FELIX-1657: - Attachment: FELIX-1567.patch.txt A patch to address this issue. > Add option in fileinstall to start bundles transiently (START_TRANSIENT) > > > Key: FELIX-1657 > URL: https://issues.apache.org/jira/browse/FELIX-1657 > Project: Felix > Issue Type: Improvement > Components: File Install >Reporter: Sahoo > Attachments: FELIX-1567.patch.txt > > > Currently fileinstall starts bundle persistently. Does it make sense to have > the option of starting bundles transiently? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2442) [Karaf] JDK 1.5 build issue - StandardEmitterMBean is JDK 1.6 specific
[ https://issues.apache.org/jira/browse/FELIX-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved FELIX-2442. Fix Version/s: karaf 1.8.0 Resolution: Fixed Committing to https://svn.apache.org/repos/asf/felix/trunk ... M karaf/features/management/src/main/java/org/apache/felix/karaf/features/management/internal/FeaturesServiceMBeanImpl.java A karaf/features/management/src/main/java/org/apache/felix/karaf/features/management/internal/StandardEmitterMBean.java Committed r957468 > [Karaf] JDK 1.5 build issue - StandardEmitterMBean is JDK 1.6 specific > -- > > Key: FELIX-2442 > URL: https://issues.apache.org/jira/browse/FELIX-2442 > Project: Felix > Issue Type: Bug > Environment: Java 1.5 >Reporter: Jamie goodyear >Assignee: Guillaume Nodet > Fix For: karaf 1.8.0 > > > "StandardEmitterMBean" appears to only be available as of Java 1.6 > http://java.sun.com/javase/6/docs/api/javax/management/StandardEmitterMBean.html. > Karaf's FeaturesServiceMBeanImpl extends StandardEmitterMBean, as such this > is a problem for building with JDK 1.5. > We may need to revert the change that introduced this to Karaf or implement > some other work around. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-2442) [Karaf] JDK 1.5 build issue - StandardEmitterMBean is JDK 1.6 specific
[ https://issues.apache.org/jira/browse/FELIX-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned FELIX-2442: -- Assignee: Guillaume Nodet > [Karaf] JDK 1.5 build issue - StandardEmitterMBean is JDK 1.6 specific > -- > > Key: FELIX-2442 > URL: https://issues.apache.org/jira/browse/FELIX-2442 > Project: Felix > Issue Type: Bug > Environment: Java 1.5 >Reporter: Jamie goodyear >Assignee: Guillaume Nodet > > "StandardEmitterMBean" appears to only be available as of Java 1.6 > http://java.sun.com/javase/6/docs/api/javax/management/StandardEmitterMBean.html. > Karaf's FeaturesServiceMBeanImpl extends StandardEmitterMBean, as such this > is a problem for building with JDK 1.5. > We may need to revert the change that introduced this to Karaf or implement > some other work around. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2444) Problems with logging bundle informations when a bundle is reinstalled or installed in multiple versions
Problems with logging bundle informations when a bundle is reinstalled or installed in multiple versions Key: FELIX-2444 URL: https://issues.apache.org/jira/browse/FELIX-2444 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.6.2 Reporter: Guillaume Nodet Fix For: karaf 1.8.0 See http://issues.ops4j.org/browse/PAXLOGGING-86 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2443) MDC information on logging events can't be displayed in the console
[ https://issues.apache.org/jira/browse/FELIX-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved FELIX-2443. Resolution: Fixed Committing to https://svn.apache.org/repos/asf/felix/trunk ... M karaf/assembly/src/main/distribution/text/etc/org.apache.felix.karaf.log.cfg M karaf/shell/log/src/main/java/org/apache/felix/karaf/shell/log/VmLogAppender.java M karaf/shell/log/src/main/java/org/apache/felix/karaf/shell/log/layout/PatternParser.java Committed r957440 > MDC information on logging events can't be displayed in the console > --- > > Key: FELIX-2443 > URL: https://issues.apache.org/jira/browse/FELIX-2443 > Project: Felix > Issue Type: Bug > Components: Karaf >Affects Versions: karaf-1.6.2 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: karaf 1.8.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2443) MDC information on logging events can't be displayed in the console
MDC information on logging events can't be displayed in the console --- Key: FELIX-2443 URL: https://issues.apache.org/jira/browse/FELIX-2443 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.6.2 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: karaf 1.8.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
