4 Replies Latest reply: Feb 4, 2011 5:03 AM by 803630 RSS

    OSB Error codes

    803630
      What OSB error codes,I have to handle in the error handler stage when a route node finds that the given end point is not available and also when the end system is timing out.

      Is it BEA-38000?

      Thanks.
        • 1. Re: OSB Error codes
          AbhishekJ
          Here is a list of groups of error codes:
          http://download.oracle.com/docs/cd/E17904_01/apirefs.1111/e15034/toc.htm
          Click on the first group and you will be able to check the details of each transport error code.
          • 2. Re: OSB Error codes
            803630
            I could not find any timeout related errors here.

            Thanks.
            • 3. Re: OSB Error codes
              AbhishekJ
              You should test various scenarios in your setup and check which errors you get in different scenarios. There can be many and the error codes will depend on type of transport as well (HTTP, FTP, FIle etc)

              In case of Server found but service not available, you should get BEA-380000 error code with Not Found in description:
              <con:fault       xmlns:con="http://www.bea.com/wli/sb/context">
                   <con:errorCode>BEA-380000</con:errorCode>
                   <con:reason>Not Found</con:reason>
                   <con:location>
                   <con:node>RouteNode1</con:node>
                   <con:path>response-pipeline</con:path>
                   </con:location>
                   </con:fault>
              In case server not running on same port:
              <con:fault       xmlns:con="http://www.bea.com/wli/sb/context">
                   <con:errorCode>BEA-380000</con:errorCode>
                   <con:reason>General runtime error: Socket Closed</con:reason>
                   <con:location>
                   <con:node>RouteNode1</con:node>
                   <con:path>request-pipeline</con:path>
                   </con:location>
                   </con:fault>
              In case of Timeout set on Business Service triggering (Target service still processing and Socket gets closed because of preconfigured timeout value on BS), you should get BEA-380000 error code with SocketTimeOut exception stacktrace in Description.
              <con:fault       xmlns:con="http://www.bea.com/wli/sb/context">
                   <con:errorCode>BEA-380000</con:errorCode>
                   <con:reason>
                   [WliSbTransports:381304]Exception in HttpOutboundMessageContext.RetrieveHttpResponseWork.run: java.net.SocketTimeoutException
              java.net.SocketTimeoutException
               at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse$SocketTimeoutNotification.&lt;clinit>(AsyncResponseHandler.java:551)
               at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse.handleTimeout(AsyncResponseHandler.java:396)
               at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse.timeout(AsyncResponseHandler.java:502)
               at weblogic.socket.SocketMuxer$TimerListenerImpl.timerExpired(SocketMuxer.java:1052)
               at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
               at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
               at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
               at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
                   </con:reason>
                   <con:location>
                   <con:node>RouteNode1</con:node>
                   <con:path>response-pipeline</con:path>
                   </con:location>
                   </con:fault>
              In case of Timeout while obtaining connection to remote server:
                   
                   <con:fault       xmlns:con="http://www.bea.com/wli/sb/context">
                   <con:errorCode>BEA-380000</con:errorCode>
                   <con:reason>General runtime error: connect timed out</con:reason>
                   <con:location>
                   <con:node>RouteNode1</con:node>
                   <con:path>request-pipeline</con:path>
                   </con:location>
                   </con:fault>
              • 4. Re: OSB Error codes
                803630
                Thanks a Lot........