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

[JSF] Endless jakarta.faces.component log

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Regression, Blocks Testing
    • Hide
      • Start a 4 nodes cluster
      • deploy the attached clusterbench-ee10.ear application
      • put the cluster under some load (1000 users - 1 request per user every 4 secs): this is key in reproducing the issue, with just a few http request you won't see anything

      Note: you might have to restart nodes in the cluster to observer the issue; hence, run the load for ~5min, restart your nodes, run load for other 5min and you should be finally able to observe the message flooding the logs...

      if you are familiar with JMETER you can use this test plan JMETER-1.jmx to generate the necessary load to trigger the log: just open it with the GUI and press the start green button;
      you can start a 4 nodes local cluster started like:

      ./server1/bin/standalone.sh --server-config=standalone-ha.xml -Djboss.default.multicast.address=230.0.0.190 -Djboss.node.name=wildfly1 -Djboss.socket.binding.port-offset=100
      
      ./server2/bin/standalone.sh --server-config=standalone-ha.xml -Djboss.default.multicast.address=230.0.0.190 -Djboss.node.name=wildfly2 -Djboss.socket.binding.port-offset=200
      
      ./server3/bin/standalone.sh --server-config=standalone-ha.xml -Djboss.default.multicast.address=230.0.0.190 -Djboss.node.name=wildfly3 -Djboss.socket.binding.port-offset=300
      
      ./server4/bin/standalone.sh --server-config=standalone-ha.xml -Djboss.default.multicast.address=230.0.0.190 -Djboss.node.name=wildfly4 -Djboss.socket.binding.port-offset=400
      
      Show
      Start a 4 nodes cluster deploy the attached clusterbench-ee10.ear application put the cluster under some load (1000 users - 1 request per user every 4 secs): this is key in reproducing the issue, with just a few http request you won't see anything Note: you might have to restart nodes in the cluster to observer the issue; hence, run the load for ~5min, restart your nodes, run load for other 5min and you should be finally able to observe the message flooding the logs... if you are familiar with JMETER you can use this test plan JMETER-1.jmx to generate the necessary load to trigger the log: just open it with the GUI and press the start green button; you can start a 4 nodes local cluster started like: ./server1/bin/standalone.sh --server-config=standalone-ha.xml -Djboss.default.multicast.address=230.0.0.190 -Djboss.node.name=wildfly1 -Djboss.socket.binding.port-offset=100 ./server2/bin/standalone.sh --server-config=standalone-ha.xml -Djboss.default.multicast.address=230.0.0.190 -Djboss.node.name=wildfly2 -Djboss.socket.binding.port-offset=200 ./server3/bin/standalone.sh --server-config=standalone-ha.xml -Djboss.default.multicast.address=230.0.0.190 -Djboss.node.name=wildfly3 -Djboss.socket.binding.port-offset=300 ./server4/bin/standalone.sh --server-config=standalone-ha.xml -Djboss.default.multicast.address=230.0.0.190 -Djboss.node.name=wildfly4 -Djboss.socket.binding.port-offset=400

    Description

      We have a 4 nodes cluster where we deploy a distributed JSF application;
      Then, 1000 clients fire HTTP requests (every client waits 4 seconds between subsequent requests) at context path /clusterbench/faces/jsf.xhtml where the JSF application responds;
      After 5 minutes the following happens:

      • node 2 logs a SEVERE jakarta.faces.component message ~ 2.000 times
      • node 3 logs a SEVERE jakarta.faces.component message ~ 6.000.000 times

      The message being logged is always the same:

      2023-08-22 07:21:17,380 SEVERE [jakarta.faces.component] (default task-3) the component(jakarta.faces.component.html.HtmlDoctype@71ed7218) is the head component of the stack, but it's _isPushedAsCurrentRefCount < 1
      

      complete logs in wildfly(1).zip

      Attachments

        1. clusterbench-ee10.ear
          75 kB
        2. JMETER-1.jmx
          12 kB
        3. wildfly(1).zip
          28.11 MB

        Issue Links

          Activity

            People

              jaslee@redhat.com Jason Lee
              tborgato@redhat.com Tommaso Borgato
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: