PH14088: Disabling isolation of third-party JAX-RS providers causes FileNotFoundException

PH14088 resolves the following problem:

ERROR DESCRIPTION:
A WebSphere applications that uses JAX-RS but does not specify the JAX-RS configuration within the web.xml may encounter a java.io.FileNotFoundExceptions such as the following when the JVM custom property "com.ibm.websphere.jaxrs.isolateJaxrsThirdPartyImplementations" is set to "false":
[7/9/19 8:30:59:933 CDT] FFDC Exception:java.io.FileNotFoundException SourceId:com.ibm.ws.webcontainer.filter.WebAppFilterManager.invo keFilters -IOE ProbeId:1044 java.io.FileNotFoundException: SRVE0190E: File not found:
/myapp/myResource at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor._pro cessEDR(DefaultExtensionProcessor.java:976) at
com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.proc essEDR(DefaultExtensionProcessor.java:957) at
com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.hand leRequest(DefaultExtensionProcessor.java:485) at
com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters (WebAppFilterManager.java:1114) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java: 4047) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.j ava:304) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer. java:1016) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContai ner.java:1817) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLin k.java:213) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr imination(HttpInboundLink.java:463) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRe quest(HttpInboundLink.java:530) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequ est(HttpInboundLink.java:316) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpI nboundLink.java:287) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sen dToDiscriminators(NewConnectionInitialReadCallback.java:214) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.com plete(NewConnectionInitialReadCallback.java:113) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureComp leted(AioReadCompletionListener.java:175) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyn cFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncC hannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHand ler.java:775) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892

USERS AFFECTED:
All users of IBM WebSphere Application Server with applications using JAXRS version 1.1.

PROBLEM DESCRIPTION:
Setting "com.ibm.websphere.jaxrs.isolateJaxrsTh irdPartyImplementations" to false may cause FileNotFoundException.

RECOMMENDATION:
None

PROBLEM SUMMARY:
WebSphere JAXRS supports a JVM custom property "com.ibm.websphere.jaxrs.isolateJaxrsThirdPartyImplementations" that disables the isolation of the third party JAXRS provider implementations that was added in WebSphere Application Server version 8.5.5.12.
If this property is set to "false" and the application configures JAXRS using only annotations and not web.xml, it is possible that a java.io.FileNotFoundException may occur when attempting to execute a JAXRS resource method.

PROBLEM CONCLUSION:
A code change has been done for this APAR to bypass the unneeded code causing the FileNotFoundException when the JVM property is set to false.
The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.16 and 9.0.5.1.
Please refer to the Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss? rs=180&uid=swg27004980