Bug 1154464

Summary: [GSS] (6.4.0) Repeatedly invoking setHandlerChain() can cause a build up of handler interceptors on the chain
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Kyle Lape <klape>
Component: Web ServicesAssignee: Alessio Soldano <asoldano>
Status: CLOSED CURRENTRELEASE QA Contact: Rostislav Svoboda <rsvoboda>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: jbliznak, kkhan
Target Milestone: DR10   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1154465 (view as bug list) Environment:
Last Closed: 2019-08-02 07:27:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1153972, 1154465, 1154466, 1276384    

Description Kyle Lape 2014-10-20 01:21:01 UTC 
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.
Comment 1 Kyle Lape 2014-10-20 01:22:33 UTC 
Still waiting on upstream Jira to be resolved.
Comment 3 Kabir Khan 2014-11-10 18:33:07 UTC 
See component upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1153972#c2 for explanation of why the upgrade was reverted and this BZ is set back to ASSIGNED
Comment 4 Kabir Khan 2014-11-10 18:33:07 UTC 
See component upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1153972#c2 for explanation of why the upgrade was reverted and this BZ is set back to ASSIGNED
Comment 5 Jan Blizňák 2014-11-19 10:57:01 UTC 
Verified on 6.4.0.DR10