java.lang.NoSuchFieldException on inputStream is flooding the agent log :[ERROR] [IntroscopeAgent.HttpURLConnectionTracerHelper] Unable to get inputStream: java.lang.NoSuchFieldException: inputStream

Document ID : KB000045179
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem:

After enabling Agent v10. java.lang.NoSuchFieldException on inputStream is flooding the agent log :
[ERROR] [IntroscopeAgent.HttpURLConnectionTracerHelper] Unable to get inputStream: java.lang.NoSuchFieldException: inputStream

Configuration: Weblogic 10.3.5.0 version, 11.1.1 SOA

Cause:

The application uses Oracle Containers for J2EE (OC4J) and the HTTPClient.HttpURLConnection used in oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection implementation does not have the inputStream field that HttpURLConnectionBackendTracer attempt to retrieve as per default agent configuration.

Workaround:

Commenting out the following line in wily/core/config/httpbackendmetrics.pbd to avoid triggering java.lang.NoSuchFieldException on inputStream and flooding the agent log with too many such error/exception:

#TurnOn: HttpURLConnectionBackendTracing

NOTE: If HttpURLConnectionBackendTracing is disabled, the agent will not be able to collect metrics from instrumenting getInputStream() for metric path "Backends|WebService at {protocol}_//{host}_{port}|Paths|{path}".  You could try customizing instrumentation on different classes/methods to make up for the missing backend visibility since the OOTB tracing specification doesn't support this particular application's implementation.