Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-3625

Inconsistent deployment status when deploy an EJB containing wrong dependencies

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 8.1.0.Final
    • Web Console
    • None
    • Hide

      Steps to Reproduce:

      1) Start up vanilla installed WildFly 8.1.0 Final(standalone-full.xml), drop the folder dsc.ear into $JBOSS_HOME/standalone/deployments, then create an empty file "dsc.ear.dodeploy"

      2) JBoss starts to deploy, and had some error printed in server.log

      3) Checking http://localhost:9990, Runtime - Server - Manage Deployments, it shows as deployed

      Show
      Steps to Reproduce: 1) Start up vanilla installed WildFly 8.1.0 Final(standalone-full.xml), drop the folder dsc.ear into $JBOSS_HOME/standalone/deployments, then create an empty file "dsc.ear.dodeploy" 2) JBoss starts to deploy, and had some error printed in server.log 3) Checking http://localhost:9990 , Runtime - Server - Manage Deployments, it shows as deployed

    Description

      On deploying an EJB (in exploded ear) which has wrong @Resource/"lookup" JNDI names, it gives ERROR log. The marker file is changed to "***.ear.failed", but in web console "http://localhost:9990" the deployment is displayed in "Manage Deployments" page and shows deployed.

      Attachments

        Activity

          People

            Unassigned Unassigned
            rhn-support-lywang Lyle Wang (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: