Uploaded image for project: 'ServiceMix 4'
  1. ServiceMix 4
  2. SMX4-765

ServiceMix doesn't start using JVM 1.5

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 4.3.0
    • 4.3.0
    • None
    • None
    • Linux Debian Squeeze
      Java version Sun 1.5.0_17

    Description

      ServiceMix doesn't start (nothing is displayed, and it appears as stuck).

      The problem is related to start of Aries Blueprint:
      11:56:51,562 | WARN | rint Extender: 3 | BlueprintContainerImpl | 7 - org.apache.aries.blueprint - 0.2.0.incubating | Bundle org.apache.karaf.features.command is waiting for namespace handlers [(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://karaf.apache.org/xmlns/shell/v1.0.0))]
      11:56:51,563 | ERROR | rint Extender: 1 | BlueprintContainerImpl | 7 - org.apache.aries.blueprint - 0.2.0.incubating | Unable to start blueprint container for bundle org.apache.aries.blueprint
      java.lang.NoSuchMethodError: com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(Ljavax/xml/transform/Source;)Lcom/sun/org/apache/xerces/internal/xni/grammars/Grammar;
      at com.sun.org.apache.xerces.internal.jaxp.validation.xs.SchemaFactoryImpl.newSchema(SchemaFactoryImpl.java:206)[:1.5.0_17]
      at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.getSchema(NamespaceHandlerRegistryImpl.java:236)[7:org.apache.aries.blueprint:0.2.0.incubating]
      at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.getSchema(NamespaceHandlerRegistryImpl.java:306)[7:org.apache.aries.blueprint:0.2.0.incubating]
      at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:261)[7:org.apache.aries.blueprint:0.2.0.incubating]
      at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:213)[7:org.apache.aries.blueprint:0.2.0.incubating]
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)[:1.5.0_17]
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)[:1.5.0_17]
      at java.util.concurrent.FutureTask.run(FutureTask.java:123)[:1.5.0_17]
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:65)[:1.5.0_17]
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:168)[:1.5.0_17]
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)[:1.5.0_17]
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)[:1.5.0_17]
      at java.lang.Thread.run(Thread.java:595)[:1.5.0_17]

      Regarding etc/jre.properties, the com.sun.org.apache.xerces.internal package is only defined for JRE-1.6. So it means that a dependency is not up to date in ServiceMix around Xerces.

      I'm digging this issue.

      Attachments

        Activity

          People

            jbonofre Jean-Baptiste Onofré
            jbonofre Jean-Baptiste Onofré
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: