Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 70B3DD1EA for ; Wed, 3 Oct 2012 09:12:14 +0000 (UTC) Received: (qmail 69958 invoked by uid 500); 3 Oct 2012 09:12:14 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 69646 invoked by uid 500); 3 Oct 2012 09:12:09 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 69593 invoked by uid 99); 3 Oct 2012 09:12:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2012 09:12:07 +0000 Date: Wed, 3 Oct 2012 20:12:07 +1100 (NCT) From: "Colm O hEigeartaigh (JIRA)" To: issues@cxf.apache.org Message-ID: <1901808656.158318.1349255527693.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (CXF-4539) WS-Security inbound performance regression MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 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