• Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.0.0.Final, 7.0.1.Final
    • Fix Version/s: 7.1.0.Beta1
    • Component/s: OSGi, Web
    • Labels:
    • Environment:

      Mac OS X 10.7 (Lion)


      Impossible to deploy OSGi war bundle. The same war bundle deploys perfectly in eclipse Virgo server. I get the following when I try to deploy my war:

      14:37:46,065 INFO [] (MSC service thread 1-12) Starting deployment of "inputstream:aps-admin-web-1.0.0.war"
      14:37:47,129 INFO [] (MSC service thread 1-5) added javax.persistence.api dependency to inputstream:aps-admin-web-1.0.0.war
      14:37:47,131 ERROR [] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."inputstream:aps-admin-web-1.0.0.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."inputstream:aps-admin-web-1.0.0.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "inputstream:aps-admin-web-1.0.0.war"
      at org.jboss.msc.service.ServiceControllerImpl$
      at org.jboss.msc.service.ServiceControllerImpl$
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( [:1.6.0_26]
      at java.util.concurrent.ThreadPoolExecutor$ [:1.6.0_26]
      at [:1.6.0_26]
      Caused by: java.lang.NullPointerException
      ... 5 more

      14:37:47,134 INFO [] (pool-3-thread-1) Deployment of "inputstream:aps-admin-web-1.0.0.war" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.\"inputstream:aps-admin-web-1.0.0.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"inputstream:aps-admin-web-1.0.0.war\".POST_MODULE: Failed to process phase POST_MODULE of deployment \"inputstream:aps-admin-web-1.0.0.war\""}}
      14:37:47,143 INFO [] (MSC service thread 1-9) Stopped deployment inputstream:aps-admin-web-1.0.0.war in 8ms
      14:37:47,147 WARN [/] (Background Install /var/folders/3l/2n_xhr7s6ksc_bddrvl1hthm0000gn/T/install6377037636958039788.tmp) %bundles.pluginTitle: Cannot install or update bundle from /var/folders/3l/2n_xhr7s6ksc_bddrvl1hthm0000gn/T/install6377037636958039788.tmp: org.osgi.framework.BundleException: Cannot deploy bundle: [aps-admin-web:1.0.0,location=inputstream:aps-admin-web-1.0.0.war]
      at org.jboss.osgi.framework.internal.AbstractBundleContext.installBundle(
      at org.jboss.osgi.framework.internal.AbstractBundleContext.installBundleInternal(
      at org.jboss.osgi.framework.internal.AbstractBundleContext.installBundle(
      at org.apache.felix.webconsole.internal.core.InstallHelper.doRun( [InstallHelper.class:]
      at org.apache.felix.webconsole.internal.core.BaseUpdateInstallHelper.doRun( [BaseUpdateInstallHelper.class:]
      at [BaseUpdateInstallHelper.class:]
      at [:1.6.0_26]
      Caused by: java.lang.Exception: {"Failed services" => {"jboss.deployment.unit.\"inputstream:aps-admin-web-1.0.0.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"inputstream:aps-admin-web-1.0.0.war\".POST_MODULE: Failed to process phase POST_MODULE of deployment \"inputstream:aps-admin-web-1.0.0.war\""}}
      ... 7 more

      The bundle manifest looks like this:
      Manifest-Version: 1.0
      Embed-Directory: lib
      Bundle-ClassPath: WEB-INF/classes
      Built-By: tommy
      Tool: Bnd-1.43.0
      Bundle-Name: APS Administration Web
      Created-By: Apache Maven Bundle Plugin
      Web-ContextPath: apsadminweb
      Build-Jdk: 1.6.0_26
      Bundle-Version: 1.0.0
      Bnd-LastModified: 1313841491925
      Bundle-ManifestVersion: 2
      Bundle-Activator: osgi.aps.apsadminweb.APSAdminWebActivator
      Bundle-Description: APS Administration Web
      Bundle-SymbolicName: aps-admin-web
      Import-Package: org.osgi.framework;version="[1.5,2)",org.osgi.service.
      Embed-Dependency: *;scope=compile

      All that is included in the war in addition to the activator is and index.jsp that looks like this:
      <%@page contentType="text/html" pageEncoding="UTF-8"%>
      <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>JSP Page</title>
      <h1>Hello World!</h1>

      In other words, this is an extremely simple war bundle that I made for testing war bundle deploy. The activator does nothing yet. It has empty start(...) and stop(...) methods. Therefore I find the following line from the stack trace above interesting:

      It is a simple war with a single jsp page, so why is it trying to do ejb3 depployment ? And also it is not the full server I'm running, only the web profile, which as far as I know should not contain ejb3.

      All I have done in the configuration (standalone) is to change start level from 1 to 3, and change osgi from lazy to eager.

      As I said above this war file deploys perfectly in the Virgo server and I can bring up http://localhost:8080/apsadminweb in the browser and get the "Hello World!". Thereby I feel that my simple war is correct.

      As another test I tried to deploy one of the war bundles that came with the Virgo server and it resulted in exactly the same stack trace as above.

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  thomas.diesler Thomas Diesler
                  tommybs Tommy Svensson
                • Votes:
                  3 Vote for this issue
                  7 Start watching this issue


                  • Created: