[JBoss JIRA] Created: (EJBTHREE-1946) Undeploy Issue with Clustered Stateless Session Beans with HTTP(S) Remote Bindings
5:59 p.m.
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
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
6:01 p.m.
New subject: [JBoss JIRA] Updated: (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....
]
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
6:07 p.m.
New subject: [JBoss JIRA] Assigned: (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....
]
Andrew Lee Rubinger reassigned EJBTHREE-1946:
---------------------------------------------
Assignee: Andrew Lee Rubinger
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
10:12 p.m.
New subject: [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)
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
5:53 p.m.
New subject: [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....
]
Ben Kirby commented on EJBTHREE-1946:
-------------------------------------
We also have exactly the same problem. Any progress towards a fix or a workaround?
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
8:47 p.m.
New subject: [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....
]
Joel Konieczny commented on EJBTHREE-1946:
------------------------------------------
Finally got some time to look into this. Put some extra logging into things and the
problem seems to be the proxyfactory deregistration.
Here's the relevant log trace:
13:14:04,027 DEBUG [JndiSessionRegistrarBase] (N/A) Unbinding Reference:
TestBean/remotehttp
13:14:04,027 DEBUG [ProxyClusteringRegistry] (N/A) Replacing ClusterConfigMetaData
partitionName property ${jboss.partition.name:DefaultPartition} with CMPPartition
13:14:04,027 DEBUG [JndiSessionRegistrarBase] (N/A) Deregistering ProxyFactory under name
"ProxyFactory/test_ear-1.0/TestBean/TestBean/remotehttp/CMPPartition"
13:14:04,027 DEBUG [JndiSessionRegistrarBase] (N/A) Bound javax.naming.Reference into JNDI
at "TestBean/remotehttp"
The naming reference is removed and then rebound during the proxy factory deregistration.
The stack trace during the rebind is:
org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase.rebind(JndiSessionRegistrarBase.java:961)
org.jboss.ejb3.proxy.clustered.jndiregistrar.JndiClusteredSessionRegistrarBase.clusterTopologyChanged(JndiClusteredSessionRegistrarBase.java:133)
org.jboss.ejb3.proxy.clustered.registry.ProxyClusteringRegistry.replicantsChanged(ProxyClusteringRegistry.java:241)
org.jboss.ha.framework.server.DistributedReplicantManagerImpl.notifyKeyListeners(DistributedReplicantManagerImpl.java:882)
org.jboss.ha.framework.server.DistributedReplicantManagerImpl.removeLocal(DistributedReplicantManagerImpl.java:470)
org.jboss.ha.framework.server.DistributedReplicantManagerImpl.remove(DistributedReplicantManagerImpl.java:452)
org.jboss.ha.framework.server.HATarget.cleanExistenceInCurrentHAPartition(HATarget.java:321)
org.jboss.ha.framework.server.HATarget.destroy(HATarget.java:135)
org.jboss.ejb3.proxy.clustered.registry.ProxyClusteringRegistry.unregisterClusteredBean(ProxyClusteringRegistry.java:157)
org.jboss.ejb3.proxy.clustered.factory.session.stateless.StatelessSessionClusteredProxyFactory.stop(StatelessSessionClusteredProxyFactory.java:127)
<Bunch of Microcontainer calls elided>
org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:568)
org.jboss.ejb3.common.registrar.plugin.mc.Ejb3McRegistrar.unbind(Ejb3McRegistrar.java:319)
org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase.deregisterProxyFactory(JndiSessionRegistrarBase.java:1312)
org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase.unbindEjb(JndiSessionRegistrarBase.java:695)
Basically a cluster topography changed event is being thrown during the proxy
deregistration that causes the naming reference to be rebound. I'm not familiar enough
with the expected process here to know if the event shouldn't have been thrown, or the
event processing shouldn't be re-registering the reference. However, the easy fix was
simply to reverse the unbind order.
Swap these lines from unbindEjb in JndiSessionRegistrarBase from this
// Unbind the JNDI entry
this.unbind(context, remoteBindingJndiName);
// Find and deregister the remote proxy factory
String remoteBindingProxyFactoryKey =
this.getProxyFactoryRegistryKey(remoteBindingJndiName, smd,
false);
this.deregisterProxyFactory(remoteBindingProxyFactoryKey);
to
// Find and deregister the remote proxy factory
String remoteBindingProxyFactoryKey =
this.getProxyFactoryRegistryKey(remoteBindingJndiName, smd,
false);
this.deregisterProxyFactory(remoteBindingProxyFactoryKey);
// Unbind the JNDI entry
this.unbind(context, remoteBindingJndiName);
Thus we unbind the entry regardless of what the proxy factory deregistration does.
We're testing this and it seems to work without any issues, but I have no idea if this
is the correct approach. Feedback?
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
9:01 p.m.
New subject: [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....
]
Andrew Lee Rubinger commented on EJBTHREE-1946:
-----------------------------------------------
Looks like some fine debugging. :)
If you create a patch (svn di > /path/to/file.patch) off jbossas/projects/ejb3/trunk
and attach it to this issue, we'll run it through the relevant testsuites and see if
there's any fallout. Also if you've got a testcase to reproduce the issue (which
we can then make pass) that'd be fantastic.
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
1:42 a.m.
New subject: [JBoss JIRA] Updated: (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....
]
Joel Konieczny updated EJBTHREE-1946:
-------------------------------------
Attachment: JndiSessionRegistrarBase.patch
Patch attached. I should be able to generate a test case for it if I can figure out how to
get the EmbeddedTestMc up in clustered mode with all the clustered versions of the
factories and HA goodies. Is there a test case somewhere that does this already I can rip
off?
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: JndiSessionRegistrarBase.patch, 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
5386
days inactive
5562
days old
7 comments
4 participants
participants (4)
-
Andrew Lee Rubinger (JIRA) -
Ben Kirby (JIRA)
-
Gert Kropiunik (JIRA)
-
Joel Konieczny (JIRA)