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

Increased count of client/server errors when starting node after shutdown in EJB clustering scenario

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 7.4.0.GA
    • Clustering, EJB
    • None
    • False
    • False
    • Undefined

    Description

      Events which lead to error occurrence:

      08:17:43 Failing WILDFLY Service 'WildFly Service 1' ...
      08:17:44  Shutting down service WildFly Service 1 with a 15 seconds suspend timeout
      08:19:30 Restoring WILDFLY Service 'WildFly Service 1' ...
      08:19:31 Starting service WildFly Service 1 with command
      08:19:31 /tmp/tests-clustering/jboss-eap-1/bin/standalone.sh -b=10.0.144.115 -bmanagement=10.0.144.115 -bprivate=10.0.144.115 --server-config=standalone-ha.xml -Djboss.default.multicast.address=230.0.0.211 -Dprogram.name=wildfly1 -Djboss.node.name=wildfly1
      

      Server error on WildFly Service 3:

      2021-05-05 08:19:43,345 ERROR [org.jboss.as.ejb3.invocation] (default task-9) WFLYEJB0034: Jakarta Enterprise Beans Invocation failed on component ServiceAccessBean for method public abstract java.lang.String org.jboss.test.singletonservice.ServiceAccess.getNodeNameOfService(): javax.ejb.ConcurrentAccessTimeoutException: WFLYEJB0241: Enterprise Beans 3.1 PFD2 4.8.5.5.1 concurrent access timeout on HaSingletonServiceInvokerBean - could not obtain lock within 5000MILLISECONDS
      

      Client error:

      2021-05-05 08:19:43,497 ERROR o.j.e.c.j.ClusteringEJBHASSRequestSampler: Thread Group 1-67: Error getting response: Invalid response: Resetting bean.
      

      I attached WildFly node logs and jmeter log.

      Attachments

        1. jmeter.log.zip
          139 kB
        2. wildfly.zip
          664 kB

        Activity

          People

            Unassigned Unassigned
            jkasik@redhat.com Jan Kašík
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: