[jira] Updated: (CXF-2342) Performance issue in StaxInInterceptor

["Kevin Conaway (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Conaway updated CXF-2342:
-------------------------------

    Attachment: CXF-2342.patch

Attaching patch that adds a pool of XmlInputFactory/XmlOutputFactory instances instead of reusing a single one.

I've also made StaxUtils.getXMLInputFactory and StaxUtils.getXMLOutputFactory() private so that callers are forced to use the convenience methods to create readers and writers.

I hard coded the pool size to be 10.  Perhaps someone from the project can make a more informed decision as to how this can be configured

> Performance issue in StaxInInterceptor
> --------------------------------------
>
>                 Key: CXF-2342
>                 URL: https://issues.apache.org/jira/browse/CXF-2342
>             Project: CXF
>          Issue Type: Improvement
>    Affects Versions: 2.2.2
>            Reporter: Kevin Conaway
>         Attachments: CXF-2342.patch
>
>
> From this mailing list thread [Performance issue in StaxInInterceptor|http://www.nabble.com/Performance-issue-in-StaxInInterceptor-td24499018.html]:
> In cxf-2.2.2, StaxInInterceptor#handleMessage() synchronizes on the XMLInputFactory before calling XMLInputFactory#createXMLStreamReader(InputStream, String).
> Profiling our application reveals this to be a pain point in high volume situations 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.