1 Reply Latest reply on Mar 12, 2019 8:07 PM by ievgenii24

    EJB Error when more than one node in JBoss cluster


      Hi All,


      I'm using JBoss EAP 7.1.1.GA (WildFly Core 3.0.12.Final-redhat-1)

      I've configured JBoss cluster with SSL + undertow load balancer, i can see that cluster works, session is persist from node to node, i can see records like this in the log:


      ISPN000094: Received new cluster view for channel ee: [masterOne|1] (2) [masterOne, nodeOne]


      When i have only one node in cluster (does not mater which one, master or slave) all EJB requests works fine, but when i add second node to the cluster i receive this error for 50% of EJB requests:


      javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "platform-redhat-jboss-current/core-platform-ejb/ConfigurationEJB", view is interface com.mycompany.platform.ejb.Configuration, affinity is Cluster "ee"


      Exception trace is pretty big, but there is no detailed (caused by, suppressed or hidden) exception in the trace.



      I've tried TCP and UDP, turning on/off load balancer - nothing helped.


      Here is my configuration for remoting:


                  <subsystem xmlns="urn:jboss:domain:remoting:4.0">

                      <connector name="remoting-connector" socket-binding="remoting"/>

                      <http-connector name="http-remoting-connector" connector-ref="https" security-realm="ApplicationRealm"/>


                          <remote-outbound-connection name="remote-ejb-connection" outbound-socket-binding-ref="remote-ejb" username="secret" security-realm="ejb-security-realm" protocol="https-remoting">


                                  <property name="SASL_POLICY_NOANONYMOUS" value="false"/>

                                  <property name="SSL_ENABLED" value="false"/>







      I can see that there is similar issue in JBoss bugtracking system: [JBEAP-12527] Clustering test failures with node0 and node1 configured - JBoss Issue Tracker

      Judging from comments it was fixed somehow in JBoss 7.1.0 GA, but i have latest version (JBoss EAP 7.1.1.GA) and still can see this issue.


      Any advice? Maybe i need to adjust my cluster configuration somehow?