Skip to Main Content

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Internal Server Error

Mark ReichmanSep 2 2014 — edited Sep 15 2014

OSB 12.1.3

JDEV 12.1.3

Implementation:  Proxy Service -> pipeline(request side has service callout) -> route -> Business Service

When I run from the proxy I get the errors below.

When run from the pipeline the message body coming back on the pipeline response side looks fine.  The only difference in the body on the pipeline response side, as opposed to a direct response from the web service using SOAPUI, is the OSB moves the namespaces around to the soap body from the soap envelope and has "http://schemas.xmlsoap.org/soap/envelope/" twice (envelope, body) with two different predicates (soapenv, soap).  Not sure why the OSB is doing this, but it is valid xml and should be OK.   Is this the reason I'm getting OSB-380001 Internal Server Error when run from the proxy because the proxy/WSDL is not expecting this?  When I run from the pipeline I don't get an error basically everything works roundtrip to the pipeline response side.  This namespace is the only difference I can find.  If I just have a proxy and a business service with no pipeline everything works fine round trip.  Or, maybe the issue is something else entirely...

Here is what the response SOAP BODY looks like when SOAPUI directly connects to the web service - no OSB:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

   <soap:Body>

      <GetSubItemListAsOfResponse xmlns="http://prosight.com/type/Portfolios/5.0/psPortfoliosSubItem">

         <GetSubItemListAsOfResult>

            <psPortfoliosSubItemInfo>

               <SubItemType>Highway Segments</SubItemType>

Here is what the response SOAP body looks like if I go through the OSB on the pipeline response side:

<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header/>
<soap:Bodyxmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<GetSubItemListAsOfResponsexmlns="http://prosight.com/type/Portfolios/5.0/psPortfoliosSubItem">
<GetSubItemListAsOfResult>
<psPortfoliosSubItemInfo>
<SubItemType>Highway Segments</SubItemType>

When run from the proxy in OSB I get these errors.  First is JDev message log and second is osb response document error when run from proxy.

The application can be accessed at location:

http://127.0.0.1:7101/lwpfconsole/LoginRedirectServlet?p1=d2VibG9naWM=&p2=QHBwbGVwaWU=&page=test_console&rtc_resourcetype=ProxyService&rtc_resourcename=OppmGis%2FProxyServices%2FpsPortfoliosSubItemSPS

<com.bea.alsb.common.catalog.CatalogLogger> <CatalogLogger> <log> <OSB-382191>

com.bea.wli.sb.pipeline.PipelineException: Transport error (error code=OSB-380001): Internal Server Error

  at com.bea.wli.sb.pipeline.components.Node.processMessage(Node.java:94)

  at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:905)

  at com.bea.wli.sb.pipeline.components.Router.processMessage(Router.java:205)

  at com.bea.wli.sb.pipeline.MessageProcessor.processResponse(MessageProcessor.java:228)

<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>OSB-380001: Internal Server Error</faultstring>
<detail>
<con:faultxmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>OSB-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>

...

This post has been answered by Mark Reichman on Sep 12 2014
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Oct 10 2014
Added on Sep 2 2014
16 comments
17,669 views