3:14 p.m.
Graeme Wallace created AS7-4223:
-----------------------------------
Summary: Failure to load balance clustered SLSB
Key: AS7-4223
URL: https://issues.jboss.org/browse/AS7-4223
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.1.Final
Reporter: Graeme Wallace
Assignee: Paul Ferraro
The following code points to an EJB which is specified as clustered via the jboss-ejb3.xml
- however it always connects to the first node in remote.connections.
Properties properties = new Properties();
properties.put("endpoint.name",
"farecompare-client-endpoint");
properties.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED",
"false");
properties.put("remote.connections", "cmc5101,cmc5102");
properties.put("remote.connection.cmc5101.host", "cmc5-101");
properties.put("remote.connection.cmc5101.port", "4447");
properties.put("remote.connection.cmc5101.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
properties.put("remote.connection.cmc5102.host", "cmc5-102");
properties.put("remote.connection.cmc5102.port", "4447");
properties.put("remote.connection.cmc5102.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
PropertiesBasedEJBClientConfiguration configuration = new
PropertiesBasedEJBClientConfiguration(properties);
final ContextSelector ejbClientContextSelector = new
ConfigBasedEJBClientContextSelector(configuration);
final ContextSelector previousSelector =
EJBClientContext.setSelector(ejbClientContextSelector);
final Hashtable jndiProperties = new Hashtable();
jndiProperties.put(Context.URL_PKG_PREFIXES,
"org.jboss.ejb.client.naming");
final Context context = new InitialContext(jndiProperties);
LocationModuleAPI locationModule = (LocationModuleAPI) context.lookup(
"ejb:locationmodule/xxi-framework-location-finder-module-ejb//LocationModuleSessionBean!com.xxi.framework.locationfindermodule.api.LocationModuleAPI");
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:44 a.m.
[
https://issues.jboss.org/browse/AS7-4223?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-4223:
-----------------------------------
Paul, the real issue here is that even though the cluster topology is sent back to the
client for stateless beans, the client has no idea about which cluster the stateless bean
belongs to. To fix this, we'll need to associate a weak affinity for the stateless
bean invocations. In the presence of @Clustered in a clustered server configuration, the
weak affinity would correspond to the name of the cluster to which the stateless bean
belongs. Looking at the current code, I don't see a way this is exposed by the
clustering implementation.
Failure to load balance clustered SLSB
--------------------------------------
Key: AS7-4223
URL: https://issues.jboss.org/browse/AS7-4223
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.1.Final
Reporter: Graeme Wallace
Assignee: Paul Ferraro
The following code points to an EJB which is specified as clustered via the
jboss-ejb3.xml - however it always connects to the first node in remote.connections.
Properties properties = new Properties();
properties.put("endpoint.name",
"farecompare-client-endpoint");
properties.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED",
"false");
properties.put("remote.connections", "cmc5101,cmc5102");
properties.put("remote.connection.cmc5101.host",
"cmc5-101");
properties.put("remote.connection.cmc5101.port", "4447");
properties.put("remote.connection.cmc5101.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
properties.put("remote.connection.cmc5102.host",
"cmc5-102");
properties.put("remote.connection.cmc5102.port", "4447");
properties.put("remote.connection.cmc5102.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
PropertiesBasedEJBClientConfiguration configuration = new
PropertiesBasedEJBClientConfiguration(properties);
final ContextSelector ejbClientContextSelector = new
ConfigBasedEJBClientContextSelector(configuration);
final ContextSelector previousSelector =
EJBClientContext.setSelector(ejbClientContextSelector);
final Hashtable jndiProperties = new Hashtable();
jndiProperties.put(Context.URL_PKG_PREFIXES,
"org.jboss.ejb.client.naming");
final Context context = new InitialContext(jndiProperties);
LocationModuleAPI locationModule = (LocationModuleAPI) context.lookup(
"ejb:locationmodule/xxi-framework-location-finder-module-ejb//LocationModuleSessionBean!com.xxi.framework.locationfindermodule.api.LocationModuleAPI");
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:47 a.m.
[
https://issues.jboss.org/browse/AS7-4223?page=com.atlassian.jira.plugin.s...
]
Paul Ferraro commented on AS7-4223:
-----------------------------------
I see. Thanks Jaikiran.
We effectively need something like @Clustered(partitionName="") from AS5/6. In
our case, we need something to indicate the cache container in which to find the cache
containing the client mappings. We can do this in 2 stages. First add weak affinity
using the default sfsb cache container - then add the ability to specify the client
mapping cache independently.
Failure to load balance clustered SLSB
--------------------------------------
Key: AS7-4223
URL: https://issues.jboss.org/browse/AS7-4223
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.1.Final
Reporter: Graeme Wallace
Assignee: Paul Ferraro
Labels: eap6_need_triage
The following code points to an EJB which is specified as clustered via the
jboss-ejb3.xml - however it always connects to the first node in remote.connections.
Properties properties = new Properties();
properties.put("endpoint.name",
"farecompare-client-endpoint");
properties.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED",
"false");
properties.put("remote.connections", "cmc5101,cmc5102");
properties.put("remote.connection.cmc5101.host",
"cmc5-101");
properties.put("remote.connection.cmc5101.port", "4447");
properties.put("remote.connection.cmc5101.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
properties.put("remote.connection.cmc5102.host",
"cmc5-102");
properties.put("remote.connection.cmc5102.port", "4447");
properties.put("remote.connection.cmc5102.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
PropertiesBasedEJBClientConfiguration configuration = new
PropertiesBasedEJBClientConfiguration(properties);
final ContextSelector ejbClientContextSelector = new
ConfigBasedEJBClientContextSelector(configuration);
final ContextSelector previousSelector =
EJBClientContext.setSelector(ejbClientContextSelector);
final Hashtable jndiProperties = new Hashtable();
jndiProperties.put(Context.URL_PKG_PREFIXES,
"org.jboss.ejb.client.naming");
final Context context = new InitialContext(jndiProperties);
LocationModuleAPI locationModule = (LocationModuleAPI) context.lookup(
"ejb:locationmodule/xxi-framework-location-finder-module-ejb//LocationModuleSessionBean!com.xxi.framework.locationfindermodule.api.LocationModuleAPI");
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:23 p.m.
[
https://issues.jboss.org/browse/AS7-4223?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-4223:
------------------------------
Fix Version/s: 7.1.2.Final
Failure to load balance clustered SLSB
--------------------------------------
Key: AS7-4223
URL: https://issues.jboss.org/browse/AS7-4223
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.1.Final
Reporter: Graeme Wallace
Assignee: Paul Ferraro
Labels: eap6_need_triage
Fix For: 7.1.2.Final
The following code points to an EJB which is specified as clustered via the
jboss-ejb3.xml - however it always connects to the first node in remote.connections.
Properties properties = new Properties();
properties.put("endpoint.name",
"farecompare-client-endpoint");
properties.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED",
"false");
properties.put("remote.connections", "cmc5101,cmc5102");
properties.put("remote.connection.cmc5101.host",
"cmc5-101");
properties.put("remote.connection.cmc5101.port", "4447");
properties.put("remote.connection.cmc5101.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
properties.put("remote.connection.cmc5102.host",
"cmc5-102");
properties.put("remote.connection.cmc5102.port", "4447");
properties.put("remote.connection.cmc5102.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
PropertiesBasedEJBClientConfiguration configuration = new
PropertiesBasedEJBClientConfiguration(properties);
final ContextSelector ejbClientContextSelector = new
ConfigBasedEJBClientContextSelector(configuration);
final ContextSelector previousSelector =
EJBClientContext.setSelector(ejbClientContextSelector);
final Hashtable jndiProperties = new Hashtable();
jndiProperties.put(Context.URL_PKG_PREFIXES,
"org.jboss.ejb.client.naming");
final Context context = new InitialContext(jndiProperties);
LocationModuleAPI locationModule = (LocationModuleAPI) context.lookup(
"ejb:locationmodule/xxi-framework-location-finder-module-ejb//LocationModuleSessionBean!com.xxi.framework.locationfindermodule.api.LocationModuleAPI");
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:26 p.m.
[
https://issues.jboss.org/browse/AS7-4223?page=com.atlassian.jira.plugin.s...
]
Graeme Wallace commented on AS7-4223:
-------------------------------------
Could you supply details of what needs to be specified and where ? Thanks.
Failure to load balance clustered SLSB
--------------------------------------
Key: AS7-4223
URL: https://issues.jboss.org/browse/AS7-4223
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.1.Final
Reporter: Graeme Wallace
Assignee: Paul Ferraro
Labels: eap6_need_triage
Fix For: 7.1.2.Final
The following code points to an EJB which is specified as clustered via the
jboss-ejb3.xml - however it always connects to the first node in remote.connections.
Properties properties = new Properties();
properties.put("endpoint.name",
"farecompare-client-endpoint");
properties.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED",
"false");
properties.put("remote.connections", "cmc5101,cmc5102");
properties.put("remote.connection.cmc5101.host",
"cmc5-101");
properties.put("remote.connection.cmc5101.port", "4447");
properties.put("remote.connection.cmc5101.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
properties.put("remote.connection.cmc5102.host",
"cmc5-102");
properties.put("remote.connection.cmc5102.port", "4447");
properties.put("remote.connection.cmc5102.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
PropertiesBasedEJBClientConfiguration configuration = new
PropertiesBasedEJBClientConfiguration(properties);
final ContextSelector ejbClientContextSelector = new
ConfigBasedEJBClientContextSelector(configuration);
final ContextSelector previousSelector =
EJBClientContext.setSelector(ejbClientContextSelector);
final Hashtable jndiProperties = new Hashtable();
jndiProperties.put(Context.URL_PKG_PREFIXES,
"org.jboss.ejb.client.naming");
final Context context = new InitialContext(jndiProperties);
LocationModuleAPI locationModule = (LocationModuleAPI) context.lookup(
"ejb:locationmodule/xxi-framework-location-finder-module-ejb//LocationModuleSessionBean!com.xxi.framework.locationfindermodule.api.LocationModuleAPI");
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:03 a.m.
[
https://issues.jboss.org/browse/AS7-4223?page=com.atlassian.jira.plugin.s...
]
Paul Ferraro commented on AS7-4223:
-----------------------------------
In the end (meaning, once this issue is fixed) - nothing else will need to be specified,
unless you want to override the effective set of nodes to which a given SLSB should be
load balanced.
Failure to load balance clustered SLSB
--------------------------------------
Key: AS7-4223
URL: https://issues.jboss.org/browse/AS7-4223
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.1.Final
Reporter: Graeme Wallace
Assignee: Paul Ferraro
Labels: eap6_need_triage
Fix For: 7.1.2.Final
The following code points to an EJB which is specified as clustered via the
jboss-ejb3.xml - however it always connects to the first node in remote.connections.
Properties properties = new Properties();
properties.put("endpoint.name",
"farecompare-client-endpoint");
properties.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED",
"false");
properties.put("remote.connections", "cmc5101,cmc5102");
properties.put("remote.connection.cmc5101.host",
"cmc5-101");
properties.put("remote.connection.cmc5101.port", "4447");
properties.put("remote.connection.cmc5101.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
properties.put("remote.connection.cmc5102.host",
"cmc5-102");
properties.put("remote.connection.cmc5102.port", "4447");
properties.put("remote.connection.cmc5102.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
PropertiesBasedEJBClientConfiguration configuration = new
PropertiesBasedEJBClientConfiguration(properties);
final ContextSelector ejbClientContextSelector = new
ConfigBasedEJBClientContextSelector(configuration);
final ContextSelector previousSelector =
EJBClientContext.setSelector(ejbClientContextSelector);
final Hashtable jndiProperties = new Hashtable();
jndiProperties.put(Context.URL_PKG_PREFIXES,
"org.jboss.ejb.client.naming");
final Context context = new InitialContext(jndiProperties);
LocationModuleAPI locationModule = (LocationModuleAPI) context.lookup(
"ejb:locationmodule/xxi-framework-location-finder-module-ejb//LocationModuleSessionBean!com.xxi.framework.locationfindermodule.api.LocationModuleAPI");
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:20 a.m.
[
https://issues.jboss.org/browse/AS7-4223?page=com.atlassian.jira.plugin.s...
]
Jason Greene commented on AS7-4223:
-----------------------------------
Thanks Paul
Failure to load balance clustered SLSB
--------------------------------------
Key: AS7-4223
URL: https://issues.jboss.org/browse/AS7-4223
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.1.Final
Reporter: Graeme Wallace
Assignee: Paul Ferraro
Labels: eap6_clustering, eap6_need_triage
Fix For: 7.1.2.Final-redhat1
The following code points to an EJB which is specified as clustered via the
jboss-ejb3.xml - however it always connects to the first node in remote.connections.
Properties properties = new Properties();
properties.put("endpoint.name",
"farecompare-client-endpoint");
properties.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED",
"false");
properties.put("remote.connections", "cmc5101,cmc5102");
properties.put("remote.connection.cmc5101.host",
"cmc5-101");
properties.put("remote.connection.cmc5101.port", "4447");
properties.put("remote.connection.cmc5101.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
properties.put("remote.connection.cmc5102.host",
"cmc5-102");
properties.put("remote.connection.cmc5102.port", "4447");
properties.put("remote.connection.cmc5102.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS",
"false");
PropertiesBasedEJBClientConfiguration configuration = new
PropertiesBasedEJBClientConfiguration(properties);
final ContextSelector ejbClientContextSelector = new
ConfigBasedEJBClientContextSelector(configuration);
final ContextSelector previousSelector =
EJBClientContext.setSelector(ejbClientContextSelector);
final Hashtable jndiProperties = new Hashtable();
jndiProperties.put(Context.URL_PKG_PREFIXES,
"org.jboss.ejb.client.naming");
final Context context = new InitialContext(jndiProperties);
LocationModuleAPI locationModule = (LocationModuleAPI) context.lookup(
"ejb:locationmodule/xxi-framework-location-finder-module-ejb//LocationModuleSessionBean!com.xxi.framework.locationfindermodule.api.LocationModuleAPI");
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5210
days inactive
5241
days old
6 comments
4 participants
participants (4)
-
Graeme Wallace (JIRA) -
jaikiran pai (JIRA)
-
Jason Greene (JIRA)
-
Paul Ferraro (JIRA)