Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-420

EARDeployer deploying EJBs not listed in application.xml

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • JBossAS-3.2.6 Final
    • None
    • None

    Description

      SourceForge Submitter: amayingenta .
      JBoss 3.2.0RC3, Solaris, Sun JDK1.3.1 & JDK1.4.1.

      EAR that deployed with 3.0.6 is failing in 3.2.0RC3.
      The EAR contains more EJBs than are currently listed in
      application.xml because we've disabled parts of the
      application until we fix them. However, in 3.2.0RC3 the
      EARDeployer is attempting to deploy all EJBs and WARs
      whether they're configured in application.xml or not.

      This is a portion of the server.log:

      2003-03-18 14:36:12,626 INFO
      [org.jboss.deployment.EARDeployer] Init J2EE
      application:
      file:/opt/isis/jboss/jboss-3.2.0RC3/server/ccsadm/deploy/isis.ear/
      2003-03-18 14:36:12,779 DEBUG
      [org.jboss.deployment.EARDeployer] Deployment Info:
      org.jboss.deployment.DeploymentInfo@73734565 {
      url=file:/opt/isis/jboss/jboss-
      3.2.0RC3/server/ccsadm/deploy/isis.ear/ejbs/statistics.jar
      }
      deployer: null
      status: null
      state: CONSTRUCTED
      watch:
      file:/opt/isis/jboss/jboss-3.2.0RC3/server/ccsadm/deploy/isis.ear/ejbs/statistics.jar
      lastDeployed: 0
      lastModified: 0
      mbeans:
      , isDirectory: false
      2003-03-18 14:36:12,780 DEBUG
      [org.jboss.deployment.EARDeployer] Deployment Info:
      org.jboss.deployment.DeploymentInfo@947e4d89

      { url=file:/opt/isis/jboss/jboss- 3.2.0RC3/server/ccsadm/deploy/isis.ear/ejbs/expander.jar }

      deployer: null
      status: null
      state: CONSTRUCTED
      watch:
      file:/opt/isis/jboss/jboss-3.2.0RC3/server/ccsadm/deploy/isis.ear/ejbs/expander.jar
      lastDeployed: 0
      lastModified: 0
      mbeans:
      , isDirectory: false

      One entry for each deployment listed in
      application.xml, including WARs, and then:

      2003-03-18 14:36:12,805 INFO
      [org.jboss.deployment.EARDeployer] looking for nested
      deployments in :
      file:/opt/isis/jboss/jboss-3.2.0RC3/server/ccsadm/deploy/is
      is.ear/
      2003-03-18 14:36:12,807 INFO
      [org.jboss.deployment.EARDeployer] nested deployment:
      file:/opt/isis/jboss/jboss-3.2.0RC3/server/ccsadm/deploy/isis.ear/ejbs/payme
      nt.jar
      2003-03-18 14:36:12,808 INFO
      [org.jboss.deployment.EARDeployer] nested deployment:
      file:/opt/isis/jboss/jboss-3.2.0RC3/server/ccsadm/deploy/isis.ear/ejbs/alert
      s.jar

      One entry for each jar or war within the EAR, including
      those not in application.xml, and then it goes on to
      deploy all of the EJBs.

      Attachments

        Activity

          People

            starksm64 Scott Stark (Inactive)
            sourceforge-user SourceForge legacy user (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: