14 Replies Latest reply on Jan 13, 2011 7:46 AM by Richard Tomlinson

    Obtain more log information on JBI deploy failure.

    Richard Tomlinson Newbie

      I'm having problems deploying a JBI SA.   The key error is:  Requirements not met for JBI artifact in bundle null (null).

       

      I've enabled full debug logging (log:set DEBUG  and also editing org.ops4j.pax.logging.cfg to change the level to debug, even enabling service mix debugging by adding log4j.category.org.apache.servicemix=DEBUG).   And yet, after all of this I get no further information about what requirement is not met.   My guess is there's some internal exception being swallowed and not reported.   What's the best way to trace deployment problems such as this?

       

      Full log snippet:

       

      09:09:16,780 | DEBUG | l Console Thread | ServiceRecipe                    | lueprint.container.ServiceRecipe  226 | 7 - org.apache.aries.blueprint - 0.2.0.incubating | Retrieving service for bundle org.apache.felix.gogo.runtime_0.4.0 and service registration {org.apache.karaf.shell.console.CompletableFunction, org.osgi.service.command.Function}={osgi.command.function=install, osgi.command.scope=osgi, service.id=82}

      09:09:16,780 | DEBUG | l Console Thread | BlueprintContainerImpl           | container.BlueprintContainerImpl  701 | 7 - org.apache.aries.blueprint - 0.2.0.incubating | Instantiating component shell-13

      09:09:16,780 | DEBUG | l Console Thread | BlueprintContainerImpl           | container.BlueprintContainerImpl  701 | 7 - org.apache.aries.blueprint - 0.2.0.incubating | Instantiating component blueprintBundleContext

      09:09:16,780 | DEBUG | Event Dispatcher |                      | ?                                   ? | 185 -  -  | BundleEvent INSTALLED

      09:09:16,796 | DEBUG | l Console Thread | BlueprintExtender                | rint.container.BlueprintExtender  210 | 7 - org.apache.aries.blueprint - 0.2.0.incubating | Scanning bundle null for blueprint application

      09:09:16,796 | DEBUG | Event Dispatcher |                      | ?                                   ? | 185 -  -  | BundleEvent RESOLVED

      09:09:16,796 | DEBUG | l Console Thread | BlueprintExtender                | rint.container.BlueprintExtender  276 | 7 - org.apache.aries.blueprint - 0.2.0.incubating | No blueprint application found in bundle null

      09:09:16,796 | DEBUG | l Console Thread | Activator                        | apache.camel.impl.osgi.Activator   84 | 58 - org.apache.camel.camel-core - 2.4.0.fuse-02-00 | Bundle started: null

      09:09:16,796 | DEBUG | l Console Thread | ContextLoaderListener            | .activator.ContextLoaderListener  681 | 62 - org.springframework.osgi.extender - 1.2.0 | Scanning bundle for configurations...

      09:09:16,796 | DEBUG | l Console Thread | ContextLoaderListener            | .activator.ContextLoaderListener  687 | 62 - org.springframework.osgi.extender - 1.2.0 | Creating an application context for bundle

      09:09:16,796 | DEBUG | l Console Thread | ContextLoaderListener            | .activator.ContextLoaderListener  698 | 62 - org.springframework.osgi.extender - 1.2.0 | No application context created for bundle

      09:09:16,796 | DEBUG | l Console Thread | BundleWatcher                    | .swissbox.extender.BundleWatcher  176 | 97 - org.ops4j.pax.web.pax-web-extender-war - 0.7.3 | Scanning bundle

      09:09:16,796 | DEBUG | l Console Thread | Deployer                         | cemix.jbi.deployer.impl.Deployer  281 | 84 - org.apache.servicemix.jbi.deployer - 1.3.0.fuse-02-00 | Checking bundle: 'null (null)'

      09:09:16,796 | INFO  | l Console Thread | Deployer                         | cemix.jbi.deployer.impl.Deployer  323 | 84 - org.apache.servicemix.jbi.deployer - 1.3.0.fuse-02-00 | Deploying bundle 'null (null)' as a JBI service assembly

      09:09:16,796 | WARN  | l Console Thread | Deployer                         | cemix.jbi.deployer.impl.Deployer  339 | 84 - org.apache.servicemix.jbi.deployer - 1.3.0.fuse-02-00 | Requirements not met for JBI artifact in bundle null (null). Installation pending. org.apache.servicemix.jbi.deployer.impl.PendingException: Component not installed: servicemix-cxf-bc

      09:09:16,796 | DEBUG | Event Dispatcher |                      | ?                                   ? | 185 -  -  | BundleEvent STARTED

        • 1. Re: Obtain more log information on JBI deploy failure.
          Freeman(Yue) Fang Master

          Hi,

           

          At the end of the log, there's

          Installation pending. org.apache.servicemix.jbi.deployer.impl.PendingException: Component not installed: servicemix-cxf-bc

           

          I think servicemix-cxf-bc component not installed caused your SA deploy failure.

           

          Your SA depend on servicemix-cxf-bc component, right?

          You need check the former part of your log to see why servicemix-cxf-bc component not get installed.

          Which FUSE ESB version you are using? servicemix-cxf-bc component should be installed by default, it's  a default feature.

           

          Freeman

          • 2. Re: Obtain more log information on JBI deploy failure.
            Richard Tomlinson Newbie

            My SU depends on cxf-bc so I'm using 4.3 fuse 03 with a dependency in my SU of:

             

                       

             

            No further information in the logs regarding to cxf-bc, just the messages shown in the snippet below.

             

            Thanks

            • 3. Re: Obtain more log information on JBI deploy failure.
              Freeman(Yue) Fang Master

              Hi,

               

              Did you change any configuration for FUSE ESB before you install your SA?

              Could you grep your log file to find anything wrong with servicemix-cxf-bc?

               

              Does your computer running FUSE ESB has internet connection?

               

              Freeman

              • 4. Re: Obtain more log information on JBI deploy failure.
                Richard Tomlinson Newbie

                No config changes to ESB.   Nothing else shown in the logs for servicemix-cxf-bc.

                 

                Computer behind proxied firewall which doesnt have direct connection to the 'Net.

                 

                What I'm noticing is that this problem appears with configuration issues - Eg, make an incorrect  definition in a pom and it builds ok but cryptically errors on deploy.  I'm presuming the PendingException reported by the Deployer doesnt really tell all the story of what's happened and that there's some other exception occuring which is being swallowed?

                • 5. Re: Obtain more log information on JBI deploy failure.
                  Freeman(Yue) Fang Master

                  Hi,

                   

                  Actually the log already tell you that a component which your SA depend on not installed cause the problem.

                   

                  Your machine can't access the internet is a problem, if you don't have all necessary bundles available on your local repo, starting FUSE ESB will try to download from remote repo.

                   

                  Could you post

                  osgi:list

                  result? I believe not all bundles get installed correctly.

                   

                  Freeman

                  • 6. Re: Obtain more log information on JBI deploy failure.
                    Richard Tomlinson Newbie

                    Restarted the server and its now reporting:

                     

                    11:53:50,240 | DEBUG | Event Dispatcher | Activator                        | apache.camel.impl.osgi.Activator   84 | 58 - org.apache.camel.camel-core - 2.4.0.fuse-02-00 | Bundle started: servicemix-soap

                    11:53:50,240 | DEBUG | Event Dispatcher | servicemix-cxf-bc                | ?                                   ? | 131 - servicemix-cxf-bc - 2010.02.0.fuse-02-00 | FrameworkEvent ERROR

                    org.osgi.framework.BundleException: The bundle "servicemix-cxf-bc_2010.2.0.fuse-02-00 " could not be resolved. Reason: Missing Constraint: Import-Package: org.apache.xbean.blueprint.context.impl; version="0.0.0"

                            at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1317)[osgi-3.6.0.v20100517.jar:]

                            at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1301)[osgi-3.6.0.v20100517.jar:]

                            at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:319)[osgi-3.6.0.v20100517.jar:]

                            at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:374)[osgi-3.6.0.v20100517.jar:]

                            at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1067)[osgi-3.6.0.v20100517.jar:]

                            at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:561)[osgi-3.6.0.v20100517.jar:]

                            at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:546)[osgi-3.6.0.v20100517.jar:]

                            at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:459)[osgi-3.6.0.v20100517.jar:]

                            at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)[osgi-3.6.0.v20100517.jar:]

                            at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:440)[osgi-3.6.0.v20100517.jar:]

                            at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)[osgi-3.6.0.v20100517.jar:]

                            at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:337)[osgi-3.6.0.v20100517.jar:]

                    11:53:50,240 | DEBUG | Event Dispatcher | NamespaceManager                 | nternal.support.NamespaceManager  147 | 62 - org.springframework.osgi.extender - 1.2.0 | Adding namespace handler resolver for Apache ServiceMix :: Components :: Shared Libraries :: SOAP Stack (servicemix-soap)

                    11:53:50,240 | DEBUG | Event Dispatcher | NamespacePlugins                 | nternal.support.NamespacePlugins  102 | 62 - org.springframework.osgi.extender - 1.2.0 | Adding as handler Apache ServiceMix :: Components :: Shared Libraries :: SOAP Stack (servicemix-soap)

                    11:53:50,240 | DEBUG | Event Dispatcher | ContextLoaderListener            | .activator.ContextLoaderListener  681 | 62 - org.springframework.osgi.extender - 1.2.0 | Scanning bundle for configurations...

                    11:53:50,240 | DEBUG | Event Dispatcher | ContextLoaderListener            | .activator.ContextLoaderListener  687 | 62 - org.springframework.osgi.extender - 1.2.0 | Creating an application context for bundle

                     

                     

                    Also for servicemix-file_2010.2.0.fuse-02-00,  org.apache.xbean.blueprint_3.7.0, etc

                    • 7. Re: Obtain more log information on JBI deploy failure.
                      Richard Tomlinson Newbie

                      Here's the osgi:list.   If its trying to pull from the local repo is there a recommended way of ensuring all artifacts are available?

                       

                       

                       

                      / ___|  ___ _ ____   () ___ ___|  \/  (_)_  __

                      \___ \ / _ \ '__\ \ / / |/ __/ _ \ |\/| | \ \/ /

                      ___) |  __/ |   \ V /| | (_|  __/ |  | | |>   osgi:list

                      START LEVEL 100

                         ID   State         Blueprint      Spring    Level  Name

                      OSGi System Bundle (3.6.0.v20100517)

                      OPS4J Pax Url - mvn: (1.2.1)

                      OPS4J Pax Url - wrap: (1.2.1)

                      OPS4J Pax Logging - API (1.5.3)

                      OPS4J Pax Logging - Service (1.5.3)

                      Apache Felix Configuration Admin Service (1.2.4)

                      Apache Felix File Install (3.0.2)

                      Apache Aries Blueprint Bundle (0.2.0.incubating)

                      Apache Karaf :: Admin Core (2.0.0.fuse-02-00)

                      Apache Karaf :: Shell OSGi Commands (2.0.0.fuse-02-00)

                      Apache Karaf :: Management (2.0.0.fuse-02-00)

                      Apache Karaf :: Features Command (2.0.0.fuse-02-00)

                      Apache Karaf :: Shell Console (2.0.0.fuse-02-00)

                      Apache Karaf :: Features Management (2.0.0.fuse-02-00)

                      Apache Aries JMX Blueprint Bundle (0.2.0.incubating)

                      Apache Karaf :: Features Deployer (2.0.0.fuse-02-00)

                      Apache Karaf :: Shell Development Commands (2.0.0.fuse-02-00)

                      Apache Felix Gogo Shell Runtime (0.4.0)

                      Apache Karaf :: Shell SSH (2.0.0.fuse-02-00)

                      Apache Karaf :: Admin Management (2.0.0.fuse-02-00)

                      Apache Karaf :: JAAS Modules (2.0.0.fuse-02-00)

                      Apache Karaf :: Features Core (2.0.0.fuse-02-00)

                      Apache Karaf :: Admin Command (2.0.0.fuse-02-00)

                      Apache Karaf :: Shell PackageAdmin Commands (2.0.0.fuse-02-00)

                      Apache Aries JMX Bundle (0.2.0.incubating)

                      Apache MINA Core (2.0.0.RC1)

                      Apache Karaf :: Shell Log Commands (2.0.0.fuse-02-00)

                      Apache Karaf :: Blueprint Deployer (2.0.0.fuse-02-00)

                      Apache Karaf :: JAAS Config (2.0.0.fuse-02-00)

                      Apache Karaf :: Spring Deployer (2.0.0.fuse-02-00)

                      Apache Mina SSHD :: Core (0.4.0)

                      Apache Karaf :: Shell Various Commands (2.0.0.fuse-02-00)

                      Apache Karaf :: Shell ConfigAdmin Commands (2.0.0.fuse-02-00)

                      geronimo-annotation_1.0_spec (1.1.1)

                      geronimo-jta_1.1_spec (1.1.1)

                      geronimo-jms_1.1_spec (1.1.1)

                      geronimo-j2ee-management_1.1_spec (1.0.1)

                      Apache ServiceMix Bundles: commons-pool-1.5.4 (1.5.4.1)

                      Apache ServiceMix :: Bundles :: commons-collections 3.2.1 (3.2.1.fuse)

                      Apache ServiceMix Bundles: commons-lang-2.4 (2.4.0.3)

                      Apache ServiceMix :: Bundles :: commons-codec (1.3.0.3)

                      Apache ServiceMix Bundles: oro-2.0.8 (2.0.8.3)

                      Apache ServiceMix Bundles: velocity-1.6.2 (1.6.2.3)

                      Apache ServiceMix :: Bundles :: jasypt (1.6.0.1)

                      Apache ServiceMix :: Bundles :: aopalliance (1.0.0.4)

                      Spring Core (3.0.3.RELEASE)

                      Spring ASM (3.0.3.RELEASE)

                      Spring Aspects (3.0.3.RELEASE)

                      Spring Expression Language (3.0.3.RELEASE)

                      Spring Beans (3.0.3.RELEASE)

                      Spring AOP (3.0.3.RELEASE)

                      Spring Context (3.0.3.RELEASE)

                      Spring Context Support (3.0.3.RELEASE)

                      Apache ServiceMix Specs :: ACTIVATION API 1.4 (1.5.0)

                      Apache ServiceMix :: Specs :: JAXB API 2.1 (1.6.0)

                      Apache ServiceMix :: Specs :: Stax API 1.0 (1.6.0)

                      Apache ServiceMix Bundles: jaxb-impl-2.1.12 (2.1.12.1)

                      Commons Management (1.0)

                      camel-core (2.4.0.fuse-02-00)

                      Apache ServiceMix :: Bundles :: cglib (2.1.0.3_6)

                      spring-osgi-io (1.2.0)

                      spring-osgi-core (1.2.0)

                      spring-osgi-extender (1.2.0)

                      spring-osgi-annotation (1.2.0)

                      Spring Transaction (3.0.3.RELEASE)

                      camel-spring (2.4.0.fuse-02-00)

                      Apache ServiceMix Naming (1.3.0.fuse-02-00)

                      Apache Aries Transaction Manager (0.2.0.incubating)

                      Apache ServiceMix Document (1.3.0.fuse-02-00)

                      Apache ServiceMix :: Utils (1.3.0.fuse-01-00)

                      Apache ServiceMix NMR API (1.3.0.fuse-02-00)

                      Apache ServiceMix NMR Core (1.3.0.fuse-02-00)

                      Apache ServiceMix NMR OSGi (1.3.0.fuse-02-00)

                      Apache ServiceMix NMR Commands (1.3.0.fuse-02-00)

                      Apache ServiceMix NMR Management (1.3.0.fuse-02-00)

                      Stax2 API (3.0.2)

                      Woodstox XML-processor (4.0.8)

                      Apache ServiceMix :: Specs :: Activation API 1.4 (1.6.0)

                      Apache ServiceMix :: Specs :: JBI API 1.0 (1.6.0)

                      Apache ServiceMix Bundles: wsdl4j-1.6.2 (1.6.2.2)

                      Apache ServiceMix Bundles: ant-1.7.0 (1.7.0.3)

                      Apache ServiceMix :: Components :: Shared Libraries :: Common (2010.02.0.fuse-02-00)

                      Apache ServiceMix JBI Runtime (1.3.0.fuse-02-00)

                      Apache ServiceMix JBI OSGi (1.3.0.fuse-02-00)

                      Apache ServiceMix JBI Deployer (1.3.0.fuse-02-00)

                      Apache ServiceMix JBI Commands (1.3.0.fuse-02-00)

                      Spring JMS (3.0.3.RELEASE)

                      Apache ServiceMix JBI Clustering Requestor (1.3.0.fuse-02-00)

                      Apache ServiceMix JBI Clustering Engine (1.3.0.fuse-02-00)

                      Apache ServiceMix JBI Clustering Config (1.3.0.fuse-02-00)

                      geronimo-servlet_2.5_spec (1.1.2)

                      Apache ServiceMix :: Bundles :: jetty (6.1.26.1-fuse)

                      OPS4J Pax Web - API (0.7.3)

                      OPS4J Pax Web - Service SPI (0.7.3)

                      OPS4J Pax Web - Runtime (0.7.3)

                      OPS4J Pax Web - Jetty (0.7.3)

                      OPS4J Pax Web - Jsp Support (0.7.3)

                      OPS4J Pax Web - Extender - WAR (0.7.3)

                      OPS4J Pax Web - Extender - Whiteboard (0.7.3)

                      OPS4J Pax Url - war:, war-i: (1.1.3)

                      Apache Karaf :: WAR Deployer (2.0.0.fuse-02-00)

                      Apache XBean :: Spring (3.7)

                      Apache XBean :: Classloader (3.7)

                      Apache XBean :: OSGI Blueprint Namespace Handler (3.7)

                      geronimo-j2ee-connector_1.5_spec (2.0.0)

                      geronimo-ws-metadata_2.0_spec (1.1.2)

                      Apache ServiceMix :: Specs :: SAAJ API 1.3 (1.6.0)

                      Apache ServiceMix :: Specs :: JAXWS API 2.1 (1.6.0)

                      JavaMail API (1.4.3)

                      Apache ServiceMix Bundles: asm-2.2.3 (2.2.3.3)

                      Apache ServiceMix Bundles: FastInfoset-1.2.7 (1.2.7.2)

                      Apache ServiceMix Bundles: neethi-2.0.4 (2.0.4.2)

                      Apache ServiceMix Bundles: saaj-impl-1.3.2 (1.3.2.1)

                      XmlSchema (1.4.5)

                      Apache ServiceMix Bundles: xmlresolver-1.2 (1.2.0.2)

                      Apache ServiceMix Bundles: xmlsec-1.4.3 (1.4.3.2)

                      WSS4J (1.5.9)

                      Apache ServiceMix Bundles: xercesImpl-2.9.1 (2.9.1.3)

                      Apache ServiceMix Bundles: bcel-5.2 (5.2.0.2)

                      Apache ServiceMix Bundles: xalan-2.7.1 (2.7.1.2)

                      Apache ServiceMix :: Specs :: JSR-311 API 1.0 (1.6.0)

                      Apache ServiceMix Bundles: opensaml-1.1 (1.1.0.3)

                      Apache ServiceMix Bundles: xmlbeans-2.4.0 (2.4.0.3)

                      Apache ServiceMix Bundles: abdera-0.4.0-incubating (0.4.0.incubating_3)

                      Apache ServiceMix Bundles: commons-codec-1.3 (1.3.0.2)

                      jettison (1.2)

                      Apache ServiceMix Bundles: jdom-1.1 (1.1.0.2)

                      Axiom API (1.2.8)

                      Axiom API (1.2.8)

                      Apache CXF Bundle Jar (2.2.11.fuse-00-00)

                      Apache ServiceMix :: Components :: Shared Libraries :: SOAP Stack v2 (2010.02.0.fuse-02-00)

                      Apache ServiceMix :: Components :: CXF Binding Component (2010.02.0.fuse-02-00)

                      Apache ServiceMix :: Components :: File Binding Component (2010.02.0.fuse-02-00)

                      Apache ServiceMix Bundles: commons-net-1.4.1 (1.4.1.3)

                      Apache ServiceMix :: Components :: FTP Binding Component (2010.02.0.fuse-02-00)

                      Apache ServiceMix Bundles: commons-httpclient-3.1 (3.1.0.4)

                      Apache ServiceMix :: Components :: Shared Libraries :: SOAP Stack (2010.02.0.fuse-02-00)

                      Apache ServiceMix :: Components :: HTTP Binding Component (2010.02.0.fuse-02-00)

                      Apache ServiceMix :: Components :: JMS Binding Component (2010.02.0.fuse-02-00)

                      Apache ServiceMix :: Components :: Mail Binding Component (2010.02.0.fuse-02-00)

                      Apache ServiceMix :: Components :: Bean Service Engine (2010.02.0.fuse-02-00)

                      Apache ServiceMix :: Components :: Camel Service Engine (2010.02.0.fuse-02-00)

                      Apache CXF Runtime JBI Binding (2.2.11.fuse-00-00)

                      Apache CXF Runtime JBI Transport (2.2.11.fuse-00-00)

                      Apache ServiceMix :: Components :: CXF Service Engine (2010.02.0.fuse-02-00)

                      Apache ServiceMix Bundles: core-3.2.3.v_686_R32x (3.2.3.3)

                      Apache ServiceMix Bundles: antlr-3.0.1 (3.0.1.3)

                      Apache ServiceMix Bundles: mvel-1.3.12 (1.3.12.1)

                      Apache ServiceMix Bundles: drools-4.0.7 (4.0.7.4)

                      Apache ServiceMix :: Components :: Drools Service Engine (2010.02.0.fuse-02-00)

                      Apache ServiceMix :: Components :: EIP Service Engine (2010.02.0.fuse-02-00)

                      Apache ServiceMix Bundles: quartz-1.6.1 (1.6.1.3)

                      Apache ServiceMix Bundles: oscore-2.2.4 (2.2.4.3)

                      Apache ServiceMix Bundles: propertyset-1.3 (1.3.0.3)

                      Apache ServiceMix Bundles: osworkflow-2.7.0 (2.7.0.3)

                      Apache ServiceMix :: Components :: OSWorkflow Service Engine (2010.02.0.fuse-02-00)

                      Apache ServiceMix :: Components :: Quartz Service Engine (2010.02.0.fuse-02-00)

                      Apache ServiceMix :: Specs :: Scripting API 1.0 (1.6.0)

                      Apache ServiceMix Bundles: antlr-2.7.7 (2.7.7.2)

                      Apache ServiceMix Bundles: groovy-1.5.6 (1.5.6.3)

                      Apache ServiceMix Bundles: js-1.7R1 (1.0.0.7R1_2)

                      Apache ServiceMix Bundles: jruby-1.1.2 (1.1.2.2)

                      ScriptEngines :: Groovy (1.1)

                      ScriptEngines :: JavaScript (1.1)

                      ScriptEngines :: JRuby (1.1)

                      Apache ServiceMix :: Components :: JSR-223 Scripting Service Engine (2010.02.0.fuse-02-00)

                      Apache ServiceMix :: Components :: Validation Service Engine (2010.02.0.fuse-02-00)

                      Apache ServiceMix Bundles: saxon-9.1.0.8 (9.1.0.8_1-fuse)

                      Apache ServiceMix :: Components :: Saxon Service Engine (2010.02.0.fuse-02-00)

                      karaf@root>

                      • 8. Re: Obtain more log information on JBI deploy failure.
                        Freeman(Yue) Fang Master

                        So lots of bundles not get started correctly, including the servicemix-cxf-bc bundle.

                         

                        The general solution for machines behind a firewall which need access mvn repo is using nexus server, only the nexus server can access external internet, and the internal machines just access the nexus server.

                         

                        Here the nexus server play the role like a proxy, you may need google to get more details.

                         

                        And fuse team may(I'm not sure the details) ever build offline repos for some customers, but I'm fear it's not free.

                         

                        Freeman

                        • 9. Re: Obtain more log information on JBI deploy failure.
                          Richard Tomlinson Newbie

                          I've put our local Nexus server in the org.ops4j.pax.url.mvn.cfg file however its failing on jexl2 and I'm not sure why as it should come from central.  I've modified the props for the settings.xml location, even copying settings.xml into $M2_HOME/conf but all to no avail. The jexl 2.0 jar is in the repo so it should be accessable.  Anything special about this dependency or the way in which servicemix decides to resolve the deps?

                           

                          15:26:39,691 | DEBUG | rint Extender: 1 | war                              | ?                                   ? | 100 - org.apache.karaf.deployer.war - 2.0.0.fuse-02-00 | ServiceEvent REGISTERED

                          15:26:39,691 | DEBUG | rint Extender: 1 | BlueprintEventDispatcher         | ntainer.BlueprintEventDispatcher  123 | 7 - org.apache.aries.blueprint - 0.2.0.incubating | Sending blueprint container event BlueprintEvent[type=CREATED] for bundle org.apache.karaf.deployer.war

                          15:26:39,691 | DEBUG | nt Dispatcher: 1 | BlueprintListener                | raf.shell.osgi.BlueprintListener   85 | 9 - org.apache.karaf.shell.osgi - 2.0.0.fuse-02-00 | Blueprint app state changed to Created for bundle 100

                          15:26:39,691 | DEBUG | rint Extender: 1 | BlueprintContainerImpl           | container.BlueprintContainerImpl  231 | 7 - org.apache.aries.blueprint - 0.2.0.incubating | Running blueprint container for bundle org.apache.karaf.deployer.war in state Created

                          15:26:39,894 | DEBUG | Event Dispatcher | BlueprintExtender                | rint.container.BlueprintExtender  210 | 7 - org.apache.aries.blueprint - 0.2.0.incubating | Scanning bundle org.apache.geronimo.specs.geronimo-j2ee-connector_1.5_spec for blueprint application

                          15:26:39,910 | DEBUG | Event Dispatcher | BlueprintExtender                | rint.container.BlueprintExtender  276 | 7 - org.apache.aries.blueprint - 0.2.0.incubating | No blueprint application found in bundle org.apache.geronimo.specs.geronimo-j2ee-connector_1.5_spec

                          15:26:39,910 | DEBUG | Event Dispatcher | Activator                        | apache.camel.impl.osgi.Activator   84 | 58 - org.apache.camel.camel-core - 2.4.0.fuse-02-00 | Bundle started: org.apache.geronimo.specs.geronimo-j2ee-connector_1.5_spec

                          15:26:39,910 | DEBUG | Event Dispatcher | blueprint                        | ?                                   ? | 103 - org.apache.xbean.blueprint - 3.7 | FrameworkEvent ERROR

                          org.osgi.framework.BundleException: The bundle "org.apache.xbean.blueprint_3.7.0 " could not be resolved. Reason: Missing Constraint: Import-Package: org.apache.commons.jexl2; version="2.0.0"

                                  at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1317)[osgi-3.6.0.v20100517.jar:]

                                  at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1301)[osgi-3.6.0.v20100517.jar:]

                                  at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:319)[osgi-3.6.0.v20100517.jar:]

                                  at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:374)[osgi-3.6.0.v20100517.jar:]

                                  at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1067)[osgi-3.6.0.v20100517.jar:]

                                  at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:561)[osgi-3.6.0.v20100517.jar:]

                                  at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:546)[osgi-3.6.0.v20100517.jar:]

                                  at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:459)[osgi-3.6.0.v20100517.jar:]

                                  at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)[osgi-3.6.0.v20100517.jar:]

                                  at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:440)[osgi-3.6.0.v20100517.jar:]

                                  at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)[osgi-3.6.0.v20100517.jar:]

                                  at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:337)[osgi-3.6.0.v20100517.jar:]

                          • 10. Re: Obtain more log information on JBI deploy failure.
                            Freeman(Yue) Fang Master

                            Hi,

                             

                            The org/apache/commons/commons-jexl/2.0.1/commons-jexl-2.0.1.jar is in $FUSE_ESB/system folder which is org.ops4j.pax.url.mvn.defaultRepositories , this is the first place maven(with pax-url-mvn) will check, so it needn't try to download it from any remote server, it's just here locally.

                             

                            What you changed in org.ops4j.pax.url.mvn.cfg? and what you changed in settings.xml?

                             

                            Freeman

                            • 11. Re: Obtain more log information on JBI deploy failure.
                              Richard Tomlinson Newbie

                              When I look in /system/... commons-jexl is 2.0.1 not the 2.0.0  dependency being looked for.

                               

                              xbean-blueprint 3.7.0 has a dep on jexl 2.0

                               

                              Is this some sort of version mixup?

                               

                              My settings.xml is unchanged and points to our Nexus repo and is fine for all other projects so, nothing wrong there.

                               

                              I have the prop set so it refers to my settings.xml on my network profile:

                               

                              org.ops4j.pax.url.mvn.settings=H:/.m2/settings.xml

                               

                              And I've prepended the nexus repo:

                               

                              org.ops4j.pax.url.mvn.repositories= \

                                  http://maven.xxxxx.com:8383/nexus/content/groups/xxxxx, \

                                  http://repo1.maven.org/maven2, \

                               

                              (xxxxx is the client name, obscured)

                               

                              Looking in the repo, the file is there

                               

                              http://maven.xxxxx.com:8383/nexus/content/groups/xxxxx/org/apache/commons/commons-jexl/2.0/

                               

                              Shows:

                              Name     Last Modified     Size     Description

                              Parent Directory

                              commons-jexl-2.0.jar      Tue Feb 02 17:33:36 GMT 2010      210653      

                              commons-jexl-2.0.jar.sha1      Tue Feb 02 17:33:36 GMT 2010      40      

                              commons-jexl-2.0.pom      Tue Feb 02 17:33:36 GMT 2010      14196      

                              commons-jexl-2.0.pom.sha1      Tue Feb 02 17:33:36 GMT 2010      40      

                               

                              So, I'm happy that the repo is accessible and holding the correct jar.

                              • 12. Re: Obtain more log information on JBI deploy failure.
                                Freeman(Yue) Fang Master

                                Hi,

                                It's not a version mismatch.

                                 

                                In OSGi world Import-Package version=?2.0.0? mean [2.0.0, infinity),  so 2.0.1 is ok.

                                 

                                I think the real problem isn't it can't download the commons-jexl-2.0.1.jar, as it already in the system folder, it's should be a problem that it can't download some bundle which commons-jexl depend on.

                                 

                                Freeman

                                • 13. Re: Obtain more log information on JBI deploy failure.
                                  Richard Tomlinson Newbie

                                  As a follow up to this I have more information.   This problem is logged as defect ESB-1324.   If I take a fuse bundle which was on my laptop that has been running with no firewall, and transfer it to the PC behind the firewall, the problem goes away.   The issue may relate to running  a new fuse deployment behind a firewall and subsequent errors that are not rectified.   So until that defect is resolved, run on a non-firewalled pc first before zipping up, transferring then running on a firewalled one....

                                  • 14. Re: Obtain more log information on JBI deploy failure.
                                    Freeman(Yue) Fang Master

                                    Hi,

                                     

                                    Not sure ESB-1324 is a real problem, as we do ship commons-jexl-2.0.1.jar in distro, and per OSGi spec, it's ok for xbean-blueprint 3.7.0 import, as I explained before,

                                    Import-Package version=2.0.0 mean [2.0.0, infinity).

                                    And I start FUSE ESB without network connection, it works for me.(I intend to delete commons-jexl from my local repo before I start FUSE ESB, so commons-jexl-2.0.1.jar  shipped with distro in system/org/apache/commons/commons-jexl/2.0.1/ is used )

                                     

                                    I'm not sure why your nexus proxy doesn't work,  here is a similar post[1], I hope it could help.

                                     

                                    http://fusesource.com/forums/thread.jspa?messageID=7513&#7513

                                     

                                    Freeman