5/9/2023 0 Comments Pritunl connection timed outSee ĥ) Another suggestion is setting the ConnectTimeout too to see if these work with a higher value. Update: One more thing we wanted to, but did not complete is to create a static route between client and server to reduce the number of hops in between and ensure no network related connection drops. Someone knowledgable enough could run snoopģ) Is there a max number of requests configured/restricted on the server - and is that throttling your connections?Ĥ) Are there any intermediate load balancers at which requests could be dropped? And once we understand which end is terminating the connection is to look at why. ![]() If it shows the same size of response, then you have a (may be not plausible) condition that the server actually responded correctly but the client did not get the response back because the connection terminated somewhere in between.Ģ) The network admin teams looked at the TCP/IP traffic to determine which end (or intermediate router) is terminating the HTTP / TCP-IP conversation. Update: If the client always gets a 200, then the server has actually sent back some response but I suspect the response byte-size (if this is recorded in the access logs) will show a different value from that of the normal response size for that request. If it's a firewall issue, we would get a Connection Refused or the SocketTimeout exception.ġ) Are you able to track these requests in the access log on the server - do they show an HTTP status 200 or 404 or something else? In our case, the server (IIS in this case) logs showed the client closed the connection and not the server. Have not fixed it yet but this is the steps we went through. Usually at high load and not easy to reproduce on test. We have come across these in a similar case to yours. Also, other apps running on the same network have not reported similar issues.ĭoes anyone have any idea what the cause of this could be, or even what I should investigate? but that doesn't make much sense to me given that the request is clearly getting through to the servlet. Given what I've been able to find so far about : Connect timed out, I wondered if it weren't some network or firewall issue on the network our servers are running on. The thing is, I have no idea how any of this could be happening, especially given that it only happens occasionally (no clear pattern of activity that I can tell) and even then only when there's (relatively) high latency between the client and the server. In case it helps, here are the calls being made on the HttpsURLConnection prior to the call to getOutputStream() (edited to show only the calls being made rather than the whole structure of the code doing this): HttpsURLConnection conn = (HttpsURLConnection) url.openConnection() Ĭonn.setRequestProperty("Cookie", cookie) Ĭonn.setRequestProperty("Content-Type", "application/x-java-serialized-object") On the server side, an EOFException is thrown in ObjectInputStream's constructor, which tries to read the serialization header but fails because the client never gets the OutputStream to write to.Also, when this happens I am able to call conn.getResponseCode() and I get a response code of 200. ![]() Note that this is not a SocketTimeoutException, which the connect() method on HttpURLConnection says it throws if the timeout expires before a connection can be established. ![]() : Connection timed out: connectĪt (Native Method)Īt (Unknown Source)Īt (Unknown Source)Īt (Unknown Source)Īt (Unknown Source)Īt (Unknown Source)Īt .(Unknown Source)Īt .(Unknown Source)Īt (Unknown Source)
0 Comments
Leave a Reply. |