[
https://jira.jboss.org/jira/browse/EJBTHREE-1946?page=com.atlassian.jira....
]
Joel Konieczny updated EJBTHREE-1946:
-------------------------------------
Attachment: test.rar
Sample maven project that replicates the issue. Just contains a single basic bean in a jar
wrapped in an ear.
Undeploy Issue with Clustered Stateless Session Beans with HTTP(S)
Remote Bindings
----------------------------------------------------------------------------------
Key: EJBTHREE-1946
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-1946
Project: EJB 3.0
Issue Type: Bug
Components: proxy-clustered
Affects Versions: 1.1.5
Environment: AS 5.1.0 GA
Reporter: Joel Konieczny
Attachments: test.rar
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>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira