My Oracle Support Banner

ALSB 2.1 - throws HttpOutboundMessageContext.RetrieveHttpResponseWork.run: java.lang.NullPointerException (Doc ID 976326.1)

Last updated on APRIL 14, 2021

Applies to:

Oracle Service Bus - Version 2.1 to 2.6.1RP [Release Aqualogic Service Bus]
Information in this document applies to any platform.

Symptoms

ALSB throws a NullPointerException instead of a meaningful Exception.

In com.bea.wli.sb.transports.http.HttpOutboundMessageContext.getResponse(), we didn't check _urlConn==null.
Sometimes, _urlConn can be null if this function is called from the callbacks and the socket is closed.
In this case, you see the NPE being propagated to the client in the $fault variable. 

We need to provide a more meaningful message to the $fault variable, even though the exception details are being logged in the log file.

HttpOutboundMessageContext.RetrieveHttpResponseWork.run:
 java.lang.NullPointerException
 at  com.bea.wli.sb.transports.http.HttpOutboundMessageContext.getResponse(HttpOutboundMessageContext.java:476)
 at  com.bea.wli.sb.transports.http.HttpOutboundMessageContext.access$000(HttpOutboundMessageContext.java:45)
 at  com.bea.wli.sb.transports.http.HttpOutboundMessageContext$RetrieveHttpResponseWork.handleResponse(HttpOutboundMessageContext.java:731)
 at  weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse$RunnableCallback.run(AsyncResponseHandler.java:495)


 


Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


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