Fixes are available
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
APAR status
Closed as program error.
Error description
When multiple JAX-RS applictions are in the same WAR, WebSphere may select a provider from the wrong application. Unexpected result is received with no error. For example: Call in browser http://localhost:9080/rest/1.7.0/check/checkVersion expected result: {"response":"Provider","activeAPI":170} Call in browser http://localhost:9080/rest/1.6.0/check/checkVersion expected result: {"response":"Provider","activeAPI":160} but get: {"response":"Provider","activeAPI":170}
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: In WAS V9 JAXRS providers with subtle * * path differences may not be cached * * properly, causing the wrong * * provider to be invoked. * **************************************************************** * RECOMMENDATION: * **************************************************************** In WAS V9 a performance modification to CXF code was inserted to cache JAXRS providers. There are problems with this caching that prevent proper differentiation between providers under certain circumstances.
Problem conclusion
This problem has been addressed in later versions of CXF and the back-port of these changes is non-trivial. Therefore we have addressed this issue in the short-term by inserting the following system property to disable provider cacheing if this problem occurs: com.ibm.webshere.jaxrs.DisableProviderCache. Setting this property to "true" will fix this issue. The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.10. 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
PH03514
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-10-02
Closed date
2018-12-03
Last modified date
2018-12-03
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R900 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 November 2021