<Warning> <JAXRSIntegration> <BEA-2192509> <Changing Servlet Class WLS 12.2.2 - JAXRSINTEGRATION Warning Being Thrown on Starting WLS
Last updated on DECEMBER 20, 2017
Applies to:Oracle Financial Services Revenue Management and Billing - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
On RMB v126.96.36.199.0, we are getting below error in native installation:
com.sun.jersey.spi.container.servlet.ServletContainer (web.xml) to org.glassfish.jersey.servlet.ServletContainer.>
Following versions of Weblogic Server and Java used in the environment:
- WebLogic Server 188.8.131.52.0 Mon Oct 3 04:35:36 PDT 2016 1827450
- java version "1.8.0_144"
- Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
- Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)
Following bug addressed similar issue against Weblogic version 12.2.1 where it was due to usage of Jersey 1 by some applications.
Bug 21621556 : WLS 12.2.2 - JAXRSINTEGRATION WARNING BEING THROWN ON STARTING WLS
Some application is using Jersey 1 on the server side. That is not supported any more and WLS does not even contain Jersey 1 server
runtime. Message states that the "jersey 1 servlet implementation class, referenced from web.xml was replaced by jersey 2 servlet implementation class."
Based on it, User tried a brand new install expecting to replicate the issue. Now when starting up the native installation, below error is occurring:
"Cannot add Jersey servlet for application class
com.sun.jersey.api.core.ResourceConfig because ApplicationPath annotation is not set on it."
Note that we found same installation is working fine with Web Logic v12.1.3 with default installation.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms