Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-9355

EJB cluster proxies are not failing over

    XMLWordPrintable

Details

    • Regression, Blocks Testing

    Description

      There is a cluster of two EAP servers called "node1" and "node2". There is a clustered EJB application deployed on both servers.

      I am using these jboss-ejb-client.properties

      remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=node1
invocation.timeout=120000

remote.connection.node1.host=127.0.0.1
remote.connection.node1.port=8080
remote.connection.node1.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
remote.connection.node1.channel.options.org.jboss.remoting3.RemotingOptions.MAX_OUTBOUND_MESSAGES=30000

      There are two issues blocking load-balancing and failover:
      1. wildfly-discovery-client needs to be updated to 1.0.0.Beta10 in order to fix WFDISC-17. With the current version 1.0.0.Beta9, the EJB client logs this NPE:

      javax.naming.CommunicationException: EJBCLIENT000062: Failed to look up "/server/HelloBean!ejb.HelloBeanRemote?stateful" [Root exception is java.lang.NullPointerException]
	at org.jboss.ejb.client.EJBRootContext.lookupNative(EJBRootContext.java:139)
	at org.wildfly.naming.client.AbstractContext.lookup(AbstractContext.java:88)
	at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
	at javax.naming.InitialContext.lookup(InitialContext.java:417)
	at org.jboss.as.standaloneejbclient.Main.doSingleLookupSmarterStylePropertiesFromFileOnClasspath(Main.java:329)
	at org.jboss.as.standaloneejbclient.Main.main(Main.java:34)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: java.lang.NullPointerException
	at org.wildfly.discovery.ServiceURL.satisfies(ServiceURL.java:256)
	at org.wildfly.discovery.impl.LocalRegistryAndDiscoveryProvider.discover(LocalRegistryAndDiscoveryProvider.java:74)
	at org.wildfly.discovery.Discovery.discover(Discovery.java:94)
	at org.jboss.ejb.protocol.remote.RemotingEJBDiscoveryProvider.discover(RemotingEJBDiscoveryProvider.java:74)
	at org.wildfly.discovery.ConfiguredProvider.discover(ConfiguredProvider.java:45)
	at org.wildfly.discovery.Discovery.discover(Discovery.java:94)
	at org.jboss.ejb.client.EJBClientContext.discover(EJBClientContext.java:440)
	at org.jboss.ejb.client.EJBClientContext.discoverAffinityNone(EJBClientContext.java:711)
	at org.jboss.ejb.client.EJBClientContext.performLocatedAction(EJBClientContext.java:698)
	at org.jboss.ejb.client.EJBClientContext.createSession(EJBClientContext.java:679)
	at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:280)
	at org.jboss.ejb.client.EJBRootContext.lookupNative(EJBRootContext.java:137)
	... 10 more

      2. Using the default affinity, or setting affinity to one of these: Affinity.LOCAL, new ClusterAffinity("ejb") will prevent the client to successfully fail over to another node in the cluster.

      The only workaround for now is setting affinity to Affinity.NONE.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-25218 [QA](8.0.z) WFLY-6282 - Exceptions in 2-clusters EJB invocation graceful shutdown tests

          • Critical - To be worked on immediately following BLOCKER issues.
          • New

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9028 EJB client 4.x can't invoke EJBs if more than one connection in "remote.connections" property is set

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3583 [QA](7.4.z) WFLY-6282 - Exceptions in 2-clusters EJB invocation graceful shutdown tests

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3926 ArrayIndexOutOfBoundsException in EJB client in 2-clusters EJB invocation graceful shutdown tests

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-8553 TimeoutException: No invocation response received in X milliseconds

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3676 NPE in LocalEjbReceiver.removeClusterNodes during server shutdown

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3730 High response times in ejbremote REPL_SYNC load test

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is blocked by

          Feature Request - Feature requests from customers and/or users EJBCLIENT-234 Provide a means for the user to obtain a proxy with cluster affinity.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11348 EJBClient 4.x: wildfly-config.xml with ServiceURLs throws parsing error

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. WFDISC-22 Problem parsing multiple <service/> elements

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-11713 Upgrade JBoss EJB Client to 4.0.0.CR5

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. EJBCLIENT-214 Cluster-related ServiceURLs not being discovered

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. EJBCLIENT-216 ServiceURLs with node: concreteURI scheme affinities not being created

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11337 Fix and re-enable RemoteFailoverTestCase

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11808 RemoteFailoverTestCase.testSecureStatelessFailover fails due to authorization

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              rachmato@redhat.com Richard Achmatowicz
              mvinkler1@redhat.com Michal Vinkler
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: