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

Jean-Baptiste Onofré updated KARAF-6716:
----------------------------------------
    Description: 
So I noticed a difference in deploying the exact same kar in the new karaf
 4.3.0.RC1 version and the older ones. When I try to install a kar with the
 feature (simplified) found below with the mariadb JDBC driver it throws a
 nullpointer exception with stacktrace found down below.

But what I find odd is that this kar installs without problems on earlier
 Karaf versions. What is furthermore odd is that only putting the mariadb
 bundle in deploy works perfectly fine in both versions.

Anyone any idea what is causing this odd behaviour and if it's a bug of the
 karaf 4.3.0.RC1 version?

Feature:
{code:java}
    <feature name="mariadb" version="${project.version}">
        
 
<bundle>mvn:org.mariadb.jdbc/mariadb-java-client/${mariadb.client.version}</bundle>
     </feature>{code}
Stacktrace:
{code:java}
java.lang.NullPointerException: null
         at
 
org.apache.karaf.features.internal.region.SubsystemResolveContext.getRegion(SubsystemResolveContext.java:270)
 ~[?:?]
         at
 
org.apache.karaf.features.internal.region.SubsystemResolveContext.access$000(SubsystemResolveContext.java:67)
 ~[?:?]
         at
 
org.apache.karaf.features.internal.region.SubsystemResolveContext$Visitor.contains(SubsystemResolveContext.java:302)
 ~[?:?]
         at
 
org.apache.karaf.features.internal.region.SubsystemResolveContext$Visitor.contains(SubsystemResolveContext.java:294)
 ~[?:?]
         at
 
org.apache.karaf.features.internal.region.AbstractRegionDigraphVisitor.visit(AbstractRegionDigraphVisitor.java:56)
 ~[?:?]
         at
 
org.eclipse.equinox.internal.region.SubgraphTraverser.visitRemainingSubgraph(SubgraphTraverser.java:37)
 ~[?:?]
         at
 
org.eclipse.equinox.internal.region.SubgraphTraverser.visitSubgraph(SubgraphTraverser.java:32)
 ~[?:?]
         at
 
org.eclipse.equinox.internal.region.StandardRegionDigraph.visitSubgraph(StandardRegionDigraph.java:374)
 ~[?:?]
         at
 
org.eclipse.equinox.internal.region.BundleIdBasedRegion.visitSubgraph(BundleIdBasedRegion.java:264)
 ~[?:?]
         at
 
org.apache.karaf.features.internal.region.SubsystemResolveContext.findProviders(SubsystemResolveContext.java:208)
 ~[?:?]
         at
 
org.apache.karaf.features.internal.region.SubsystemResolveContext.computeEdges(SubsystemResolveContext.java:138)
 ~[?:?]
         at
 
org.apache.karaf.features.internal.region.SubsystemResolveContext.computeDistances(SubsystemResolveContext.java:118)
 ~[?:?]
         at
 
org.apache.karaf.features.internal.region.SubsystemResolveContext.<init>(SubsystemResolveContext.java:96)
 ~[?:?]
         at
 
org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:231)
 ~[?:?]
         at
 org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:391)
 ~[?:?]
         at
 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
 ~[?:?]
         at
 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
 ~[?:?]
         at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
~[?:1.8.0_212]
         at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 ~[?:1.8.0_212]
         at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 ~[?:1.8.0_212]
         at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_212]{code}

  was:
So I noticed a difference in deploying the exact same kar in the new karaf
4.3.0.RC1 version and the older ones. When I try to install a kar with the
feature (simplified) found below with the mariadb JDBC driver it throws a
nullpointer exception with stacktrace found down below.

But what I find odd is that this kar installs without problems on earlier
Karaf versions. What is furthermore odd is that only putting the mariadb
bundle in deploy works perfectly fine in both versions.

Anyone any idea what is causing this odd behaviour and if it's a bug of the
karaf 4.3.0.RC1 version?

Feature:

    <feature name="mariadb" version="${project.version}">
       
<bundle>mvn:org.mariadb.jdbc/mariadb-java-client/${mariadb.client.version}</bundle>
    </feature>

Stacktrace:

java.lang.NullPointerException: null
        at
org.apache.karaf.features.internal.region.SubsystemResolveContext.getRegion(SubsystemResolveContext.java:270)
~[?:?]
        at
org.apache.karaf.features.internal.region.SubsystemResolveContext.access$000(SubsystemResolveContext.java:67)
~[?:?]
        at
org.apache.karaf.features.internal.region.SubsystemResolveContext$Visitor.contains(SubsystemResolveContext.java:302)
~[?:?]
        at
org.apache.karaf.features.internal.region.SubsystemResolveContext$Visitor.contains(SubsystemResolveContext.java:294)
~[?:?]
        at
org.apache.karaf.features.internal.region.AbstractRegionDigraphVisitor.visit(AbstractRegionDigraphVisitor.java:56)
~[?:?]
        at
org.eclipse.equinox.internal.region.SubgraphTraverser.visitRemainingSubgraph(SubgraphTraverser.java:37)
~[?:?]
        at
org.eclipse.equinox.internal.region.SubgraphTraverser.visitSubgraph(SubgraphTraverser.java:32)
~[?:?]
        at
org.eclipse.equinox.internal.region.StandardRegionDigraph.visitSubgraph(StandardRegionDigraph.java:374)
~[?:?]
        at
org.eclipse.equinox.internal.region.BundleIdBasedRegion.visitSubgraph(BundleIdBasedRegion.java:264)
~[?:?]
        at
org.apache.karaf.features.internal.region.SubsystemResolveContext.findProviders(SubsystemResolveContext.java:208)
~[?:?]
        at
org.apache.karaf.features.internal.region.SubsystemResolveContext.computeEdges(SubsystemResolveContext.java:138)
~[?:?]
        at
org.apache.karaf.features.internal.region.SubsystemResolveContext.computeDistances(SubsystemResolveContext.java:118)
~[?:?]
        at
org.apache.karaf.features.internal.region.SubsystemResolveContext.<init>(SubsystemResolveContext.java:96)
~[?:?]
        at
org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:231)
~[?:?]
        at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:391)
~[?:?]
        at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
~[?:?]
        at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
~[?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
~[?:1.8.0_212]
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
~[?:1.8.0_212]
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
~[?:1.8.0_212]
        at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_212]


>        Change in KAR installation behaviour
> --------------------------------------
>
>                 Key: KARAF-6716
>                 URL: https://issues.apache.org/jira/browse/KARAF-6716
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 4.3.0
>            Reporter: Sjoerd Brauer
>            Assignee: Jean-Baptiste Onofré
>            Priority: Critical
>              Labels: kar
>             Fix For: 4.3.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> So I noticed a difference in deploying the exact same kar in the new karaf
>  4.3.0.RC1 version and the older ones. When I try to install a kar with the
>  feature (simplified) found below with the mariadb JDBC driver it throws a
>  nullpointer exception with stacktrace found down below.
> But what I find odd is that this kar installs without problems on earlier
>  Karaf versions. What is furthermore odd is that only putting the mariadb
>  bundle in deploy works perfectly fine in both versions.
> Anyone any idea what is causing this odd behaviour and if it's a bug of the
>  karaf 4.3.0.RC1 version?
> Feature:
> {code:java}
>     <feature name="mariadb" version="${project.version}">
>         
>  
> <bundle>mvn:org.mariadb.jdbc/mariadb-java-client/${mariadb.client.version}</bundle>
>      </feature>{code}
> Stacktrace:
> {code:java}
> java.lang.NullPointerException: null
>          at
>  
> org.apache.karaf.features.internal.region.SubsystemResolveContext.getRegion(SubsystemResolveContext.java:270)
>  ~[?:?]
>          at
>  
> org.apache.karaf.features.internal.region.SubsystemResolveContext.access$000(SubsystemResolveContext.java:67)
>  ~[?:?]
>          at
>  
> org.apache.karaf.features.internal.region.SubsystemResolveContext$Visitor.contains(SubsystemResolveContext.java:302)
>  ~[?:?]
>          at
>  
> org.apache.karaf.features.internal.region.SubsystemResolveContext$Visitor.contains(SubsystemResolveContext.java:294)
>  ~[?:?]
>          at
>  
> org.apache.karaf.features.internal.region.AbstractRegionDigraphVisitor.visit(AbstractRegionDigraphVisitor.java:56)
>  ~[?:?]
>          at
>  
> org.eclipse.equinox.internal.region.SubgraphTraverser.visitRemainingSubgraph(SubgraphTraverser.java:37)
>  ~[?:?]
>          at
>  
> org.eclipse.equinox.internal.region.SubgraphTraverser.visitSubgraph(SubgraphTraverser.java:32)
>  ~[?:?]
>          at
>  
> org.eclipse.equinox.internal.region.StandardRegionDigraph.visitSubgraph(StandardRegionDigraph.java:374)
>  ~[?:?]
>          at
>  
> org.eclipse.equinox.internal.region.BundleIdBasedRegion.visitSubgraph(BundleIdBasedRegion.java:264)
>  ~[?:?]
>          at
>  
> org.apache.karaf.features.internal.region.SubsystemResolveContext.findProviders(SubsystemResolveContext.java:208)
>  ~[?:?]
>          at
>  
> org.apache.karaf.features.internal.region.SubsystemResolveContext.computeEdges(SubsystemResolveContext.java:138)
>  ~[?:?]
>          at
>  
> org.apache.karaf.features.internal.region.SubsystemResolveContext.computeDistances(SubsystemResolveContext.java:118)
>  ~[?:?]
>          at
>  
> org.apache.karaf.features.internal.region.SubsystemResolveContext.<init>(SubsystemResolveContext.java:96)
>  ~[?:?]
>          at
>  
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:231)
>  ~[?:?]
>          at
>  org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:391)
>  ~[?:?]
>          at
>  
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
>  ~[?:?]
>          at
>  
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
>  ~[?:?]
>          at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> ~[?:1.8.0_212]
>          at
>  
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  ~[?:1.8.0_212]
>          at
>  
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  ~[?:1.8.0_212]
>          at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_212]{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to