OSB Fails when Inbound HTTPS Call is Routed as HTTP Call (Doc ID 1092053.1)

Last updated on NOVEMBER 03, 2016

Applies to:

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

Symptoms

You have Oracle HTTP Server (OHS) and Oracle service Bus (OSB) 10.3.1 configured. In OSB 10.3.1 you have an HTTP proxy and you would like to implement the following scenario:

client ------https---->OHS----http--->OSB

When the client submits a request to access the  proxy WSDL using the above configuration, the following error is returned.

"Error 500--Internal Server Error
Cannot process inbound request to endpoint ProxyService default/Checking the Behavior. over https"

The OSB log will carry the below error message.

<Feb 23, 2010 7:12:06 PM EST> <Error> <HTTP> <BEA-101017>
<[weblogic.servlet.internal.WebAppServletContext@1cfbe29 - appName: 'XBus Kernel', name: 'EstimatedDischarge/ProxyServices/EstimatedDischarge', context-path: '/EstimatedDischarge/ProxyServices/EstimatedDischarge',spec-version: 'null', request:
weblogic.servlet.internal.ServletRequestImpl@16dd08a[GET /EstimatedDischarge/ProxyServices/EstimatedDischarge?WSDL HTTP/1.1
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8)
Gecko/20100202 Firefox/3.5.8 GTB6 (.NET CLR 3.5.30729)
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Cookie:
ADMINCONSOLESESSION=cXl2LGtVmQhDY8QL7YmlkcCKJj4Nc9ZGBGWtJ92ny4RQnVGwR9H6!-1876841619; _WL_AUTHCOOKIE_ADMINCONSOLESESSION=URobdW1jivjVfEL[5eSi;
WINDOW_JSP_ID=Projects_ProjectDetail; WINDOW_X_PO
S=0; WINDOW_Y_POS=0
Connection: Keep-Alive
Proxy-Client-IP: localhost
X-Forwarded-For: localhost
X-WebLogic-KeepAliveSecs: 30
X-WebLogic-Force-JVMID: -1876841619

]] Root cause of ServletException.
javax.servlet.ServletException: Cannot process inbound request to endpoint ProxyService default/Checking the Behavior. over https
at com.bea.wli.sb.transports.http.HttpTransportServlet$RequestHelper.enforceSecurity(HttpTransportServlet.java:360)
at com.bea.wli.sb.transports.http.HttpTransportServlet$RequestHelper.service(HttpTransportServlet.java:207)
at com.bea.wli.sb.transports.http.HttpTransportServlet.service(HttpTransportServlet.java:133)
at weblogic.servlet.FutureResponseServlet.service(FutureResponseServlet.java:24)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
Truncated. see log file for complete stacktrace



Available workarounds:
---------------------
Configure the proxy service with the HTTPS transport. Even though the message comes over the non-SSL  port from the Web server, OSB recognizes that the message originally used the HTTPS protocol and  accepts the message as an HTTPS message. The SSL port in the OSB domain must be enabled to do this, even though it is not used in this scenario.

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