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

Details

    • Bug
    • Resolution: Done
    • 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

    Description

      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.

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-6097 Track component upgrades - EAP 5.1.2

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-10705 xalan regression causing classloading issue

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-5230 CLONE -Patch Xalan for XALANJ-2195

          • 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

          Activity

            People

              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

              Dates

                Created:
                Updated:
                Resolved: