OSB Proxy Service does not want to display on the browser
OpholaNov 9 2010 — edited Nov 19 2010Hi guys, can you please help with this one
I have created a business service that calls a webservice tha is housed inside my weblogic domain. The business service is then called by a proxy service. The business and the proxy service make use of the same wsdl that ensures that they both comform to the structure of the soap envelope.
When I debug both the business and the proxy service from inside the osb console, I get a positive result. Now the problem arises when I call the proxy service directly from the browser, I get a BEA-380001 error. http://localhost:8001/ProxServiceProj/RicaPS
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>BEA-380001: Internal Server Error</faultstring>
<detail>
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380001</con:errorCode>
<con:reason>Internal Server Error</con:reason>
<con:location>
<con:node>RouteNode1</con:node>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
The proxy service has a route node that routes to the business service. I did not do anything that will affect the response, so there are no request actions or response actions. I have even tried adding a pipeline pair that has a stage on the response, this stage does nothing though as I do not know what to do with it.
Based on the information I have gathered from the net, it might be a transport header problem, that is related to the response-pipeline. So does anyone know what the potential problem could be? Is there anything that I was supposed to do?
O..