Community
Participate
Working Groups
Created attachment 197943 [details] exceptions on client disconnect (it seems to me that the second exception is a subsequent fault) Build Identifier: 3.7.0.201106071621, Build id: 20110607-1621 Client disconnects causes some exceptions in "ServiceTunnelServlet.doPost" (see attachment). The comments in the catch-block state that these exceptions should be ignored, but they don't. Reproducible: Always Steps to Reproduce: 1. Browse a LookupCall-SmartField (a longer taking call suits best) 2. Click the SmartField-DropDown away (which closes the connection) 3. Voilà, you can find the exceptions in the server log
//ignore disconnect errors // we don't want to throw an exception, if the client closed the connection Throwable cause = t; while (cause != null) { if (cause instanceof SocketException) { return; } else if (cause.getClass().getSimpleName().equalsIgnoreCase("EofException")) { return; } else if (cause instanceof InterruptedIOException) { return; } // next cause = cause.getCause(); }
shipped with scout 3.7.1