felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <cziege...@apache.org>
Subject Re: [VOTE] Release Apache Felix Web Console Memory Usage Plugin 1.0.6
Date Fri, 24 Apr 2015 11:34:56 GMT
Hi Valentin,

I guess this problem already existed in the 1.0.4 version. In that case
I think there is no need to stop this vote. The problem is that version
1.0.4 does not work with the web console 4.2.8.

So I think we should continue with the vote, fix the problem you mention
and then do another release once that's done

Regards
Carsten

Am 24.04.15 um 09:23 schrieb Valentin Valchev:
> Hi Carsten,
> Our test team discovered, that there is a slight problem, with this
> release, when the framework is run in security mode. The bundle
> implements ManagedServer but in it's updated method it performs
> operation that requires special permission. Because the memoryusage
> bundles doesn't use doPrivileged, the configuration admin bundle is also
> in the stack trace. In that case, if the CM bundle doesn't have the
> required permission, security exception will be thrown:
> 
> fw>$#0   DEBUG   > [SecuritySimple] Insufficient local permissions:
> bundle: com.prosyst.mbs.osgi.cm.bundle; permission:
> ("java.lang.management.ManagementPermission" "control"); local perms:
> Bundle: ../../../bundles/com.prosyst.mbs.osgi.cm.bundle.jar
>         at
> com.prosyst.mbs.impl.framework.module.security.PPermissions.implies(PPermissions.java:288)
>         at java.security.ProtectionDomain.implies(ProtectionDomain.java:276)
>         at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:350)
>         at
> com.prosyst.mbs.impl.framework.module.security.SecurityManagerImpl.checkPermission(SecurityManagerImpl.java:110)
>         at
> com.prosyst.mbs.impl.framework.module.security.SecurityManagerImpl.checkPermission(SecurityManagerImpl.java:71)
>         at
> com.prosyst.mbs.impl.framework.PSecurityManager.checkPermission(PSecurityManager.java:243)
>         at sun.management.Util.checkAccess(Util.java:77)
>         at sun.management.Util.checkControlAccess(Util.java:85)
>         at
> sun.management.MemoryPoolImpl.setUsageThreshold(MemoryPoolImpl.java:118)
>         at
> org.apache.felix.webconsole.plugins.memoryusage.internal.MemoryUsageSupport.setThreshold(MemoryUsageSupport.java:244)
>         at
> org.apache.felix.webconsole.plugins.memoryusage.internal.MemoryUsageConfigurator.updated(MemoryUsageConfigurator.java:85)
> 
> Regards,
> Valentin
> 
> On 24/04/2015 09:22, Carsten Ziegeler wrote:
>> Hi,
>>
>> We solved 1 issue in this release:
>> https://issues.apache.org/jira/browse/FELIX-4862
>>
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachefelix-1066/
>>
>> 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 1066 /tmp/felix-staging
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Veto the release (please provide specific comments)
>>
>> This vote will be open for at least 72 hours.
>>
>> Regards
>> Carsten
> 
> 


-- 
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org

Mime
View raw message