[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-884) HTTP transport barfs in stress tests with read timed out

HTTP transport barfs in stress tests with read timed out -------------------------------------------------------- Key: JBMESSAGING-884 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-884 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.CR1 Reporter: Tim Fox Assigned To: Ron Sigal Fix For: 1.2.1 When running the stress tests. e.g. StressTest:testQueueMultipleSenders() The HTTP transport intermittently barfs with: Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:327) at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:133) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) at org.jboss.remoting.Client.invoke(Client.java:1538) at org.jboss.remoting.Client.invoke(Client.java:527) at org.jboss.remoting.Client.invoke(Client.java:515) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:182) ... 19 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read1(BufferedInputStream.java:256) at java.io.BufferedInputStream.read(BufferedInputStream.java:313) at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:606) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:554) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:939) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:274) ... 25 more This only occurs under high load. I suspect the server side tomcat server is having problems dealing with so many concurrent poll requests and times them out.