[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1946) Undeploy Issue with Clustered Stateless Session Beans with HTTP(S) Remote Bindings

[ https://jira.jboss.org/jira/browse/EJBTHREE-1946?page=com.atlassian.jira.... ] Gert Kropiunik commented on EJBTHREE-1946: ------------------------------------------ I have exactly the same problem. After undeploying my app that has clustered SLSBeans with remote proxies for HTTP and HTTPS I can still see the bindings in the JNDI-View of the jmx-console. So they don't get un-bound when the bean is stopped. When I try to re-deploy I get NameAlreadyBoundExceptions for the remote bindings of the HTTP and HTTPS proxies. before stopping the application: | +- DocumentStateManager (class: org.jnp.interfaces.NamingContext) | | +- local (class: Proxy for: at.apa.excelsa.contentmanager.document.state.DocumentStateManagerLocal) | | +- local-at.apa.excelsa.contentmanager.document.state.DocumentStateManagerLocal (class: Proxy for: at.apa.excelsa.contentmanager.document.state.DocumentStateManagerLocal) | | +- remote (class: Proxy for: at.apa.excelsa.contentmanager.client.document.state.DocumentStateManagerRemote) | | +- remoteHttp (class: Proxy for: at.apa.excelsa.contentmanager.client.document.state.DocumentStateManagerRemote) | | +- remoteHttps (class: Proxy for: at.apa.excelsa.contentmanager.client.document.state.DocumentStateManagerRemote) after stopping: | +- DocumentStateManager (class: org.jnp.interfaces.NamingContext) | | +- remoteHttp (class: Proxy for: at.apa.excelsa.contentmanager.client.document.state.DocumentStateManagerRemote) | | +- remoteHttps (class: Proxy for: at.apa.excelsa.contentmanager.client.document.state.DocumentStateManagerRemote) -- 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