Add Logging Capability to Coherence REST Server-Side for Exceptions when REST Service Returns Status Bad Request 400 (Doc ID 2825532.1)

Last updated on DECEMBER 07, 2022

Applies to:

Symptoms

In a 14c cluster environment, the REST-based coherence proxy does not work in a scenario as explained below. The user needs a REST-based proxy to access coherence caches. It works that the same JVM for caches and proxy process too, otherwise not. In the user's requirement, cache servers to store data and a different cache server started defining the REST proxy. With that configuration, GET requests run OK except when includes a "where" clause. When needs a "where", always obtain "Bad request" and there is no log related to it why the request was a 'bad request'.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.