[
https://issues.jboss.org/browse/EJBTHREE-2264?page=com.atlassian.jira.plu...
]
Brad Maxwell moved JBPAPP-6912 to EJBTHREE-2264:
------------------------------------------------
Project: EJB 3.0 (was: JBoss Enterprise Application Platform)
Key: EJBTHREE-2264 (was: JBPAPP-6912)
Affects Version/s: bom-eap5-1.0.2
(was: EAP_EWP 5.1.0)
Component Fix Version(s): proxy-clustered 1.0.4
Component/s: proxy-clustered
(was: Clustering)
Security: (was: Public)
Fix Version/s: bom-eap5-1.0.3
(was: EAP_EWP 5.1.2)
Docs QE Status: (was: NEW)
Cannot specify default loadBalancePolicy for Clustered EJB3s
------------------------------------------------------------
Key: EJBTHREE-2264
URL:
https://issues.jboss.org/browse/EJBTHREE-2264
Project: EJB 3.0
Issue Type: Bug
Components: proxy-clustered
Affects Versions: bom-eap5-1.0.2
Reporter: Brad Maxwell
Assignee: Brad Maxwell
Fix For: bom-eap5-1.0.3
Tried using ejb3-interceptors-aop.xml, however it seems you cannot modify @Clustered
annotations, since the EJBs already have @Clustered on them.
This file is where the defaults are currently, This file can be modified to allow you to
specify the default loadBalancePolicy to be specified and the default sticky load balance
policy in the
$JBOSS_HOME/server/$PROFILE/deployers/ejb3.deployer/META-INF/ejb3-deployers-jboss-beans.xml
jboss-ejb3-proxy-clustered-1.0.3/src/main/java/org/jboss/ejb3/proxy/clustered/registry/ProxyClusteringRegistry.java
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira