Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-6953

EJB redeployment fails after dependency redeploy

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.1.2 ER2
    • EAP_EWP 5.1.1
    • EJB
    • None
    • Hide

      Supposing we have a project A(deployed using farm service) which is a dependency of EJB project B(deployed using HA-Singleton service). This dependence relation is done by using aliases.txt and the jboss-dependency.xml approach.

      The problem is when we make a hot deploy of the A, you can see the exception.

      Attached we have a zip containing projects and a server.log file describing the error. You can use it to reproduce the error

      Show
      Supposing we have a project A(deployed using farm service) which is a dependency of EJB project B(deployed using HA-Singleton service). This dependence relation is done by using aliases.txt and the jboss-dependency.xml approach. The problem is when we make a hot deploy of the A, you can see the exception. Attached we have a zip containing projects and a server.log file describing the error. You can use it to reproduce the error
    • Hide

      There's two workarounds:

      • After the error, manually redeploy the dependent EJB;
      • Restart the server.
      Show
      There's two workarounds: After the error, manually redeploy the dependent EJB; Restart the server.
    • Medium
    • Hide
      If an EJB jar deployment specifies a dependency and this dependency is restarted, the deployment or start of the EJB would fail with an IllegalStateException message similar to the following:

      <screen>
      Caused by: java.lang.IllegalStateException: jboss.j2ee:ear=helloWorld.ear,jar=helloWorld-ejb.jar,name=HelloBean,service=EJB3 is already installed.
      </screen>

      This was caused because the EJB's deployment was duplicated during the installation or start. To resolve this problem before upgrading to EAP 5.1.2, either redeploy the dependent EJB or restart the server. This problem has been fixed and this workaround is not required once you have upgraded.
      Show
      If an EJB jar deployment specifies a dependency and this dependency is restarted, the deployment or start of the EJB would fail with an IllegalStateException message similar to the following: <screen> Caused by: java.lang.IllegalStateException: jboss.j2ee:ear=helloWorld.ear,jar=helloWorld-ejb.jar,name=HelloBean,service=EJB3 is already installed. </screen> This was caused because the EJB's deployment was duplicated during the installation or start. To resolve this problem before upgrading to EAP 5.1.2, either redeploy the dependent EJB or restart the server. This problem has been fixed and this workaround is not required once you have upgraded.
    • Documented as Resolved Issue
    • NEW

    Description

      We need to implement the uninstall method from EJB3.
      When you have dependencies between deployments, undeploying a dependency undeploys the ejb, but when the dependency is redeployed, the ejb fails because it was not uninstalled.

      The exception we get when it tries to redeploy the dependent EJB:

      Caused by: java.lang.IllegalStateException: jboss.j2ee:ear=helloWorld.ear,jar=helloWorld-ejb.jar,name=HelloBean,service=EJB3 is already installed.

      Attachments

        Activity

          People

            rhn-engineering-cdewolf Carlo de Wolf
            rhn-support-wsiqueir William Siqueira
            Russell Dickenson Russell Dickenson (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: