On a real productive with higher degree of complexity the situation can be much worse.
This API should be heavily tuned, Jresey should never or rarily be spotted during thread dump sampling of the deployment of an application.
In this case, we are dealing with WeldBoostrap which is a process of much higher complexity than checking if an annotated class is related to JAX-RS, and the code from WeldBoostrap barely registers in the thread dumps, if not for Jersey.
99sono
commented
6 years ago
Hi, In weblogic 12.2.1.2, Jersey and the: CdiComponentProvider.isJaxRsComponentType
Is throttling deployment speed. We have an application where this annotated beans obverver is responsible for more than 7 seconds of deployment time.
The following sample application with 4999 beans is able to demonstrate, if a Thread Dump is taken every second, that the deployBeans phase is being slowed down by jersey. https://github.com/99sono/wls-jsf-2-2-12-jersey-weldstartup-bottleneck
On a real productive with higher degree of complexity the situation can be much worse.
This API should be heavily tuned, Jresey should never or rarily be spotted during thread dump sampling of the deployment of an application.
In this case, we are dealing with WeldBoostrap which is a process of much higher complexity than checking if an annotated class is related to JAX-RS, and the code from WeldBoostrap barely registers in the thread dumps, if not for Jersey.
NOTE: Oracle has been made aware of this issue.
Kindest regards.