Calling wso2 data services WS from wso2 ESB 1.7.1 timeouts

Hi Steve >... then the second call seems to block and timeout ("A connection that was expected to be kept alive was closed by the server") Seems like a low level problem.. what is the exact version of your JDK? Is it the Sun JDK? Also, post the full stack trace of the error cheers asankha http://adroitlogic.org

Hi, I am using java 5.0 update 17 for both the ESB and the Data services. Java itself reports no error, and while it is blocking it uses no java runtime processor or excessive memory. Looking at the logs, the ESB receives the request but never forwards it on to the data services server. "The underlying connection was closed: A connection that was expected to be kept alive was closed by the server." This error is the one reported back by the .NET runtime when the ESB closes the connection so the stack trace that goes with this error only relates to my test client. Steve

Steve Is this a GET request by any chance? You will need to share more/all information to find whats going wrong. Please post the synapse.xml and any other material. Also, can you run the sample web service (i.e. the SimpleStockQuoteService) and the ESB on the same machine and load test it? Refer to : http://wso2.org/library/1721 and the other related performance testing articles for some background on some of the perf tests carried out sometime back. cheers asankha http://adroitlogic.org

Hi, This is a SOAP 1.1 request. If I proxy to a standard .NET WS then performance is pretty good and there is no timeouts at all. <?xml version="1.0" encoding="UTF-8"?> <syn:definitions xmlns:syn="http://ws.apache.org/ns/synapse">     <syn:registry provider="org.wso2.esb.registry.WSO2Registry"/>     <syn:proxy name="DataTestProxy" transports="http" startOnLoad="true">         <syn:target>             <syn:endpoint>                 <syn:address uri="http://localhost:9762/services/SteveService.SteveServiceHttpSoap11Endpoint/"/>             </syn:endpoint>             <syn:inSequence>                 <syn:log level="full" separator=","/>             </syn:inSequence>             <syn:outSequence>                 <syn:send/>             </syn:outSequence>         </syn:target>         <syn:publishWSDL uri="http://localhost:9762/services/SteveService?wsdl"/>     </syn:proxy>     <syn:sequence name="fault">         <syn:log/>     </syn:sequence>     <syn:sequence name="main">         <syn:in>             <syn:log level="full"/>             <syn:filter source="get-property('To')" regex="http://localhost:9000.*">                 <syn:send/>             </syn:filter>         </syn:in>         <syn:out>             <syn:send/>         </syn:out>     </syn:sequence> </syn:definitions> <?xml version="1.0" encoding="UTF-8"?> Interestingly I have just relocated the esb to an old windows XP box and set up the proxy again and it's now working. Seems like it's either an issue with the ESB and data services being on the same server, a linux/FC6 or a VMWare issue. I will relocate the data services to the same XP box as well and see if the problem re-surfaces. Steve

Hi Steve > Interestingly I have just relocated the esb to an old windows XP box and set up the proxy again and it's now working. I have seen such issues with old Sun OS (I think 5.6), IBM JVMs etc.. and sometimes its when connecting to the same machine Commonly this is a FC6/JVM issue.. cheers asankha http://adroitlogic.org