javax.servlet.ServletException: Bundle context attribute [org.osgi.framework.BundleContext] not set in servlet context

Pentaho BI Platform Tracking | João Pereira | 11 months ago
  1. 0

    When executing DI-Server 6.0 GA on JBoss EAP 6.4, we are not able to properly initialize karaf. Karaf does tries to initialize but it shutdowns right after. Moreover, when trying to shutdown DI-Server it gets blocked. I get these errors on the logs: {noformat} [org.pentaho.di.osgi.KarafLifecycleListener] (KarafLifecycleListner Timeout Thread) The Kettle Karaf Lifycycle Listener failed to execute properly. Releasing lifecycle hold, but some services may be unavailable. {noformat} {noformat} ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/pentaho-di]] (ServerService Thread Pool -- 72) JBWEB000289: Servlet proxy threw load() exception: javax.servlet.ServletException: Bundle context attribute [org.osgi.framework.BundleContext] not set in servlet context at org.apache.felix.http.proxy.ProxyServlet.getBundleContext(ProxyServlet.java:81) [org.apache.felix.http.proxy-2.3.0.jar:2.3.0] at org.apache.felix.http.proxy.ProxyServlet.doInit(ProxyServlet.java:50) [org.apache.felix.http.proxy-2.3.0.jar:2.3.0] at org.apache.felix.http.proxy.ProxyServlet.init(ProxyServlet.java:39) [org.apache.felix.http.proxy-2.3.0.jar:2.3.0] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3593) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3802) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_79] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_79] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79] at org.jboss.threads.JBossThread.run(JBossThread.java:122) {noformat} {noformat} ERROR [org.pentaho.di.osgi.KarafLifecycleListener] (Thread-131) Error in Feature Watcher: org.pentaho.osgi.api.IKarafFeatureWatcher$FeatureWatcherException: Unknown error in KarafWatcher at org.pentaho.osgi.impl.KarafFeatureWatcherImpl.waitForFeatures(KarafFeatureWatcherImpl.java:130) at org.pentaho.di.osgi.KarafLifecycleListener$2.run(KarafLifecycleListener.java:95) [pdi-osgi-bridge-core-6.0.0.0-353.jar:6.0.0.0-353] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79] Caused by: org.pentaho.osgi.api.IKarafFeatureWatcher$FeatureWatcherException: Timed out waiting for Karaf features to install: config,management,kar,ssh,cxf,camel,camel-blueprint,camel-stream,pentaho-camel-jms,pentaho-server,mongolap,pentaho-monitoring-to-snmp,pentaho-monitoring-jms-broker,pentaho-metaverse,pdi-dataservice,pentaho-yarn-obf,pentaho-marketplace at org.pentaho.osgi.impl.KarafFeatureWatcherImpl.waitForFeatures(KarafFeatureWatcherImpl.java:116) ... 2 more ERROR [org.pentaho.di.osgi.KarafLifecycleListener] (Thread-131) Error in Blueprint Watcher: org.pentaho.osgi.api.IKarafBlueprintWatcher$BlueprintWatcherException: Unknown error in KarafBlueprintWatcher at org.pentaho.osgi.impl.KarafBlueprintWatcherImpl.waitForBlueprint(KarafBlueprintWatcherImpl.java:89) at org.pentaho.di.osgi.KarafLifecycleListener$2.run(KarafLifecycleListener.java:112) [pdi-osgi-bridge-core-6.0.0.0-353.jar:6.0.0.0-353] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79] Caused by: org.pentaho.osgi.api.IKarafBlueprintWatcher$BlueprintWatcherException: Timed out waiting for blueprints to load: pdi-dataservice-server-plugin,pentaho-big-data-impl-shim-initializer,pentaho-big-data-impl-shim-hdfs,pentaho-big-data-impl-shim-pig,pentaho-big-data-impl-vfs-hdfs,pentaho-big-data-kettle-plugins-common-named-cluster-bridge,pentaho-big-data-kettle-plugins-guiTestActionHandlers,pentaho-big-data-kettle-plugins-pig,pentaho-hadoop-shims-mapr-osgi-jaas,pentaho-big-data-impl-clusterTests,pentaho-big-data-impl-shim-shimTests,pentaho-blueprint-activators-6.0.0.0,pentaho-ss4-proxies,pentaho-ss2-proxies,pentaho-proxy-spring4,pentaho-requirejs-osgi-manager,pentaho-blueprint-activators-6.0.0.0,pentaho-angular-bundle,mondrian,org.apache.cxf.karaf.cxf-karaf-commands,org.apache.karaf.management.server,org.apache.karaf.config.core,org.apache.karaf.config.command,pentaho-marketplace-ba,pentaho-yarn-api,pentaho-yarn-impl-shim,pentaho-yarn-kettle-plugin,pentaho-monitoring-plugin,pentaho-camel-snmp,pentaho-blueprint-activators-6.0.0.0,org.apache.karaf.shell.ssh,pentaho-metaverse-core,pentaho-blueprint-activators-6.0.0.0 at org.pentaho.osgi.impl.KarafBlueprintWatcherImpl.waitForBlueprint(KarafBlueprintWatcherImpl.java:77) ... 2 more {noformat} Until now, I have identified a set of bundles from features: pentaho-big-data-plugin-osgi, pentaho-big-data-plugin-testless-osgi, and pentaho-yarn-obf that block karaf and if removed they allow karaf to initialize. The bundles that prevent karaf from properly initializing on jboss are: - mvn:pentaho/pentaho-yarn-impl-shim/6.0.0.0-353/jar/obf - mvn:pentaho/pentaho-big-data-impl-shim-shimTests/6.0.0.0-353 - mvn:pentaho/pentaho-big-data-impl-shim-initializer/6.0.0.0-353 - mvn:pentaho/pentaho-big-data-impl-shim-hdfs/6.0.0.0-353 - mvn:pentaho/pentaho-big-data-impl-shim-pig/6.0.0.0-353 - mvn:pentaho/pentaho-big-data-kettle-plugins-common-named-cluster-bridge/6.0.0.0-353 - mvn:pentaho/pentaho-hadoop-shims-mapr-osgi-jaas/6.0.0.0-353

    Pentaho BI Platform Tracking | 11 months ago | João Pereira
    javax.servlet.ServletException: Bundle context attribute [org.osgi.framework.BundleContext] not set in servlet context
  2. 0

    When executing DI-Server 6.0 GA on JBoss EAP 6.4, we are not able to properly initialize karaf. Karaf does tries to initialize but it shutdowns right after. Moreover, when trying to shutdown DI-Server it gets blocked. I get these errors on the logs: {noformat} [org.pentaho.di.osgi.KarafLifecycleListener] (KarafLifecycleListner Timeout Thread) The Kettle Karaf Lifycycle Listener failed to execute properly. Releasing lifecycle hold, but some services may be unavailable. {noformat} {noformat} ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/pentaho-di]] (ServerService Thread Pool -- 72) JBWEB000289: Servlet proxy threw load() exception: javax.servlet.ServletException: Bundle context attribute [org.osgi.framework.BundleContext] not set in servlet context at org.apache.felix.http.proxy.ProxyServlet.getBundleContext(ProxyServlet.java:81) [org.apache.felix.http.proxy-2.3.0.jar:2.3.0] at org.apache.felix.http.proxy.ProxyServlet.doInit(ProxyServlet.java:50) [org.apache.felix.http.proxy-2.3.0.jar:2.3.0] at org.apache.felix.http.proxy.ProxyServlet.init(ProxyServlet.java:39) [org.apache.felix.http.proxy-2.3.0.jar:2.3.0] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3593) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3802) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_79] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_79] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79] at org.jboss.threads.JBossThread.run(JBossThread.java:122) {noformat} {noformat} ERROR [org.pentaho.di.osgi.KarafLifecycleListener] (Thread-131) Error in Feature Watcher: org.pentaho.osgi.api.IKarafFeatureWatcher$FeatureWatcherException: Unknown error in KarafWatcher at org.pentaho.osgi.impl.KarafFeatureWatcherImpl.waitForFeatures(KarafFeatureWatcherImpl.java:130) at org.pentaho.di.osgi.KarafLifecycleListener$2.run(KarafLifecycleListener.java:95) [pdi-osgi-bridge-core-6.0.0.0-353.jar:6.0.0.0-353] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79] Caused by: org.pentaho.osgi.api.IKarafFeatureWatcher$FeatureWatcherException: Timed out waiting for Karaf features to install: config,management,kar,ssh,cxf,camel,camel-blueprint,camel-stream,pentaho-camel-jms,pentaho-server,mongolap,pentaho-monitoring-to-snmp,pentaho-monitoring-jms-broker,pentaho-metaverse,pdi-dataservice,pentaho-yarn-obf,pentaho-marketplace at org.pentaho.osgi.impl.KarafFeatureWatcherImpl.waitForFeatures(KarafFeatureWatcherImpl.java:116) ... 2 more ERROR [org.pentaho.di.osgi.KarafLifecycleListener] (Thread-131) Error in Blueprint Watcher: org.pentaho.osgi.api.IKarafBlueprintWatcher$BlueprintWatcherException: Unknown error in KarafBlueprintWatcher at org.pentaho.osgi.impl.KarafBlueprintWatcherImpl.waitForBlueprint(KarafBlueprintWatcherImpl.java:89) at org.pentaho.di.osgi.KarafLifecycleListener$2.run(KarafLifecycleListener.java:112) [pdi-osgi-bridge-core-6.0.0.0-353.jar:6.0.0.0-353] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79] Caused by: org.pentaho.osgi.api.IKarafBlueprintWatcher$BlueprintWatcherException: Timed out waiting for blueprints to load: pdi-dataservice-server-plugin,pentaho-big-data-impl-shim-initializer,pentaho-big-data-impl-shim-hdfs,pentaho-big-data-impl-shim-pig,pentaho-big-data-impl-vfs-hdfs,pentaho-big-data-kettle-plugins-common-named-cluster-bridge,pentaho-big-data-kettle-plugins-guiTestActionHandlers,pentaho-big-data-kettle-plugins-pig,pentaho-hadoop-shims-mapr-osgi-jaas,pentaho-big-data-impl-clusterTests,pentaho-big-data-impl-shim-shimTests,pentaho-blueprint-activators-6.0.0.0,pentaho-ss4-proxies,pentaho-ss2-proxies,pentaho-proxy-spring4,pentaho-requirejs-osgi-manager,pentaho-blueprint-activators-6.0.0.0,pentaho-angular-bundle,mondrian,org.apache.cxf.karaf.cxf-karaf-commands,org.apache.karaf.management.server,org.apache.karaf.config.core,org.apache.karaf.config.command,pentaho-marketplace-ba,pentaho-yarn-api,pentaho-yarn-impl-shim,pentaho-yarn-kettle-plugin,pentaho-monitoring-plugin,pentaho-camel-snmp,pentaho-blueprint-activators-6.0.0.0,org.apache.karaf.shell.ssh,pentaho-metaverse-core,pentaho-blueprint-activators-6.0.0.0 at org.pentaho.osgi.impl.KarafBlueprintWatcherImpl.waitForBlueprint(KarafBlueprintWatcherImpl.java:77) ... 2 more {noformat} Until now, I have identified a set of bundles from features: pentaho-big-data-plugin-osgi, pentaho-big-data-plugin-testless-osgi, and pentaho-yarn-obf that block karaf and if removed they allow karaf to initialize. The bundles that prevent karaf from properly initializing on jboss are: - mvn:pentaho/pentaho-yarn-impl-shim/6.0.0.0-353/jar/obf - mvn:pentaho/pentaho-big-data-impl-shim-shimTests/6.0.0.0-353 - mvn:pentaho/pentaho-big-data-impl-shim-initializer/6.0.0.0-353 - mvn:pentaho/pentaho-big-data-impl-shim-hdfs/6.0.0.0-353 - mvn:pentaho/pentaho-big-data-impl-shim-pig/6.0.0.0-353 - mvn:pentaho/pentaho-big-data-kettle-plugins-common-named-cluster-bridge/6.0.0.0-353 - mvn:pentaho/pentaho-hadoop-shims-mapr-osgi-jaas/6.0.0.0-353

    Pentaho BI Platform Tracking | 11 months ago | João Pereira
    javax.servlet.ServletException: Bundle context attribute [org.osgi.framework.BundleContext] not set in servlet context
  3. 0

    Following instructions for manual deployment of Pentaho-Server 7 to a JBoss EAP 6.4 with PostgreSQL as the backend and the server.log will show the following exception {noformat} 15:54:15,813 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/pentaho]] (ServerService Thread Pool -- 86) JBWEB000289: Servlet proxy threw load() exception: javax.servlet.ServletException: Bundle context attribute [org.osgi.framework.BundleContext] not set in servlet context at org.apache.felix.http.proxy.ProxyServlet.getBundleContext(ProxyServlet.java:81) [org.apache.felix.http.proxy-2.3.0.jar:2.3.0] at org.apache.felix.http.proxy.ProxyServlet.doInit(ProxyServlet.java:50) [org.apache.felix.http.proxy-2.3.0.jar:2.3.0] at org.apache.felix.http.proxy.ProxyServlet.init(ProxyServlet.java:39) [org.apache.felix.http.proxy-2.3.0.jar:2.3.0] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3593) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3802) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [rt.jar:1.8.0_111] at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.8.0_111] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.8.0_111] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.8.0_111] at java.lang.Thread.run(Unknown Source) [rt.jar:1.8.0_111] at org.jboss.threads.JBossThread.run(JBossThread.java:122) {noformat}

    Pentaho BI Platform Tracking | 3 weeks ago | Carlos Lopez
    javax.servlet.ServletException: Bundle context attribute [org.osgi.framework.BundleContext] not set in servlet context
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Plugin tutorial - Jenkins - Jenkins Wiki

    jenkins-ci.org | 6 months ago
    javax.servlet.ServletException: there's no "app" attribute in the application context.
  6. 0

    Re: Error running hudson: no "app" attribute - Marc-Andre Houle - net.java.dev.hudson.dev - MarkMail

    markmail.org | 8 months ago
    javax.servlet.ServletException: there's no "app" attribute in the application context.

    1 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. javax.servlet.ServletException

      Bundle context attribute [org.osgi.framework.BundleContext] not set in servlet context

      at org.apache.felix.http.proxy.ProxyServlet.getBundleContext()
    2. Apache Felix Http Proxy
      ProxyServlet.init
      1. org.apache.felix.http.proxy.ProxyServlet.getBundleContext(ProxyServlet.java:81)[org.apache.felix.http.proxy-2.3.0.jar:2.3.0]
      2. org.apache.felix.http.proxy.ProxyServlet.doInit(ProxyServlet.java:50)[org.apache.felix.http.proxy-2.3.0.jar:2.3.0]
      3. org.apache.felix.http.proxy.ProxyServlet.init(ProxyServlet.java:39)[org.apache.felix.http.proxy-2.3.0.jar:2.3.0]
      3 frames
    3. Glassfish Core
      StandardContext.start
      1. org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194)[jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
      2. org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100)[jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
      3. org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3593)[jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
      4. org.apache.catalina.core.StandardContext.start(StandardContext.java:3802)[jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
      4 frames
    4. JBoss Web
      WebDeploymentService$1.run
      1. org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163)[jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
      2. org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61)[jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
      3. org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96)[jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
      3 frames
    5. Java RT
      Thread.run
      1. java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[rt.jar:1.7.0_79]
      2. java.util.concurrent.FutureTask.run(FutureTask.java:262)[rt.jar:1.7.0_79]
      3. java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[rt.jar:1.7.0_79]
      4. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[rt.jar:1.7.0_79]
      5. java.lang.Thread.run(Thread.java:745)[rt.jar:1.7.0_79]
      5 frames
    6. JBoss Threads
      JBossThread.run
      1. org.jboss.threads.JBossThread.run(JBossThread.java:122)
      1 frame