Geronimo
  1. Geronimo
  2. GERONIMO-6221

Error"Unable to start blueprint container for bundle org.apache.karaf.shell.obr" happened when stop the service that geronimo server as

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 3.0-beta-1
    • Fix Version/s: 3.0-beta-2
    • Component/s: commands
    • Security Level: public (Regular issues)
    • Labels:
      None
    • Environment:

      s390x GNU/Linux,x86_64 GNU/Linux
      IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux s390x-64 jvmxz6460sr9-20110203_74623 (JIT enabled, AOT enabled)

    • Patch Info:
      Patch Available

      Description

      1. Using the build Nov 17 09:40:41 UTC 2011 of geronimo 3.0 snapshot
      2. Run geronimo as a linux service:
      <geronimo_home>/bin#./register-service add gservice
      <geronimo_home>/bin#gservice start
      3. Stop the service:
      <geronimo_home>/bin#gservice stop
      4.But service can't be stopped and fond error:
      Could not communicate with the server. The server may not be running or the port number may be incorrect (Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
      java.net.ConnectException: Connection refused])
      Locating server on localhost:1099... 2011-11-28 20:17:45,730 ERROR [BlueprintContainerImpl] Unable to start blueprint container for bundle org.apache.karaf.shell.obr
      org.osgi.service.blueprint.container.ComponentDefinitionException: Unsupported node namespace: http://karaf.apache.org/xmlns/shell/v1.0.0
      at org.apache.aries.blueprint.container.Parser.getNamespaceHandler(Parser.java:1262)
      at org.apache.aries.blueprint.container.Parser.getNamespaceHandler(Parser.java:1253)
      at org.apache.aries.blueprint.container.Parser.parseCustomElement(Parser.java:1246)
      at org.apache.aries.blueprint.container.Parser.loadComponents(Parser.java:337)
      at org.apache.aries.blueprint.container.Parser.populate(Parser.java:277)
      at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:277)
      at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:227)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:452)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
      at java.util.concurrent.FutureTask.run(FutureTask.java:149)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:109)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:218)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
      at java.lang.Thread.run(Thread.java:736)
      2011-11-28 20:17:45,775 ERROR [BlueprintContainerImpl] Unable to start blueprint container for bundle org.apache.karaf.features.command
      org.osgi.service.blueprint.container.ComponentDefinitionException: Unsupported node namespace: http://karaf.apache.org/xmlns/shell/v1.0.0
      at org.apache.aries.blueprint.container.Parser.getNamespaceHandler(Parser.java:1262)
      at org.apache.aries.blueprint.container.Parser.getNamespaceHandler(Parser.java:1253)
      at org.apache.aries.blueprint.container.Parser.parseCustomElement(Parser.java:1246)
      at org.apache.aries.blueprint.container.Parser.loadComponents(Parser.java:337)
      at org.apache.aries.blueprint.container.Parser.populate(Parser.java:277)
      at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:277)
      at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:227)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:452)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
      at java.util.concurrent.FutureTask.run(FutureTask.java:149)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:109)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:218)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
      at java.lang.Thread.run(Thread.java:736)
      5.for linux x86_64, when executing step4, server can be stopped but displayed the info:
      Locating server on localhost:1099... Server found.
      Server shutdown started
      Server shutdown completed
      org.apache.karaf.features.core[org.apache.karaf.features.internal.FeaturesServiceImpl] : Error persisting FeaturesService state
      java.lang.IllegalStateException: BundleContext is no longer valid
      at org.eclipse.osgi.framework.internal.core.BundleContextImpl.checkValid(BundleContextImpl.java:931)
      at org.eclipse.osgi.framework.internal.core.BundleContextImpl.getDataFile(BundleContextImpl.java:664)
      at org.apache.karaf.features.internal.FeaturesServiceImpl.saveState(FeaturesServiceImpl.java:1042)
      at org.apache.karaf.features.internal.FeaturesServiceImpl$1.run(FeaturesServiceImpl.java:973)

        Activity

        Hide
        viola.lu added a comment -

        Can you stop server after confirming server is started completely? From the error log, it seems you stop server right after running start command, server may not be started completely.

        Show
        viola.lu added a comment - Can you stop server after confirming server is started completely? From the error log, it seems you stop server right after running start command, server may not be started completely.
        Hide
        Tina Li added a comment -

        Hi, Problem still happened for this condition:
        1. ceservice start
        2. ceservice stop
        3. ceservice start
        4. ceservice stop, then problem happened:
        2012-03-02 17:27:26,663 ERROR [FeaturesServiceImpl] Error persisting FeaturesService state
        java.lang.IllegalStateException: BundleContext is no longer valid
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.checkValid(BundleContextImpl.java:931)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.getDataFile(BundleContextImpl.java:664)
        at org.apache.karaf.features.internal.FeaturesServiceImpl.saveState(FeaturesServiceImpl.java:1042)
        at org.apache.karaf.features.internal.FeaturesServiceImpl$1.run(FeaturesServiceImpl.java:973)

        Show
        Tina Li added a comment - Hi, Problem still happened for this condition: 1. ceservice start 2. ceservice stop 3. ceservice start 4. ceservice stop, then problem happened: 2012-03-02 17:27:26,663 ERROR [FeaturesServiceImpl] Error persisting FeaturesService state java.lang.IllegalStateException: BundleContext is no longer valid at org.eclipse.osgi.framework.internal.core.BundleContextImpl.checkValid(BundleContextImpl.java:931) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.getDataFile(BundleContextImpl.java:664) at org.apache.karaf.features.internal.FeaturesServiceImpl.saveState(FeaturesServiceImpl.java:1042) at org.apache.karaf.features.internal.FeaturesServiceImpl$1.run(FeaturesServiceImpl.java:973)
        Hide
        Tina Li added a comment -

        Problem fixed and patch attached.

        Show
        Tina Li added a comment - Problem fixed and patch attached.
        Hide
        Tina Li added a comment -

        Patch is available,someone can help review and commit this patch? thanks in advance!

        Show
        Tina Li added a comment - Patch is available,someone can help review and commit this patch? thanks in advance!
        Hide
        Forrest Xia added a comment -

        3.0-beta@1296100

        Show
        Forrest Xia added a comment - 3.0-beta@1296100
        Hide
        Tina Li added a comment -

        Verified and closed it.

        Show
        Tina Li added a comment - Verified and closed it.

          People

          • Assignee:
            Tina Li
            Reporter:
            Tina Li
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development