Hi Remsy
> 2008-09-23 09:00:06,792 [127.0.1.1-ubuntu] [HttpServerWorker-13]  INFO 
> LogMediator To: http://localhost:8280/soap/Transformer,MessageID: 
> urn:uuid:1CA76505829CE3EE4A1222174807357,Direction: request
> 2008-09-23 09:00:07,812 [127.0.1.1-ubuntu] [HttpClientWorker-1]  INFO 
> LogMediator To: , MessageID: 
> urn:uuid:1EB40901883271FB4D1222174746812073009-1951864453, Direction: 
> request, MESSAGE = Executing default "fault" sequence, ERROR_CODE = 00000, 
> ERROR_MESSAGE = Connection timeout, Envelope: <?xml version='1.0' 
> encoding='utf-8'?><soapenv:Envelope 
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";><soapenv:Body><ax:text
>  xmlns:ax="http://ws.apache.org/commons/ns/payload";>SAMPLE 
> MESSAGE</ax:text></soapenv:Body></soapenv:Envelope>
>
> So the connection from the mediator to the proxy service is timiming out. is 
> there a way to fix this ?
>   
This is not an "Abnormal connection close".. in this case, "we" (i.e. 
the ESB side) close the TCP socket after our TCP socket timeout expired. 
For the ESB 1.7 and 1.7.1 versions, the socket timeout is fixed by a 
properties file you drop into the classpath

e.g. create a file named nhttp.properties with the following line (which 
specifies the socket timeout in milli seconds). Drop this file into 
wso2esb-1.7/webapp/WEB-INF/classes/conf

http.socket.timeout=60000

asankha

_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Reply via email to