Bug 1154465 - [GSS] (6.3.z) Repeatedly invoking setHandlerChain() can cause a build up of handler interceptors on the chain
Summary: [GSS] (6.3.z) Repeatedly invoking setHandlerChain() can cause a build up of h...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Services
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.3.3
Assignee: Alessio Soldano
QA Contact: Rostislav Svoboda
URL:
Whiteboard:
Depends On: 1154464
Blocks: eap633-payload 1154466 1157479 1276384
TreeView+ depends on / blocked
 
Reported: 2014-10-20 01:23 UTC by Kyle Lape
Modified: 2019-08-02 07:27 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1154464
: 1154466 (view as bug list)
Environment:
Last Closed: 2019-08-02 07:27:10 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA CXF-6038 0 None None None Never

Description Kyle Lape 2014-10-20 01:23:46 UTC 
+++ This bug was initially created as a clone of Bug #1154464 +++

If an interceptor chain is cached between invocations and a user calls setHandlerChain() before every invocation, the handler chain interceptors get added to the interceptor chain over and over indefinitely.

I'm guessing that JaxWsEndpointImpl.addHandlerInterceptors() would need to check for the presence of the handler interceptors on the chain already.

--- Additional comment from Kyle Lape on 2014-10-19 21:22:33 EDT ---

Still waiting on upstream Jira to be resolved.
Comment 1 Kyle Lape 2014-10-24 01:28:51 UTC 
Upstream fix has been committed.

https://github.com/apache/cxf/commit/00636b5987466ef8ab5e901fa0efc701bb124090
Comment 12 Yong Yang 2014-12-19 07:48:41 UTC 
Will upgrade CXF to 2.7.14
https://bugzilla.redhat.com/show_bug.cgi?id=1174927
Comment 17 Rostislav Svoboda 2015-01-19 13:37:23 UTC 
Verified on EAP 6.3.3 CR1 using reproducer used for BZ 1154466 verification.
Note You need to log in before you can comment on or make changes to this bug.