facebook

JBoss 4.2.2 Exploded Deployment Issue

  1. MyEclipse Archived
  2.  > 
  3. Application Servers and Deployment
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #280729 Reply

    jebscar
    Member

    When we try to deploy as exploded we get a bunch of errors similar to the follow when starting the server. An packaged archive works without issue.

    --- Packages waiting for a deployer ---
    org.jboss.deployment.DeploymentInfo@28d20c2a { url=file:/C:/jboss-4.2.2.GA/server/default/deploy/web/META-INF/MANIFEST.MF }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/C:/jboss-4.2.2.GA/server/default/deploy/web/META-INF/MANIFEST.MF
      altDD: null
      lastDeployed: 1200435564199
      lastModified: 1200435564199
      mbeans:
    
    org.jboss.deployment.DeploymentInfo@fd54f173 { url=file:/C:/jboss-4.2.2.GA/server/default/deploy/web/resources/yui/button/assets/skins/sam/button.css }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/C:/jboss-4.2.2.GA/server/default/deploy/web/resources/yui/button/assets/skins/sam/button.css
      altDD: null
      lastDeployed: 1200435565688
      lastModified: 1200435565687
      mbeans:
    
    org.jboss.deployment.DeploymentInfo@dfa4b434 { url=file:/C:/jboss-4.2.2.GA/server/default/deploy/web/resources/yui/button/assets/skins/sam/menu-button-arrow-disabled.png }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/C:/jboss-4.2.2.GA/server/default/deploy/web/resources/yui/button/assets/skins/sam/menu-button-arrow-disabled.png
      altDD: null
      lastDeployed: 1200435565691
      lastModified: 1200435565691
      mbeans:
    #280747 Reply

    Loyal Water
    Member

    jebscar,
    Can you go to MyEclipse > Installation Summary > Installation Details and paste the information here for me.

    Are there any errors recorded under <workspace>/.metadata/.log file ?

    #280752 Reply

    jebscar
    Member

    No errors in <workspace>/.metadata/.log file. Installation details below.

    *** Date:
    Wednesday, January 16, 2008 9:29:29 AM EST

    ** System properties:
    OS=WindowsVista
    OS version=6.0
    Java version=1.5.0_11

    *** MyEclipse details:
    MyEclipse Enterprise Workbench
    Version: 6.0.1 GA
    Build id: 6.0.1-GA-200710

    *** Eclipse details:
    MyEclipse Enterprise Workbench

    Version: 6.0.1 GA
    Build id: 6.0.1-GA-200710

    Eclipse Platform

    Version: 3.3.2.R33x_v20071022-_19UEksF-G8Yc6bUv3Dz
    Build id: M20071023-1652

    Eclipse Java Development Tools

    Version: 3.3.1.r331_v20070629-7o7jE72EDlXAbqAcnbmyg1rf8RIL
    Build id: M20070921-1145

    Eclipse Project SDK

    Version: 3.3.2.R33x_r20071022-7M7J7C_Mu2gop0b_GAwplOBhyuKO
    Build id: M20071023-1652

    Eclipse RCP

    Version: 3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS
    Build id: M20070921-1145

    Eclipse Plug-in Development Environment

    Version: 3.3.2.R33x_r20071022-7N7M4CYWLBCz-yHkMIuHN
    Build id: M20070921-1145

    Eclipse Graphical Editing Framework

    Version: 3.3.1.v20070814
    Build id: 20070814-1555

    Eclipse startup command=-os
    win32
    -ws
    win32
    -arch
    x86
    -showsplash
    -launcher
    C:\MyEclipse601\eclipse\eclipse.exe
    -name
    Eclipse
    –launcher.library
    C:\MyEclipse601\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.2.R331_v20071019\eclipse_1021.dll
    -startup
    C:\MyEclipse601\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar
    -exitdata
    1710_64
    -vm
    C:\MyEclipse601\jre\bin\javaw.exe

    #280753 Reply

    jebscar
    Member

    a little more detail.. below is the exception that is getting thrown when the server starts up.

    09:26:10,707 WARN [JARDeployer] Failed to add deployable jar: file:/C:/jboss-4.2.2.GA/server/default/tmp/deploy/tmp14970README
    java.util.zip.ZipException: error in opening zip file
    at java.util.zip.ZipFile.open(Native Method)
    at java.util.zip.ZipFile.<init>(Unknown Source)
    at java.util.jar.JarFile.<init>(Unknown Source)
    at java.util.jar.JarFile.<init>(Unknown Source)
    at org.jboss.deployment.SubDeployerSupport.processNestedDeployments(SubDeployerSupport.java:377)
    at org.jboss.deployment.SubDeployerSupport.init(SubDeployerSupport.java:284)
    at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy9.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy5.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
    at org.jboss.Main.boot(Main.java:200)
    at org.jboss.Main$1.run(Main.java:508)
    at java.lang.Thread.run(Unknown Source)

    #280769 Reply

    jebscar
    Member

    The name of my project in myeclipse is “web”. It appears that the application is getting exploded in the jboss deploy directory as /web. According to the Jboss documentation it should be a in a directory named web.war.

    When I manually change the directory from application directory from web to web.war the server starts normally and the application can be accessed.

    {$JBOSS_HOME}/server/default/deploy/web – does NOT work
    {$JBOSS_HOME}/server/default/deploy/web.war – does work

    http://www.jboss.org/wiki/Wiki.jsp?page=ExplodedDeployment

    #280786 Reply

    jebscar
    Member

    renaming my project in myeclipse from web to web.war resulted in the application getting deployed into a web.war folder. this allowed Jboss to work correctly.

    #280789 Reply

    Loyal Water
    Member

    Thats wierd. Can you switch to a new workspace, create a new project and try deploying it to your server without adding the .war extension. Does it work ?

    #280794 Reply

    jebscar
    Member

    we have another project named web_admin. it deployed correctly the the web_admin.war directory in the JBoss deploy directory.

    #280812 Reply

    jebscar
    Member

    originally the ‘web’ project was deployed under the embedded tomcat then later changed to Jboss. it almost seems like it did not change the deployed directory from ‘web’ under tomat to ‘web.war’ under jboss. I have not have time to test this very much though.

    #280854 Reply

    Loyal Water
    Member

    This issue is project related. I would suggest you create a new project and transfer your code to the new project when ever you get time and continue working. That should sort this issue out.

Viewing 10 posts - 1 through 10 (of 10 total)
Reply To: JBoss 4.2.2 Exploded Deployment Issue

You must be logged in to post in the forum log in