PM39649: EXCEPTION ADDING SERVLET MAPPING: MAPPING CLASH SERVLETWRAPPER REPORTED IN SYSTEMOUT.LOG WHEN NO SEVERE ERROR HAS OCCURED

8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

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 an
  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.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server v8 Base and Network Deployment.
  ****************************************************************
  * 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 second binding can utilize the
  application generated for the first binding.
  

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 PM39649 is currently targeted for inclusion in
  fix pack 8.0.0.1.  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 PM39356
  for WebSphere Application Server v7 Feature Pack for Service
  Component Architecture (SCA).
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PM39356

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R800 PSY

     UP