2 Replies Latest reply on Jun 30, 2005 1:42 PM by Murtuza Vohra

    Failed to find .par module

    Murtuza Vohra Newbie

      I am testing code from the Relation Tutorial and i have following setup
      Windows XP Pro
      MyEclipse 3.8.4
      Eclipse 3.1M6
      JBoss 4.0.2 with EJB Beta 1

      I have complete application and .ejb3 and .par gets deployed find and when it comes to .ear deployment it thorws following error (here is a clip of it)

      17:24:33,260 INFO [Ejb3Module] Create EntityManager with JNDI name: manager1
      17:24:33,270 INFO [JaccHelper] JACC Policy Configuration for deployment has been put in service
      17:24:33,270 INFO [Ejb3Module] EJB3 deployment time took: 9594
      17:24:34,301 INFO [ProxyDeployer] no declared remote bindings
      17:24:34,321 INFO [ProxyDeployer] there is remote interfaces
      17:24:34,331 INFO [ProxyDeployer] default remote binding has jndiName of com.kt.inventory.session.entity.InventoryManager
      17:24:34,712 INFO [ProxyDeployer] no declared remote bindings
      17:24:34,712 INFO [ProxyDeployer] there is remote interfaces
      17:24:34,712 INFO [ProxyDeployer] default remote binding has jndiName of com.kt.order.session.bean.OrderManager
      17:24:34,752 INFO [EJB3Deployer] Deployed: file:/C:/jboss-4.0.2/server/all/deploy/emanager.par
      17:24:35,002 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/C:/jboss-4.0.2/server/all/deploy/jmx-console.war/
      17:24:35,563 INFO [EARDeployer] Init J2EE application: file:/C:/jboss-4.0.2/server/all/deploy/ktee.ear
      17:24:35,653 ERROR [MainDeployer] Could not initialise deployment: file:/C:/jboss-4.0.2/server/all/deploy/ktee.ear
      org.jboss.deployment.DeploymentException: Failed to find module file: emanager.par
       at org.jboss.deployment.EARDeployer.init(EARDeployer.java:244)
       at org.jboss.deployment.MainDeployer.init(MainDeployer.java:828)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:765)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
       at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
       at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
       at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
       at $Proxy8.deploy(Unknown Source)
       at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325)
       at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:501)
       at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
       at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
       at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
       at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897)
       at $Proxy0.start(Unknown Source)
       at org.jboss.system.ServiceController.start(ServiceController.java:418)
       at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
       at $Proxy4.start(Unknown Source)
       at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
       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:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
       at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
       at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
       at $Proxy5.deploy(Unknown Source)
       at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:434)
       at org.jboss.system.server.ServerImpl.start(ServerImpl.java:315)
       at org.jboss.Main.boot(Main.java:195)
       at org.jboss.Main$1.run(Main.java:463)
       at java.lang.Thread.run(Thread.java:595)
      17:24:37,606 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
      
      --- Incompletely deployed packages ---
      org.jboss.deployment.DeploymentInfo@61de1bae { url=file:/C:/jboss-4.0.2/server/all/deploy/ktee.ear }
       deployer: org.jboss.deployment.EARDeployer@169c398
       status: null
       state: FAILED
       watch: file:/C:/jboss-4.0.2/server/all/deploy/ktee.ear
       altDD: null
       lastDeployed: 1120141475653
       lastModified: 1120141475563
       mbeans:
      
      
      17:24:37,967 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
      17:24:38,538 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
      17:24:38,658 INFO [JkMain] Jk running ID=0 time=0/211 config=null
      17:24:38,748 INFO [Server] JBoss (MX MicroKernel) [4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)] Started in 2m:31s:939ms



      As one can see emanager.par and smanager.ejb3 get deployed find but ktee.ear throws "Failed to find module file: emanager.par" error.

      My application.xml is as follows:

      <?xml version="1.0" encoding="UTF-8"?>
      <!DOCTYPE application PUBLIC
       "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
       "http://java.sun.com/dtd/application_1_3.dtd">
      
      <application>
       <display-name>Keep Track Enterprise Edition</display-name>
      
       <module>
       <ejb>emanager.par</ejb>
       </module>
       <module>
       <ejb>smanager.ejb3</ejb>
       </module>
      </application>



      and persistence.xml is as follows:

      <?xml version="1.0" encoding="UTF-8"?>
      <entity-manager>
       <name>manager1</name>
       <jta-data-source>java:/MySqlDS</jta-data-source>
       <properties>
       <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
       <property name="hibernate.hbm2ddl.auto" value="update"/>
       </properties>
      </entity-manager>


      The eclipse pacaking script which is generated using eclipse GUI is as follows:
      <?xml version="1.0" encoding="UTF-8"?>
      <project name="Packaging Generator" default="_packaging_generation_">
      <target name="_packaging_generation_" depends="N65540,N65565,N65582"/>
      <target name="N65540" description="emanager.par">
      <jar destfile="emanager.par">
      <zipfileset dir="bin" prefix="META-INF">
      <include name="persistence.xml"/>
      </zipfileset>
      <zipfileset dir="bin" excludes="**/*Manager*.java"/>
      </jar>
      </target>
      <target name="N65565" description="smanager.ejb3">
      <jar destfile="smanager.ejb3">
      <zipfileset dir="bin" includes="**/*Manager*.java"/>
      </jar>
      </target>
      <target name="N65582" description="ktee.ear">
      <jar destfile="ktee.ear">
      <zipfileset dir="bin" prefix="META-INF">
      <include name="application.xml"/>
      </zipfileset>
      </jar>
      </target>
      </project>
      
      


      I'll appreciate if anyone can show me what is wrong with the code.

      Thanks
      Murtuza


        • 1. Re: Failed to find .par module
          Bill Burke Master

          recheck your packaging as there is a tutorial example of an ear with a .par and .ejb3 within it.

          • 2. Re: Failed to find .par module
            Murtuza Vohra Newbie

            Excellent, works perfect

            also i noticed that .par and .ejb3 were not packaged corrected, here is the revised build script. The difference is it must include class file and not .java file for build process.

            <?xml version="1.0" encoding="UTF-8"?>
            <project name="Packaging Generator" default="_packaging_generation_">
            <target name="_packaging_generation_" depends="N65540,N65565,N65582"/>
            <target name="N65540" description="emanager.par">
            <jar destfile="emanager.par">
            <zipfileset dir="bin" prefix="META-INF">
            <include name="persistence.xml"/>
            </zipfileset>
            <zipfileset dir="bin" excludes="**/*Manager*.class"/>
            </jar>
            </target>
            <target name="N65565" description="smanager.ejb3">
            <jar destfile="smanager.ejb3">
            <zipfileset dir="bin" includes="**/*Manager*.class"/>
            </jar>
            </target>
            <target name="N65582" description="ktee.ear">
            <jar destfile="ktee.ear">
            <zipfileset dir="bin" prefix="META-INF">
            <include name="application.xml"/>
            </zipfileset>
            </jar>
            </target>
            </project>