"com.bea.wli.sb.pipeline.PipelineException: Transport error (error code=BEA-380000): Bad Request" SSL Communication Failure from ALSB to External Service When OEM Agent is Enabled
(Doc ID 1186834.1)
Last updated on DECEMBER 15, 2023
Applies to:
Oracle Service Bus - Version 3.0 and laterInformation in this document applies to any platform.
Symptoms
When Oracle Enterprise Manager (OEM) Agent is enabled on a Oracle Service Bus domain, an external (.net) webservice is rejecting the requests. The issue occurs only when the OEM agent is enabled.
Exception:
####<May 17, 2010 4:17:22 PM EDT> <Debug> <AlsbPipeline> <hpfh3n01.ddmi.intra.renhsc.com> <extServBusUat11> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1274127442879> <BEA-000000> <MIRetailers/CreditCard/ProxyService/CreditCardProxyService: Unhandled error caught by system-level error handler
com.bea.wli.sb.pipeline.PipelineException: Transport error (error code=BEA-380000): Bad Request
at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:79)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:871)
at com.bea.wli.sb.pipeline.Router.processMessage_aroundBody0(Router.java:191)
at com.bea.wli.sb.pipeline.Router.processMessage_aroundBody1$advice(Router.java:546)
at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:1)
at com.bea.wli.sb.pipeline.MessageProcessor.processResponse(MessageProcessor.java:149)
at com.bea.wli.sb.pipeline.RouterCallback.onError(RouterCallback.java:137)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.onError(LoadBalanceFailoverListener.java:349)
at com.bea.wli.sb.transports.http.HttpOutboundMessageContext$RetrieveHttpResponseWork.handleResponse(HttpOutboundMessageContext.java:819)
at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse$RunnableCallback.run(AsyncResponseHandler.java:531)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute_aroundBody0(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.execute_aroundBody1$advice(ExecuteThread.java:176)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:1)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
com.bea.wli.sb.pipeline.PipelineException: Transport error (error code=BEA-380000): Bad Request
at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:79)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:871)
at com.bea.wli.sb.pipeline.Router.processMessage_aroundBody0(Router.java:191)
at com.bea.wli.sb.pipeline.Router.processMessage_aroundBody1$advice(Router.java:546)
at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:1)
at com.bea.wli.sb.pipeline.MessageProcessor.processResponse(MessageProcessor.java:149)
at com.bea.wli.sb.pipeline.RouterCallback.onError(RouterCallback.java:137)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.onError(LoadBalanceFailoverListener.java:349)
at com.bea.wli.sb.transports.http.HttpOutboundMessageContext$RetrieveHttpResponseWork.handleResponse(HttpOutboundMessageContext.java:819)
at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse$RunnableCallback.run(AsyncResponseHandler.java:531)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute_aroundBody0(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.execute_aroundBody1$advice(ExecuteThread.java:176)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:1)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
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 |