[jira] [Commented] (FELIX-5906) Intstalling Manifest only bundles causes ArrayIndexOutOfBoundsException from Felix Security

2018-08-13 Thread Karl Pauls (JIRA) 


[ 
https://issues.apache.org/jira/browse/FELIX-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578958#comment-16578958
 ] 

Karl Pauls commented on FELIX-5906:
---

Good catch - I think I fixed it in r1837982. 

[~timothyjward], could you test it with the current trunk (2.7.0-SNAPSHOT) and 
see if it works for you now?

> Intstalling Manifest only bundles causes ArrayIndexOutOfBoundsException from 
> Felix Security
> ---
>
> Key: FELIX-5906
> URL: https://issues.apache.org/jira/browse/FELIX-5906
> Project: Felix
>  Issue Type: Bug
>  Components: Framework Security
>Affects Versions: framework.security-2.6.0
>Reporter: Timothy Ward
>Assignee: Karl Pauls
>Priority: Major
> Fix For: framework.security-2.8.0
>
>
> The Felix security Provider returns an empty array, rather than null when 
> [finding 
> certificates|[https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L274].]
>  This then causes an ArrayIndexOutOfBoundsException when [this 
> line|https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L475]
>  is reached



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (FELIX-5906) Installing Manifest only bundles causes ArrayIndexOutOfBoundsException from Felix Security

2018-08-13 Thread Karl Pauls (JIRA) 


 [ 
https://issues.apache.org/jira/browse/FELIX-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls updated FELIX-5906:
--
Summary: Installing Manifest only bundles causes 
ArrayIndexOutOfBoundsException from Felix Security  (was: Intstalling Manifest 
only bundles causes ArrayIndexOutOfBoundsException from Felix Security)

> Installing Manifest only bundles causes ArrayIndexOutOfBoundsException from 
> Felix Security
> --
>
> Key: FELIX-5906
> URL: https://issues.apache.org/jira/browse/FELIX-5906
> Project: Felix
>  Issue Type: Bug
>  Components: Framework Security
>Affects Versions: framework.security-2.6.0
>Reporter: Timothy Ward
>Assignee: Karl Pauls
>Priority: Major
> Fix For: framework.security-2.8.0
>
>
> The Felix security Provider returns an empty array, rather than null when 
> [finding 
> certificates|[https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L274].]
>  This then causes an ArrayIndexOutOfBoundsException when [this 
> line|https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L475]
>  is reached



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (FELIX-5906) Intstalling Manifest only bundles causes ArrayIndexOutOfBoundsException from Felix Security

2018-08-13 Thread Karl Pauls (JIRA) 


 [ 
https://issues.apache.org/jira/browse/FELIX-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls reassigned FELIX-5906:
-

Assignee: Karl Pauls

> Intstalling Manifest only bundles causes ArrayIndexOutOfBoundsException from 
> Felix Security
> ---
>
> Key: FELIX-5906
> URL: https://issues.apache.org/jira/browse/FELIX-5906
> Project: Felix
>  Issue Type: Bug
>  Components: Framework Security
>Affects Versions: framework.security-2.6.0
>Reporter: Timothy Ward
>Assignee: Karl Pauls
>Priority: Major
> Fix For: framework.security-2.8.0
>
>
> The Felix security Provider returns an empty array, rather than null when 
> [finding 
> certificates|[https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L274].]
>  This then causes an ArrayIndexOutOfBoundsException when [this 
> line|https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L475]
>  is reached



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (FELIX-5906) Intstalling Manifest only bundles causes ArrayIndexOutOfBoundsException from Felix Security

2018-08-13 Thread Karl Pauls (JIRA) 


 [ 
https://issues.apache.org/jira/browse/FELIX-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls updated FELIX-5906:
--
Fix Version/s: framework.security-2.8.0

> Intstalling Manifest only bundles causes ArrayIndexOutOfBoundsException from 
> Felix Security
> ---
>
> Key: FELIX-5906
> URL: https://issues.apache.org/jira/browse/FELIX-5906
> Project: Felix
>  Issue Type: Bug
>  Components: Framework Security
>Affects Versions: framework.security-2.6.0
>Reporter: Timothy Ward
>Priority: Major
> Fix For: framework.security-2.8.0
>
>
> The Felix security Provider returns an empty array, rather than null when 
> [finding 
> certificates|[https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L274].]
>  This then causes an ArrayIndexOutOfBoundsException when [this 
> line|https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L475]
>  is reached



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Does felix.Configurator provides a global extender property as felix.scr ?

2018-08-13 Thread Cristiano 

Hi Carsten.

Sorry to answer a bit late but I needed to check if my subsystems 
knowledge was still updated ;)


Your solution to install the bundle in every scoped subsystem would be 
good, if Subsystems impl allowed this.


But its not the case, the Subsystems doesn't allows to have more than 
one bundle using same name/version inside the container, even if it is 
being provided as a constituent of a scope subsystem.


In order to test I've created a composite subsystem and included as a 
constituent the bundle:"org.apache.felix.bundlerepository". This bundle 
is required in order aries subsystem to boot. When I tried to install 
this subsystem, I got this exception:


org.osgi.service.subsystem.SubsystemException: 
org.osgi.framework.BundleException: A bundle is already installed with 
the name "org.apache.felix.bundlerepository" and version "2.0.10" 


But I think that this theme about how specs that provides Extenders (as 
DS/SCR and Configurator specs) should implement in order to support 
scoped subsystems should be in the compendium...


best regards,

Cristiano


On 09/08/2018 04:28, Carsten Ziegeler wrote:

The configurator does not have such a setting, it uses it's own bundle
context to find other bundles. Therefore if you want to use it with
scoped subsystems, the best is to simply install it in every scoped
system. It will pick up the configuration admin using the bundle
containing the configuration

Regards

Carsten


Cristiano Gavião wrote

Hi all,

Felix SCR has a property named "ds.global.extender" that instructs SCR
to use the System Bundle's bundleContext instead its own bundleContext
in order to register its extender service.

It is useful to listening for bundles that are installed inside scoped
subsystems.

thanks,

Cristiano

[jira] [Updated] (FELIX-5906) Intstalling Manifest only bundles causes ArrayIndexOutOfBoundsException from Felix Security

2018-08-13 Thread Timothy Ward (JIRA) 


 [ 
https://issues.apache.org/jira/browse/FELIX-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Ward updated FELIX-5906:

Component/s: Framework Security

> Intstalling Manifest only bundles causes ArrayIndexOutOfBoundsException from 
> Felix Security
> ---
>
> Key: FELIX-5906
> URL: https://issues.apache.org/jira/browse/FELIX-5906
> Project: Felix
>  Issue Type: Bug
>  Components: Framework Security
>Affects Versions: framework.security-2.6.0
>Reporter: Timothy Ward
>Priority: Major
>
> The Felix security Provider returns an empty array, rather than null when 
> [finding 
> certificates|[https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L274].]
>  This then causes an ArrayIndexOutOfBoundsException when [this 
> line|https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L475]
>  is reached



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (FELIX-5906) Intstalling Manifest only bundles causes ArrayIndexOutOfBoundsException from Felix Security

2018-08-13 Thread Timothy Ward (JIRA) 


 [ 
https://issues.apache.org/jira/browse/FELIX-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Ward updated FELIX-5906:

Affects Version/s: framework.security-2.6.0

> Intstalling Manifest only bundles causes ArrayIndexOutOfBoundsException from 
> Felix Security
> ---
>
> Key: FELIX-5906
> URL: https://issues.apache.org/jira/browse/FELIX-5906
> Project: Felix
>  Issue Type: Bug
>  Components: Framework Security
>Affects Versions: framework.security-2.6.0
>Reporter: Timothy Ward
>Priority: Major
>
> The Felix security Provider returns an empty array, rather than null when 
> [finding 
> certificates|[https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L274].]
>  This then causes an ArrayIndexOutOfBoundsException when [this 
> line|https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L475]
>  is reached



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FELIX-5906) Intstalling Manifest only bundles causes ArrayIndexOutOfBoundsException from Felix Security

2018-08-13 Thread Timothy Ward (JIRA) 
Timothy Ward created FELIX-5906:
---

 Summary: Intstalling Manifest only bundles causes 
ArrayIndexOutOfBoundsException from Felix Security
 Key: FELIX-5906
 URL: https://issues.apache.org/jira/browse/FELIX-5906
 Project: Felix
  Issue Type: Bug
Reporter: Timothy Ward


The Felix security Provider returns an empty array, rather than null when 
[finding 
certificates|[https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L274].]
 This then causes an ArrayIndexOutOfBoundsException when [this 
line|https://github.com/apache/felix/blob/trunk/framework.security/src/main/java/org/apache/felix/framework/security/verifier/BundleDNParser.java#L475]
 is reached



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (FELIX-5905) SCR cannot access method getLogger from LogService R7

2018-08-13 Thread JIRA 


[ 
https://issues.apache.org/jira/browse/FELIX-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578525#comment-16578525
 ] 

Raymond Augé commented on FELIX-5905:
-

super weird, is there a way to get a basic example project that reproduces the 
issue?

> SCR cannot access method getLogger from LogService R7
> -
>
> Key: FELIX-5905
> URL: https://issues.apache.org/jira/browse/FELIX-5905
> Project: Felix
>  Issue Type: Bug
>  Components: Declarative Services (SCR)
>Affects Versions: scr-2.1.2
>Reporter: Alexandre Roman
>Priority: Blocker
>
> I'm using SCR 2.1.5-SNAPSHOT with Felix LogService R7 and Felix Log-Extension.
> The LogService bundle is installed in the boot classpath (with Felix Logback 
> & SLF4J APIs), and I'm using Log-Extension to expose LogService services to 
> the OSGi environment.
> When using SCR, the method ValueUtils#getLogger cannot get access to the 
> method LogService#getLogger using reflection for unknown reason: 
> IllegalAccessException.
> The LogService implementation used as argument (coming from Felix LogService) 
> owns the right method, but the reflection code failed with this exception.
> I tried a "workaround", using "setAccessible(true)" to the method handle, 
> before invoking the method on the LogService implementation: now it works as 
> expected.
> I'm not sure if it's related to my setup, meanwhile I need this call to 
> "setAccessible" in order to get the expected behaviour. Without it, SCR 
> failed to get a logger instance, and my components fail with a NPE.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (FELIX-5905) SCR cannot access method getLogger from LogService R7

2018-08-13 Thread Carsten Ziegeler (JIRA) 


[ 
https://issues.apache.org/jira/browse/FELIX-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578509#comment-16578509
 ] 

Carsten Ziegeler commented on FELIX-5905:
-

The getLogger method is public, so I fail to see why setAccessible(true) is 
required here
[~rotty3000] Do you have any idea?

> SCR cannot access method getLogger from LogService R7
> -
>
> Key: FELIX-5905
> URL: https://issues.apache.org/jira/browse/FELIX-5905
> Project: Felix
>  Issue Type: Bug
>  Components: Declarative Services (SCR)
>Affects Versions: scr-2.1.2
>Reporter: Alexandre Roman
>Priority: Blocker
>
> I'm using SCR 2.1.5-SNAPSHOT with Felix LogService R7 and Felix Log-Extension.
> The LogService bundle is installed in the boot classpath (with Felix Logback 
> & SLF4J APIs), and I'm using Log-Extension to expose LogService services to 
> the OSGi environment.
> When using SCR, the method ValueUtils#getLogger cannot get access to the 
> method LogService#getLogger using reflection for unknown reason: 
> IllegalAccessException.
> The LogService implementation used as argument (coming from Felix LogService) 
> owns the right method, but the reflection code failed with this exception.
> I tried a "workaround", using "setAccessible(true)" to the method handle, 
> before invoking the method on the LogService implementation: now it works as 
> expected.
> I'm not sure if it's related to my setup, meanwhile I need this call to 
> "setAccessible" in order to get the expected behaviour. Without it, SCR 
> failed to get a logger instance, and my components fail with a NPE.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE CANCEL] Release Apache Felix SCR 2.1.4

2018-08-13 Thread Carsten Ziegeler 
As noted in FELIX-5904 SRC was passing in "null" into LoggerFactory
which causes the LoggerFactory to throw an NPE.

I've changed this now to use ROOT instead of null


Regards

Carsten


Raymond Auge wrote
> On Mon, Aug 13, 2018 at 1:11 AM, Carsten Ziegeler 
> wrote:
> 
>> I hereby cancel the vote due to FELIX-5904.
>>
>> (This release was supposed to fix the R7 logging problems, but
>> apparently it doesn't,
> 
> 
> Carsten can you elaborate on this?
> 
> - Ray
> 
> 
>> there are no other changes compared to 2.1.2)
>>
>> Regards
>> Carsten
>>
>> Carsten Ziegeler wrote
>>> We solved one issue in this release:
>>>
>>> https://issues.apache.org/jira/browse/FELIX-5902
>>>
>>> Staging repositories:
>>> https://repository.apache.org/content/repositories/orgapachefelix-1244/
>>>
>>> You can use this UNIX script to download the release and verify the
>>> signatures:
>>> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>>>
>>> Usage:
>>> sh check_staged_release.sh 1244 /tmp/felix-staging
>>>
>>> Please vote to approve this release:
>>>
>>> [ ] +1 Approve the release
>>> [ ] -1 Veto the release (please provide specific comments)
>>>
>>> Regards
>>> Carsten
>>>
>> --
>> Carsten Ziegeler
>> Adobe Research Switzerland
>> cziege...@apache.org
>>
> 
> 
> 
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [VOTE CANCEL] Release Apache Felix SCR 2.1.4

2018-08-13 Thread Raymond Auge 
On Mon, Aug 13, 2018 at 1:11 AM, Carsten Ziegeler 
wrote:

> I hereby cancel the vote due to FELIX-5904.
>
> (This release was supposed to fix the R7 logging problems, but
> apparently it doesn't,


Carsten can you elaborate on this?

- Ray


> there are no other changes compared to 2.1.2)
>
> Regards
> Carsten
>
> Carsten Ziegeler wrote
> > We solved one issue in this release:
> >
> > https://issues.apache.org/jira/browse/FELIX-5902
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1244/
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1244 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> >
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>



-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

[jira] [Resolved] (FELIX-5904) SCR is creating a logger instance using name "null"

2018-08-13 Thread Carsten Ziegeler (JIRA) 


 [ 
https://issues.apache.org/jira/browse/FELIX-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved FELIX-5904.
-
Resolution: Fixed

Thanks

> SCR is creating a logger instance using name "null"
> ---
>
> Key: FELIX-5904
> URL: https://issues.apache.org/jira/browse/FELIX-5904
> Project: Felix
>  Issue Type: Bug
>  Components: Declarative Services (SCR)
>Affects Versions: scr-2.1.6
>Reporter: Alexandre Roman
>Assignee: Carsten Ziegeler
>Priority: Blocker
> Fix For: scr-2.1.6
>
>
> When using LogService 1.2 from OSGi r7 together with SCR 2.1.4, the following 
> error happens:
> {{org.osgi.framework.BundleException: Activator start error in bundle 
> org.apache.felix.scr [8].}}
> {{ at org.apache.felix.framework.Felix.activateBundle(Felix.java:2448)}}
> {{ at org.apache.felix.framework.Felix.startBundle(Felix.java:2304)}}
> {{ at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1535)}}
> {{ at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)}}
> {{ at java.lang.Thread.run(Thread.java:748)}}
> {{Caused by: java.lang.NullPointerException}}
> {{ at 
> org.apache.felix.log.RootLoggerContextImpl.getEffectiveLogLevel(RootLoggerContextImpl.java:53)}}
> {{ at 
> org.apache.felix.log.LoggerContextImpl.getEffectiveLogLevel(LoggerContextImpl.java:70)}}
> {{ at org.apache.felix.log.LoggerImpl.isErrorEnabled(LoggerImpl.java:216)}}
> {{ at 
> org.apache.felix.scr.impl.logger.R7LogServiceLogger.isLogEnabled(R7LogServiceLogger.java:48)}}
> {{ at 
> org.apache.felix.scr.impl.logger.AbstractLogger.isLogEnabled(AbstractLogger.java:72)}}
> {{ at 
> org.apache.felix.scr.impl.logger.AbstractLogger.log(AbstractLogger.java:110)}}
> {{ at org.apache.felix.scr.impl.Activator.restart(Activator.java:143)}}
> {{ at 
> org.apache.felix.scr.impl.config.ScrConfigurationImpl.configure(ScrConfigurationImpl.java:213)}}
> {{ at 
> org.apache.felix.scr.impl.config.ScrConfigurationImpl.start(ScrConfigurationImpl.java:118)}}
> {{ at org.apache.felix.scr.impl.Activator.start(Activator.java:100)}}
> {{ at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)}}
> {{ at org.apache.felix.framework.Felix.activateBundle(Felix.java:2398)}}
> {{ ... 4 more}}
> It looks like SCR is trying to create a Logger instance through LoggerFactory 
> with name=null.
> Specs from OSGi r7 do not clearly specify what happens when the logger name 
> is null.
> The LogService implementation from Felix does not check whether the value is 
> null or not. I think this behaviour is normal: one should not expect a method 
> to work normally if nothing in the documentation say anything about 
> nullability.
> The Logger instance is created from R7LogServiceLogger, which is created by 
> LogServiceSupport#getLogger. This instance is internally used by the bundle.
> I think a default logger name should be set for this internal logger.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FELIX-5905) SCR cannot access method getLogger from LogService R7

2018-08-13 Thread Alexandre Roman (JIRA) 
Alexandre Roman created FELIX-5905:
--

 Summary: SCR cannot access method getLogger from LogService R7
 Key: FELIX-5905
 URL: https://issues.apache.org/jira/browse/FELIX-5905
 Project: Felix
  Issue Type: Bug
  Components: Declarative Services (SCR)
Affects Versions: scr-2.1.2
Reporter: Alexandre Roman


I'm using SCR 2.1.5-SNAPSHOT with Felix LogService R7 and Felix Log-Extension.

The LogService bundle is installed in the boot classpath (with Felix Logback & 
SLF4J APIs), and I'm using Log-Extension to expose LogService services to the 
OSGi environment.

When using SCR, the method ValueUtils#getLogger cannot get access to the method 
LogService#getLogger using reflection for unknown reason: 
IllegalAccessException.

The LogService implementation used as argument (coming from Felix LogService) 
owns the right method, but the reflection code failed with this exception.

I tried a "workaround", using "setAccessible(true)" to the method handle, 
before invoking the method on the LogService implementation: now it works as 
expected.

I'm not sure if it's related to my setup, meanwhile I need this call to 
"setAccessible" in order to get the expected behaviour. Without it, SCR failed 
to get a logger instance, and my components fail with a NPE.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (FELIX-5904) SCR is creating a logger instance using name "null"

2018-08-13 Thread Alexandre Roman (JIRA) 


[ 
https://issues.apache.org/jira/browse/FELIX-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16577953#comment-16577953
 ] 

Alexandre Roman commented on FELIX-5904:


Looks good to me!

> SCR is creating a logger instance using name "null"
> ---
>
> Key: FELIX-5904
> URL: https://issues.apache.org/jira/browse/FELIX-5904
> Project: Felix
>  Issue Type: Bug
>  Components: Declarative Services (SCR)
>Affects Versions: scr-2.1.6
>Reporter: Alexandre Roman
>Assignee: Carsten Ziegeler
>Priority: Blocker
> Fix For: scr-2.1.6
>
>
> When using LogService 1.2 from OSGi r7 together with SCR 2.1.4, the following 
> error happens:
> {{org.osgi.framework.BundleException: Activator start error in bundle 
> org.apache.felix.scr [8].}}
> {{ at org.apache.felix.framework.Felix.activateBundle(Felix.java:2448)}}
> {{ at org.apache.felix.framework.Felix.startBundle(Felix.java:2304)}}
> {{ at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1535)}}
> {{ at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)}}
> {{ at java.lang.Thread.run(Thread.java:748)}}
> {{Caused by: java.lang.NullPointerException}}
> {{ at 
> org.apache.felix.log.RootLoggerContextImpl.getEffectiveLogLevel(RootLoggerContextImpl.java:53)}}
> {{ at 
> org.apache.felix.log.LoggerContextImpl.getEffectiveLogLevel(LoggerContextImpl.java:70)}}
> {{ at org.apache.felix.log.LoggerImpl.isErrorEnabled(LoggerImpl.java:216)}}
> {{ at 
> org.apache.felix.scr.impl.logger.R7LogServiceLogger.isLogEnabled(R7LogServiceLogger.java:48)}}
> {{ at 
> org.apache.felix.scr.impl.logger.AbstractLogger.isLogEnabled(AbstractLogger.java:72)}}
> {{ at 
> org.apache.felix.scr.impl.logger.AbstractLogger.log(AbstractLogger.java:110)}}
> {{ at org.apache.felix.scr.impl.Activator.restart(Activator.java:143)}}
> {{ at 
> org.apache.felix.scr.impl.config.ScrConfigurationImpl.configure(ScrConfigurationImpl.java:213)}}
> {{ at 
> org.apache.felix.scr.impl.config.ScrConfigurationImpl.start(ScrConfigurationImpl.java:118)}}
> {{ at org.apache.felix.scr.impl.Activator.start(Activator.java:100)}}
> {{ at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)}}
> {{ at org.apache.felix.framework.Felix.activateBundle(Felix.java:2398)}}
> {{ ... 4 more}}
> It looks like SCR is trying to create a Logger instance through LoggerFactory 
> with name=null.
> Specs from OSGi r7 do not clearly specify what happens when the logger name 
> is null.
> The LogService implementation from Felix does not check whether the value is 
> null or not. I think this behaviour is normal: one should not expect a method 
> to work normally if nothing in the documentation say anything about 
> nullability.
> The Logger instance is created from R7LogServiceLogger, which is created by 
> LogServiceSupport#getLogger. This instance is internally used by the bundle.
> I think a default logger name should be set for this internal logger.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)