You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2012/10/03 11:12:07 UTC

[jira] [Created] (CXF-4539) WS-Security inbound performance regression

Colm O hEigeartaigh created CXF-4539:
----------------------------------------

             Summary: WS-Security inbound performance regression
                 Key: CXF-4539
                 URL: https://issues.apache.org/jira/browse/CXF-4539
             Project: CXF
          Issue Type: Bug
          Components: WS-* Components
    Affects Versions: 2.6.2, 2.5.5, 2.4.9
            Reporter: Colm O hEigeartaigh
             Fix For: 2.4.10, 2.5.6, 2.6.3



There is a significant performance regression in inbound WS-Security in CXF due to CXF-4052:

https://issues.apache.org/jira/browse/CXF-4052

On each invocation, a URL is resolved corresponding to the path of the properties file for the signature verification or decryption Crypto. This carries a performance penalty due to the CXF ResourceManager being involved, even though the Crypto object itself is actually cached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CXF-4539) WS-Security inbound performance regression

Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh reassigned CXF-4539:
----------------------------------------

    Assignee: Colm O hEigeartaigh
    
> WS-Security inbound performance regression
> ------------------------------------------
>
>                 Key: CXF-4539
>                 URL: https://issues.apache.org/jira/browse/CXF-4539
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.4.9, 2.5.5, 2.6.2
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>             Fix For: 2.4.10, 2.5.6, 2.6.3
>
>
> There is a significant performance regression in inbound WS-Security in CXF due to CXF-4052:
> https://issues.apache.org/jira/browse/CXF-4052
> On each invocation, a URL is resolved corresponding to the path of the properties file for the signature verification or decryption Crypto. This carries a performance penalty due to the CXF ResourceManager being involved, even though the Crypto object itself is actually cached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CXF-4539) WS-Security inbound performance regression

Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh resolved CXF-4539.
--------------------------------------

    Resolution: Fixed
    
> WS-Security inbound performance regression
> ------------------------------------------
>
>                 Key: CXF-4539
>                 URL: https://issues.apache.org/jira/browse/CXF-4539
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.4.9, 2.5.5, 2.6.2
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>             Fix For: 2.4.10, 2.5.6, 2.6.3
>
>
> There is a significant performance regression in inbound WS-Security in CXF due to CXF-4052:
> https://issues.apache.org/jira/browse/CXF-4052
> On each invocation, a URL is resolved corresponding to the path of the properties file for the signature verification or decryption Crypto. This carries a performance penalty due to the CXF ResourceManager being involved, even though the Crypto object itself is actually cached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira