Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-1946

Undeploy Issue with Clustered Stateless Session Beans with HTTP(S) Remote Bindings

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 1.1.5
    • proxy-clustered
    • AS 5.1.0 GA

      Combination of a clustered annotation and a HTTP(S) based remote proxy on a stateless session bean causes the bean to leave the HTTP(S) remote proxy binding still deployed after an undeploy operation, breaking re-deploys of the bean.

      For example:

      <session>
      <ejb-name>TestBean</ejb-name>
      <remote-binding>
      <jndi-name>TestBean/remote</jndi-name>
      </remote-binding>
      <remote-binding>
      <jndi-name>TestBean/remotehttp</jndi-name>
      <client-bind-url>
      http://${public.firewall.address}/servlet-invoker/ServerInvokerServlet
      </client-bind-url>
      </remote-binding>
      <clustered>true</clustered>
      </session>

        1. test.rar
          7 kB
          Joel Konieczny
        2. JndiSessionRegistrarBase.patch
          1 kB
          Joel Konieczny

              arubinge@redhat.com Andrew Rubinger (Inactive)
              jkonieczny Joel Konieczny (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: