APAR status
Closed as program error.
Error description
When an SCA composite has a component using both binding.http and binding.atom, the internally generated web application for each binding uses the same context root. This will cause the following error to be logged in SystemOut.log even though there is no severe error. The application generated for the first binding functions properly for the other bindings. SCAWebExtensi E Exception adding servlet mapping: Mapping clash for ServletWrapper[TuscanyBindingServletWrapper:null]: Target ServletWrapper[TuscanyBindingServletWrapper:null] already exists at node / or HTTPExtension E Exception adding servlet mapping: Mapping clash for ServletWrapper[TuscanyBindingServletWrapper:null]: Target ServletWrapper[TuscanyBindingServletWrapper:null] already exists at node /
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All IBM WebSphere Application Server v7 * * Feature Pack for Service Component * * Architecture (SCA) users. * **************************************************************** * PROBLEM DESCRIPTION: "Exception adding servlet mapping" * * logged in SystemOut.log when no * * severe error has occurred. * **************************************************************** * RECOMMENDATION: * **************************************************************** Service Component Architecture (SCA) applications using binding.http and binding.atom utilize an application dynamically generated at deploy time. When an SCA component contains both binding.http and binding.atom, the internally generated web application for each binding uses the same context root and results in the following exception: SCAWebExtensi E Exception adding servlet mapping: Mapping clash for ServletWrapper[TuscanyBindingServletWrapper:null]: Target ServletWrapper[TuscanyBindingServletWrapper:null] already exists at node / Even though the second application failed to register properly, the application generated for the first binding functions properly for the other bindings.
Problem conclusion
The code was updated to log the error in FFDC logs instead of SystemOut.log. If the application is running as expected, the FFDC log entry can safely be ignored. The fix for APAR PM39356 is currently targeted for inclusion in fix pack 1.0.1.13. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 The fix for this issue will be delivered via APAR PM39649 for WebSphere Application Server v8.
Temporary fix
Comments
APAR Information
APAR number
PM39356
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-05-17
Closed date
2011-06-20
Last modified date
2011-06-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WAS SCA FEATURE
Fixed component ID
5724J0854
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
09 February 2022