Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-7093

The xalan patch in JBPAPP-5230 is causing performance problems

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.1.2 ER1
    • EAP_EWP 5.1.1
    • Build
    • None
    • Hide
      In an earlier release the caching behaviour in XMLReaderManager was removed to resolve a memory leak. This forced each invocation to recreate the XMLReader and, as a result of the presence of the Synchronized methods, contend with other threads. Caching has been reinstated through the use of the SAXParser class, resolving the issue of thread contention. The original issue of a memory leak is avoided by use of the SAXParser reset method.
      Show
      In an earlier release the caching behaviour in XMLReaderManager was removed to resolve a memory leak. This forced each invocation to recreate the XMLReader and, as a result of the presence of the Synchronized methods, contend with other threads. Caching has been reinstated through the use of the SAXParser class, resolving the issue of thread contention. The original issue of a memory leak is avoided by use of the SAXParser reset method.
    • Documented as Resolved Issue
    • NEW

      The patch applied to address the memory leak in xalan, through JBPAPP-5230, disables the caching intent of XMLReaderManager but still enforces synchronization. This has a significant performance impact.

      Removing the synchronization and caching does significantly improve the performance, but does not restore it to the previous levels. Providing an alternative caching implementation, based on SAXParser, does restore the performance.

        1. xalan-j2-XALANJ-2195.patch-v2
          6 kB

              kconner@redhat.com Kevin Conner (Inactive)
              kconner@redhat.com Kevin Conner (Inactive)
              Russell Dickenson Russell Dickenson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: