Calls Made To JMS Business Service Through Local Proxy Throws Exception "java.lang.NullPointerException at com.bea.wli.sb.service.handlerchain.handlers.OutboundResponseMetadataHandler.getResponseMetadata"

(Doc ID 2275398.1)

Last updated on AUGUST 09, 2017

Applies to:

Oracle Service Bus - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

When a JMS BS is called through local proxy from another proxy service, it throws the following exception in the log.  There is no transaction loss, only the logs filled with the below exception trace for every call.

ERROR
-----------------------
#### <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <>  java.lang.NullPointerException.
java.lang.NullPointerException
  at com.bea.wli.sb.service.handlerchain.handlers.OutboundResponseMetadataHandler.getResponseMetadata(OutboundResponseMetadataHandler.java:86)
  at com.bea.wli.sb.service.handlerchain.handlers.OutboundResponseMetadataHandler.handleResponse(OutboundResponseMetadataHandler.java:45)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$1.handleResponse(AbstractHandler.java:307)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleResponse(AbstractHandler.java:139)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$1.handleResponse(AbstractHandler.java:307)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleResponse(AbstractHandler.java:139)
  at com.bea.wli.sb.service.handlerchain.handlers.ResultCachingHandler.handleResponse(ResultCachingHandler.java:148)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$1.handleResponse(AbstractHandler.java:307)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleResponse(AbstractHandler.java:139)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$1.handleResponse(AbstractHandler.java:307)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleResponse(AbstractHandler.java:139)
  at com.bea.wli.sb.service.handlerchain.handlers.OutboundMessageContentHandler.handleResponse(OutboundMessageContentHandler.java:89)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$1.handleResponse(AbstractHandler.java:307)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleResponse(AbstractHandler.java:139)
  at com.bea.wli.sb.service.handlerchain.handlers.LoadBalanceFailover$LoadBalanceFailoverHelper.handleResponse(LoadBalanceFailover.java:475)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleResponse(AbstractHandler.java:139)
  at com.bea.wli.sb.service.handlerchain.handlers.UpdateOutboundStatistics.handleResponse(UpdateOutboundStatistics.java:89)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$1.handleResponse(AbstractHandler.java:307)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleResponse(AbstractHandler.java:139)
  at com.bea.wli.sb.service.handlerchain.handlers.EndpointManagementHandler.handleResponse(EndpointManagementHandler.java:122)
  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$1.handleResponse(AbstractHandler.java:307)
  at com.bea.wli.sb.service.handlerchain.handlers.TransportProviderInvoker$ServiceTransportListener.onReceiveResponse(TransportProviderInvoker.java:302)
  at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext$PostJmsAckWork.run(JmsOutboundMessageContext.java:1052)
  at weblogic.work.WorkAreaContextWrap.run(WorkAreaContextWrap.java:55)
  at weblogic.work.ContextWrap.run(ContextWrap.java:40)
  at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:194)
  at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:548)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Call a JMS Based BS through Local proxy from another proxy (http)
 

Cause

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