BEA-380000 Error : Thread loss ?
Hi
Information:
My proxy message flow:
1. Proxy calls business service. Business service response is transformed and returned to client.
2. If business service call fails, then proxy writes to database with comment "EmployeeID_Failed". (EmployeeID is in request which I store to variable EMPID). Then it returns error response to client.
I have set read timeout 200 and connection timeout 60 for the business service. That's enough I guess.
===============================================================================================================
Problem:
Problem is when backend service is overloaded with requests from other clients it returns the following -
<con:fault>
<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.<clinit>(AsyncResponseHandler.java:551)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
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:985)
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:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)</con:reason>
<con:location>
<con:node>To Backend Busines service</con:node>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault>
And nothing is written to DB!! Request volume is in thousands and hence I am not able to confirm if the response was returned to client or not as well.
===============================================================================================================
Observations: Returned response body content after timeout error is empty. Header content is also empty.
===============================================================================================================
My question is - is there any thread loss involved due to BEA-380000?
-s-k