[ https://issues.jboss.org/browse/AS7-4862?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-4862: ------------------------------------- run https://hudson.qa.jboss.com/hudson/job/eap-6x-failover-ejb-ejbremote-unde... -- 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

[ https://issues.jboss.org/browse/AS7-4862?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-4862: ------------------------------------- Yes. Since SFSB invocations should be sticky, I am taking about load-balancing upon first invocation and thus creation. -- 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

[ https://issues.jboss.org/browse/AS7-4862?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-4862: ----------------------------------- This isn't a bug. Like mentioned in EJBCLIENT-31 https://issues.jboss.org/browse/EJBCLIENT-31?focusedCommentId=12675000&am... the EJB client API implementation uses a default implementation which "randomly" selects a deployment node from among the ones eligible, for handling the initial request. The user application is expected to configure the deployment.node.selector property to use any custom implementations of the DeploymentNodeSelector interface. More details here https://issues.jboss.org/browse/EJBCLIENT-31?focusedCommentId=12696416&am... -- 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

[ https://issues.jboss.org/browse/AS7-4862?page=com.atlassian.jira.plugin.s... ] Radoslav Husar reopened AS7-4862: --------------------------------- This must remain open as it is an issue. I will rephrase the as the cause might be something else, e.g. incorrect handling of notification about members in the cluster. The balancing by default should give a reasonable balancing of session creation, we have a test for that in the upstream testsuite but only on 2 nodes, so even the balancing might be really broken. The defaults and default implementation logic MUST be reasonable. We cannot expect users to go on an change every default to get the product working. The latest job shows the distribution problem in CR1 build as well https://hudson.qa.jboss.com/hudson/job/eap-6x-failover-ejb-ejbremote-unde... -- 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

[ https://issues.jboss.org/browse/AS7-4862?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-4862: ----------------------------------- Rado, like I said, this isn't a bug. If there are multiple nodes that can handle the same bean and if the client application expects the deployment node selection to be as per his application requirements, then the application is expected to configure such a deployment node selector for the initial load balancing on the beans. The EJB client API will have no knowledge of which of the nodes to select. For now, the only available implementation of a deployment node selector in the EJB client API is the random node selector. {quote} The defaults and default implementation logic MUST be reasonable. We cannot expect users to go on an change every default to get the product working. {quote} What's reasonable? Which part of the product isn't working? Like I have said in some JIRAs and forum threads, the EJB client API identifies a EJB target by the appname/modulename/distinctname/beanname combination. If multiple nodes can handle it, then it uses a deployment node selector to pick one node. The only implementation of that selector currently is the random node selector. The EJB client API cannot really come up with a different reasonable implementation since it's the application which decides what's reasonable. For example, how do you define a round robin implementation when the number of nodes keep changing? Each application might deal with that differently. {quote} we have a test for that in the upstream testsuite but only on 2 nodes, so even the balancing might be really broken. {quote} It's not broken. Which test is this? The tests that I'm aware of do not check any round robin or other similar load balancing techniques. {quote} The latest job shows the distribution problem in CR1 build as well https://hudson.qa.jboss.com/hudson/job/eap-6x-failover-ejb-ejbremote-unde... {quote} Why would the results be any different if the same random deployment node selector was used? I'm assigning this back, since this isn't broken and isn't a bug. If there's a requirement to provide a different implementation for deployment node selector then please create a feature request with details of the exact requirements of that selector. -- 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

[ https://issues.jboss.org/browse/AS7-4862?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-4862: ------------------------------------- Yes, the cluster is unsecured so no configuration is needed for the connections. -- 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

[ https://issues.jboss.org/browse/AS7-4862?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4862: ---------------------------------- Fix Version/s: 7.2.0.Alpha1 (was: 7.1.3.Final (EAP)) -- 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