You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Andras Szerdahelyi <an...@gmail.com> on 2014/09/26 09:59:37 UTC

karaf-jaas-modules registering o.a.f.fileinstall.ArtifactInstaller services

hello list,

i'm seeing something very weird with the out-of-the-box ( + feature:install
webconsole ) karaf 3.0.1 tar distribution.

A single page load to the web console triggers Apache Karaf :: JAAS ::
Modules to register a number
[org.apache.felix.fileinstall.ArtifactInstaller] services. Every single
page load ( ! ) :-)

this is the situation at boot

karaf@root()> bundle:services 38 | grep -i ArtifactInstaller | wc -l

1

-- pageload to system/console/configMgr ---

karaf@root()> bundle:services 38 | grep -i ArtifactInstaller | wc -l

 20

-- load system/console/services/ ---

karaf@root()> bundle:services 38 | grep -i ArtifactInstaller | wc -l

 34

-- pageload to system/console/configMgr ---

karaf@root()> bundle:services 38 | grep -i ArtifactInstaller | wc -l

 49


as you can see the number of registered ArtifactInstallers isn't exactly
consistent either.

What is happening..? Could someone point me to the code in jaas-modules
where this is happening? The only reference i could find so far was in a
unit test and it mentions a leak :-)

https://github.com/apache/karaf/blob/143644ad6f8ec74cb75e7849652ae0eecd11eba2/itests/src/test/java/org/apache/karaf/itests/JaasTest.java
@Test // shows the leak afaics public void testLoginSingleReg() throws
Exception { for (int i=0; i<10; i++) { doLogin(); } assertEquals(2,
bundleContext.getServiceReferences(ArtifactInstaller.class.getName(), null).
length); }