6 Replies Latest reply on May 28, 2004 10:21 AM by tbauer

    Deployment errors when 2nd of 2 apps starts to deploy in /jb

    tbauer

      I have an appserver running 3.2.4RC2 (all config). If I only deploy 1 or my 2 applications, it works fine. But the minute I try to start the server that has two .ear files, the second one starts to throw very strange/bogus deployment errors.

      the errors are:
      Warning: The methods defined in the remote interface must have a matching method in the bean's class with the same name and same number and types of arguments.

      These errors cause deployment to fail...My remote interfaces ARE declared properly...

      BTW, these exact same applications deploy perfectly in 3.2.3Jetty

      Any clues from the genius bar????

      2004-05-26 20:40:06,660 INFO [org.jboss.ejb.EJBDeployer] Deployed: file:/Applications/jboss-3.2.4RC2/server/all/tmp/deploy/tmp38024asponline.ear-contents/asponline-ejb.jar
      2004-05-26 20:40:06,878 INFO [org.jboss.web.tomcat.tc5.TomcatDeployer] deploy, ctxPath=/asp, warUrl=file:/Applications/jboss-3.2.4RC2/server/all/tmp/deploy/tmp38024asponline.ear-c
      ontents/asponline-web.war/
      2004-05-26 20:40:07,013 DEBUG [tomcat.localhost./asp.Context] Starting tomcat.localhost./asp.Context
      2004-05-26 20:40:07,014 DEBUG [tomcat.localhost./asp.Context] Configuring default Resources
      2004-05-26 20:40:07,026 DEBUG [tomcat.localhost./asp.Context] Processing standard container startup
      2004-05-26 20:40:07,208 DEBUG [tomcat.localhost./asp.Context] Setting deployment descriptor public ID to '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN'
      2004-05-26 20:40:07,227 DEBUG [tomcat.localhost./asp.Context] Setting deployment descriptor public ID to '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN'
      2004-05-26 20:40:07,235 DEBUG [tomcat.localhost./asp.Context] Posting standard context attributes
      2004-05-26 20:40:07,236 DEBUG [tomcat.localhost./asp.Context] Configuring application event listeners
      2004-05-26 20:40:07,236 DEBUG [tomcat.localhost./asp.Context] Configuring event listener class 'com.cj.sessadm.admListener'
      2004-05-26 20:40:07,251 DEBUG [tomcat.localhost./asp.Context] Sending application start events
      2004-05-26 20:40:07,252 DEBUG [tomcat.localhost./asp.Context] Starting filters
      2004-05-26 20:40:07,253 DEBUG [tomcat.localhost./asp.Context] Starting completed
      2004-05-26 20:40:07,253 DEBUG [tomcat.localhost./asp.Context] Checking for jboss.web:j2eeType=WebModule,name=//localhost/asp,J2EEApplication=none,J2EEServer=none
      2004-05-26 20:40:07,323 INFO [org.jboss.deployment.EARDeployer] Started J2EE application: file:/Applications/jboss-3.2.4RC2/server/all/deploy/asponline.ear
      2004-05-26 20:40:07,433 INFO [org.jboss.deployment.EARDeployer] Init J2EE application: file:/Applications/jboss-3.2.4RC2/server/all/deploy/icsboomerang.ear
      2004-05-26 20:40:10,035 WARN [org.jboss.ejb.EJBDeployer.verifier] EJB spec violation:
      Bean : ShiftManagerBean
      Method : public abstract void removeShift(ShiftModel, boolean, int) throws RemoteException, FinderException
      Section: 7.10.5
      Warning: The methods defined in the remote interface must have a matching method in the bean's class with the same name and same number and types of arguments.

      2004-05-26 20:40:10,036 WARN [org.jboss.ejb.EJBDeployer.verifier] EJB spec violation:
      Bean : ShiftManagerBean
      Method : public abstract Integer createShift(ShiftModel, ICSRegSession) throws RemoteException, FinderException
      Section: 7.10.5
      Warning: The methods defined in the remote interface must have a matching method in the bean's class with the same name and same number and types of arguments.

        • 1. Re: Deployment errors when 2nd of 2 apps starts to deploy in
          tbauer

          This IS reproducable on my dev machine. Here's what else I found out...

          I have 2 application .ear files both in the server/all/deploy directory.
          The deployment happens by alpha, so asponline.ear deployed before icsboomerang.ear...and for some reason I get those bogus deployment errors when icsboomerang.ear tries to deploy.

          If I rename asponline.ear to x_asponline.ear, which enables icsboomerang.ear to deploy FIRST, then everything is fine and there are no deployment errors....If this is an configuration problem, then I need to learn that...otherwise, this is unacceptable...

          Any clues why this would happen??

          • 2. Re: Deployment errors when 2nd of 2 apps starts to deploy in
            starksm64

            Read about the default flat class loading model and how to isolate the deployment classes:

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

            • 3. Re: Deployment errors when 2nd of 2 apps starts to deploy in
              tbauer

              Thanks Scott...I think this is what I am looking for...will try it out when I get back to my dev machine...

              cheers,

              Tim

              • 4. Re: Deployment errors when 2nd of 2 apps starts to deploy in
                tbauer

                Well, as usual I spoke too soon..

                I followd the Isolation example on the URL given above.....

                In jboss.xml, for each application (just changed the name)

                <loader-repository>
                icsboomerang.com:loader=ICS_BIS
                </loader-repository>

                Get the same problem as before, except that I also get:

                16:10:08,412 WARN [DeploymentInfo] Only the root deployment can set the loader repository, ingoring config=LoaderRepositoryConfig(repositoryName: icsboomerang.com:loader=ICS_BIS, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: null, repositoryConfig: null)
                16:10:09,446 WARN [DeploymentInfo] Only the root deployment can set the loader repository, ingoring config=LoaderRepositoryConfig(repositoryName: icsboomerang.com:loader=ICS_BIS, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: null, repositoryConfig: null)

                • 5. Re: Deployment errors when 2nd of 2 apps starts to deploy in
                  starksm64

                  You cannot scope nested deployments. For an ear deployment, scoping may only be specified at the ear level via its META-INF/jboss-app.xml descriptor.

                  • 6. Re: Deployment errors when 2nd of 2 apps starts to deploy in
                    tbauer

                    Okay, I got that part with the EAR figured out, but what about a SAR. I have a schedulable MBean in a SAR that calls stateful session beans deployed in my EAR. I scoped the EAR with success, but when the SAR is deployed it throws errors because it can't find the home interface of the session bean...I did try putting a jboss-app.xml file in the META-INF directory of the SAR, but that did not work.

                    Any help would be appreciated...

                    Thanks so much...

                    tim