3 Replies Latest reply on Jul 11, 2013 3:16 AM by jasonnh

    fabric containers and offline repository creation problems

    jasonnh

      Hi,

       

      I use FUSE Enterprise 7.1.0 with fabric and an offline repository.  I intermittently get the following when the containers are being created:

       

      java.io.IOException: URL could not be resolved. : ...../xml/features

       

      The containers are created by a combination of:

       

      container-create-child

       

      and then one or more

       

      container-add-profile

       

      Adding all the profiles to container-create-child command does not help.

       

      The error suggests a problem similar to:

       

      http://fusesource.com/issues/browse/FABRIC-398

       

      But the workaround for that does not help and the file:

      file\:$\{karaf.data}/maven/agent

       

      Does not exist - there is a folder called proxy in that folder but not agent.

       

      I also intermittently get one or more containers stuck in the 'restarting' state and being unusable.

       

      Trying the whole installation procedure again, i.e. clean FUSE and rerun all karaf scripts normally works but not always.

       

      Has anybody else seen this problem?

       

      Any help much appreciated.

       

      Thanks.

        • 1. Re: fabric containers and offline repository creation problems
          iocanel

          I would upgrade to the 7.2.0, which solves most of these issues.

           

          If this is not possible, I could help you work around it, if you provided a stacktrace.

          • 2. Re: fabric containers and offline repository creation problems
            jasonnh

            Sorry for not replying quicker.

             

            Upgrading to 7.2.0 is not an option for us.

             

            A typical stack trace is below.

             

            java.io.IOException: URL mvn:org.apache.camel.karaf/apache-camel/2.10.4/xml/features could not be resolved. : mvn:org.apache.camel.karaf/apache-camel/2.10.4/xml/features

                    at org.apache.karaf.features.internal.RepositoryImpl.load(RepositoryImpl.java:240)[67:org.fusesource.fabric.fabric-agent:7.1.0.fuse-047]

                    at org.fusesource.fabric.agent.DeploymentAgent.addRepository(DeploymentAgent.java:479)[67:org.fusesource.fabric.fabric-agent:7.1.0.fuse-047]

                    at org.fusesource.fabric.agent.DeploymentAgent.doUpdate(DeploymentAgent.java:360)[67:org.fusesource.fabric.fabric-agent:7.1.0.fuse-047]

                    at org.fusesource.fabric.agent.DeploymentAgent$1.run(DeploymentAgent.java:238)[67:org.fusesource.fabric.fabric-agent:7.1.0.fuse-047]

                    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_21]

                    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[:1.7.0_21]

                    at java.util.concurrent.FutureTask.run(FutureTask.java:166)[:1.7.0_21]

                    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_21]

                    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_21]

                    at java.lang.Thread.run(Thread.java:722)[:1.7.0_21]

            Caused by: java.lang.RuntimeException: URL mvn:org.apache.camel.karaf/apache-camel/2.10.4/xml/features could not be resolved.

                    at org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:195)[1:org.ops4j.pax.url.mvn:1.3.5]

                    at org.apache.karaf.features.internal.RepositoryImpl.load(RepositoryImpl.java:87)[67:org.fusesource.fabric.fabric-agent:7.1.0.fuse-047]

                    ... 9 more

             

            Edited by: jasonnh on Jul 8, 2013 12:47 PM

            • 3. Re: fabric containers and offline repository creation problems
              jasonnh

              Hi,

               

              "I would upgrade to the 7.2.0, which solves most of these issues."

               

              Please can you point me in the direction of the JIRA issues / commits that you think help this sort of problem in 7.2.0?

               

              Thanks.