facebook

Upgrade to MyEclipse 3.8.2 from 2.x breaks deployment

💡
Our Forums Have Moved

For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub

  1. MyEclipse IDE
  2.  > 
  3. Installation, Configuration & Updates
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #220695 Reply

    nlecaros
    Member

    I have three projects:

    xyz-app: Enterprise Application Project
    xyz: Web Application Project
    xyz-ejb: EJB Project

    xyz-app contains xyz and xyz-ejb as modules. I deploy them as one .ear package, and under 2.x, this setup worked fine. When I installed MyEclipse 3.8.2, checked these three projects out of our CVS and attempted to redeploy, I get this exception on JBoss startup:

    ——— START ——-

    23:12:30,840 INFO [MainDeployer] Starting deployment of package: file:/C:/Tools/jboss-3.2.3/server/default/deploy/xyz-app.ear
    23:12:31,070 INFO [EARDeployer] Init J2EE application: file:/C:/Tools/jboss-3.2.3/server/default/deploy/xyz-app.ear
    23:12:33,273 ERROR [MainDeployer] Could not initialise deloyment: file:/C:/Tools/jboss-3.2.3/server/default/deploy/xyz-app.ear
    org.jboss.deployment.DeploymentException: Failed to find module file: hibernate2.jar
    at org.jboss.deployment.EARDeployer.init(EARDeployer.java:171)
    at org.jboss.deployment.MainDeployer.init(MainDeployer.java:696)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:632)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
    at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy6.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:302)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:476)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)
    at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
    at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:394)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy5.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
    at org.jboss.Main.boot(Main.java:150)
    at org.jboss.Main$1.run(Main.java:395)
    at java.lang.Thread.run(Thread.java:534)
    23:12:33,313 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation ‘checkIncompleteDeployments()’
    Cause: Incomplete Deployment listing:
    Packages waiting for a deployer:
    <none>
    Incompletely deployed packages:
    [org.jboss.deployment.DeploymentInfo@de4e5ee0 { url=file:/C:/Tools/jboss-3.2.3/server/default/deploy/xyz-app.ear }
    deployer: org.jboss.deployment.EARDeployer@1304043
    status: null
    state: FAILED
    watch: file:/C:/Tools/jboss-3.2.3/server/default/deploy/xyz-app.ear
    lastDeployed: 1102479153273
    lastModified: 1102479151070
    mbeans:
    ]MBeans waiting for classes:
    <none>
    MBeans waiting for other MBeans:
    <none>

    —— END ———

    When I examine the .ear file, the hibernate2.jar file is indeed missing. However, this jar file is present in the xyz-app project (I should also mention that xyz-app is nothing but a placeholder for all common jar files between its two modules).

    In both versions of MyEclipse, I deploy to the same JBoss 3.2.3 installation, so I’m fairly sure that the only difference is the Eclipse/MyEclipse installations.

    What could possibly have changed between these two releases to cause this? What can I do to get this working in 3.8.2?

    Thanks.

    #220710

    Riyad Kalla
    Member

    nlecaros,
    The first thing I would check is your deployment rules that you have setup. In the past you might have “deploy external libs” or “deploy dependent libs” setup to true, and now when you reinstalled these are set to false, so no dependent libraries are getting deployed and the EAR cannot be built.

    #220714

    nlecaros
    Member

    Hi Riyad,

    Thanks for the quick reply. I checked my workspace settings under Window->Preferences->MyEclipse->J2EE Project->Web Project Deployment and they are all set to always deploy dependent projects and libraries, and the hibernate2.jar still doesn’t get packaged.

    The strange part is that hibernate2.jar isn’t the only jar file in the xyz-app directory, but all the other jar files make it into the .ear file. Is there anything else I need to look at?

    Thanks.

    Noel

    #220716

    Riyad Kalla
    Member

    Noel,
    Very strange… open up your xyz-app, go to Java Build Path > Libraries tab… is there anything different about the hibernate2.jar file? Does it have an error or warning marker on it? Try removing it and readding it… is this JAR any different than the others or are they all part of the xyz-app? It is not an external lib right? (I’m guessing you added Hibernate caps to this project and just had all the JARs added to the build path or something like that).

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Upgrade to MyEclipse 3.8.2 from 2.x breaks deployment

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