Fixes are available
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
In addition to default SimpleFileServlet, additional info is also loaded from scope.war module, which may be causing this. Line 319: [8/19/15 5:57:07:182 EDT] 000000f9 metadata 1 com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl setPageURI card_df_1#scope.war#InternalServlet_SimpleFileServlet Line 320: card_df_1#scope.war#InternalServlet_SimpleFileServlet Line 321: com.ibm.ws.webcontainer.metadata.WebModuleMetaDataImpl@104f61f2[ card_df_1#scope.war] This problem seems to happen because the Spring framework is doing a direct reference to our SimpleFileServlet. This is not allowed and not supported.
Local fix
I have seen reports of people fixing this by setting Spring not to handle static file requests, but I haven't tested this solution so I am not sure of it solves the issue. Just wanted to throw that idea out there for the customer to try.
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server Full * * Profile version 8.5.5 users of Performance * * Monitoring Infrastructure(PMI). * **************************************************************** * PROBLEM DESCRIPTION: Unable to register PMI module due to * * duplicate name: SimpleFileServlet * **************************************************************** * RECOMMENDATION: * **************************************************************** When PMI is enabled on the server, and an application dispatches to "SimpleFIleServlet", the following error message might be seen: CWPMI0023W: Unable to register PMI module due to duplicate name: SimpleFileServlet
Problem conclusion
The WebContainer code was modified to avoid multiple registrations of servlets in PMI. The fix for this APAR is currently targeted for inclusion in fixpack 8.5.5.9. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI48485
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-09-10
Closed date
2015-10-08
Last modified date
2015-10-08
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
27 April 2022