PI82364: For JAX-RS 2.0, a request may fail with a 404 because a resource class was incorrectly indicated as not found.

Fixes are available

APAR status

Closed as program error.

Error description

During application initialization, a resource class was not
added to the application resource class list.  See the
following exception during a request:

00000024 W javax.ws.rs.NotFoundException: HTTP 404 Not Found
	at
org.apache.cxf.jaxrs.utils.SpecExceptions.toNotFoundExceptio
n(SpecExceptions.java:89)
	at
org.apache.cxf.jaxrs.utils.ExceptionUtils.toNotFoundExceptio
n(ExceptionUtils.java:129)
	at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processR
equest(JAXRSInInterceptor.java:209)
	at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMe
ssage(JAXRSInInterceptor.java:85)
	at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(Phase
InterceptorChain.java:308)
	at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(C
hainInitiationObserver.java:124)
	at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke
(AbstractHTTPDestination.java:265)
	at
com.ibm.ws.jaxrs20.endpoint.AbstractJaxRsWebEndpoint.invoke(
AbstractJaxRsWebEndpoint.java:134)
	at
com.ibm.websphere.jaxrs.server.IBMRestServlet.handleRequest(
IBMRestServlet.java:149)
	at
com.ibm.websphere.jaxrs.server.IBMRestServlet.doDelete(IBMRe
stServlet.java:134)
	at
javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
	at
com.ibm.websphere.jaxrs.server.IBMRestServlet.service(IBMRes
tServlet.java:99)
	at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(Servl
etWrapper.java:1290)
	at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest
(ServletWrapper.java:778)
	at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest
(ServletWrapper.java:475)
	at
com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFil
ters(WebAppFilterManager.java:1161)
	at
com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.j
ava:4978)
	at
com.ibm.ws.webcontainer31.osgi.webapp.WebApp31.handleRequest
(WebApp31.java:528)
	at
com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.handleRequ
est(DynamicVirtualHost.java:315)
	at
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContai
ner.java:1014)
	at
com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.run(Dynami
cVirtualHost.java:280)
	at
com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLi
nk$TaskWrapper.run(HttpDispatcherLink.java:967)
	at
com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLi
nk.wrapHandlerAndExecute(HttpDispatcherLink.java:359)
	at
com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLi
nk.ready(HttpDispatcherLink.java:318)
	at
com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.han
dleDiscrimination(HttpInboundLink.java:471)
	at
com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.han
dleNewRequest(HttpInboundLink.java:405)
	at
com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.pro
cessRequest(HttpInboundLink.java:285)
	at
com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.rea
dy(HttpInboundLink.java:256)
	at
com.ibm.ws.tcpchannel.internal.NewConnectionInitialReadCallb
ack.sendToDiscriminators(NewConnectionInitialReadCallback.ja
va:174)
	at
com.ibm.ws.tcpchannel.internal.NewConnectionInitialReadCallb
ack.complete(NewConnectionInitialReadCallback.java:83)
	at
com.ibm.ws.tcpchannel.internal.WorkQueueManager.requestCompl
ete(WorkQueueManager.java:504)
	at
com.ibm.ws.tcpchannel.internal.WorkQueueManager.attemptIO(Wo
rkQueueManager.java:574)
	at
com.ibm.ws.tcpchannel.internal.WorkQueueManager.workerRun(Wo
rkQueueManager.java:929)
	at
com.ibm.ws.tcpchannel.internal.WorkQueueManager$Worker.run(W
orkQueueManager.java:1018)
	at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Executor.java:1153)
	at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
lExecutor.java:628)
	at java.lang.Thread.run(Thread.java:785)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty - JAX-RS 2.0                 *
****************************************************************
* PROBLEM DESCRIPTION: For JAX-RS 2.0, a request may fail with *
*                      a 404 because a resource class was      *
*                      incorrectly indicated as not found.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During application initialization, a resource class was not
added to the application resource class list.  See the following
exception during a request:

00000024 W javax.ws.rs.NotFoundException: HTTP 404 Not Found
	at
org.apache.cxf.jaxrs.utils.SpecExceptions.toNotFoundException(Sp
ecExceptions.java:89)
	at
org.apache.cxf.jaxrs.utils.ExceptionUtils.toNotFoundException(Ex
ceptionUtils.java:129)
	at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processReque
st(JAXRSInInterceptor.java:209)
	at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessag
e(JAXRSInInterceptor.java:85)
	at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInte
rceptorChain.java:308)
	at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(Chain
InitiationObserver.java:124)
	at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(Abs
tractHTTPDestination.java:265)
	at
com.ibm.ws.jaxrs20.endpoint.AbstractJaxRsWebEndpoint.invoke(Abst
ractJaxRsWebEndpoint.java:134)
	at
com.ibm.websphere.jaxrs.server.IBMRestServlet.handleRequest(IBMR
estServlet.java:149)
	at
com.ibm.websphere.jaxrs.server.IBMRestServlet.doDelete(IBMRestSe
rvlet.java:134)
	at
javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
	at
com.ibm.websphere.jaxrs.server.IBMRestServlet.service(IBMRestSer
vlet.java:99)
	at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
apper.java:1290)
	at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser
vletWrapper.java:778)
	at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser
vletWrapper.java:475)
	at
com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters
(WebAppFilterManager.java:1161)
	at
com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:
4978)
	at
com.ibm.ws.webcontainer31.osgi.webapp.WebApp31.handleRequest(Web
App31.java:528)
	at
com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.handleRequest(
DynamicVirtualHost.java:315)
	at
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.
java:1014)
	at
com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.run(DynamicVir
tualHost.java:280)
	at
com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink$T
askWrapper.run(HttpDispatcherLink.java:967)
	at
com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink.w
rapHandlerAndExecute(HttpDispatcherLink.java:359)
	at
com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink.r
eady(HttpDispatcherLink.java:318)
	at
com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.handleD
iscrimination(HttpInboundLink.java:471)
	at
com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.handleN
ewRequest(HttpInboundLink.java:405)
	at
com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.process
Request(HttpInboundLink.java:285)
	at
com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.ready(H
ttpInboundLink.java:256)
	at
com.ibm.ws.tcpchannel.internal.NewConnectionInitialReadCallback.
sendToDiscriminators(NewConnectionInitialReadCallback.java:174)
	at
com.ibm.ws.tcpchannel.internal.NewConnectionInitialReadCallback.
complete(NewConnectionInitialReadCallback.java:83)
	at
com.ibm.ws.tcpchannel.internal.WorkQueueManager.requestComplete(
WorkQueueManager.java:504)
	at
com.ibm.ws.tcpchannel.internal.WorkQueueManager.attemptIO(WorkQu
eueManager.java:574)
	at
com.ibm.ws.tcpchannel.internal.WorkQueueManager.workerRun(WorkQu
eueManager.java:929)
	at
com.ibm.ws.tcpchannel.internal.WorkQueueManager$Worker.run(WorkQ
ueueManager.java:1018)
	at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
utor.java:1153)
	at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
cutor.java:628)
	at java.lang.Thread.run(Thread.java:785)

Problem conclusion

Additional synchronization has been added to ensure correct
placement of the resource class.

The fix for this APAR is currently targeted for inclusion in fix
pack 17.0.0.3.  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
PI82364
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-05-31
Closed date
2017-07-04
Last modified date
2017-07-04

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
LIBERTY PROFILE
Fixed component ID
5724J0814

Applicable component levels

RCD0 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":"CD0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI82364: For JAX-RS 2.0, a request may fail with a 404 because a resource class was incorrectly indicated as not found.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

RCD0 PSY

Document Information

Share your feedback

Need support?