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

[Gert Kropiunik (JIRA)]

    [ https://jira.jboss.org/jira/browse/EJBTHREE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12517152#action_12517152 ] 

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)

> 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
>            Assignee: Andrew Lee Rubinger
>         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