Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-7754

Magnolia + wildfly + java 11 leads to performance issue


    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: High High
    • None
    • 5.7.6, 6.1.4
    • None
    • AKS

      When we upgraded to java 11 (from java 8), there was noticed a significant performance decrease on Magnolia.

      After investigating, it appears we are running into the issue as reported here: https://issues.redhat.com/projects/LOGMGR/issues/LOGMGR-263. A lot of threads are getting slowed down because of a call to MethodUtils.getMatchingAccessibleMethod(...) from "commons-beanutils" which is called indirectly by Magnolia from "info.magnolia.rendering.renderer.AbstractRenderer.newModel(Class, Node, RenderableDefinition, RenderingModel) AbstractRenderer.java:258" (BeanUtils.populate(...) call). The MethodUtils.getMatchingAccessibleMethod creates a new Logger on each call resulting in the issue described in the redhat issue.

      After implementing the workaround suggested here https://issues.redhat.com/browse/LOGMGR-263?focusedCommentId=13975980&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13975980 as a test, the performance returned back to what we had with java 8.

      Tested with Wildfly 13 and Wildfly 18.

        Acceptance criteria

              Unassigned Unassigned
              alevaux Aymeric Levaux
              0 Vote for this issue
              4 Start watching this issue