wicket-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Grigorov <mgrigo...@apache.org>
Subject Re: ResponseIOException
Date Wed, 21 Dec 2016 08:01:17 GMT

There are no known memory related issues with Wicket 1.5.x!

The best way to debug out of memory issues is to create heap dumps just
after starting the application and another when the OOM occurs with
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<path to dump file>.

ResponseIOException is not related. It occurs when the browser closes the
connection before the server has the chance to write the response back to

Martin Grigorov
Wicket Training and Consulting

On Wed, Dec 21, 2016 at 3:28 AM, durairaj t <durairaj.tha@gmail.com> wrote:

> I'm migrating my application to wicket7.x, but it is still running in
> wicket1.5  in production and logging following error frequently and
> throwing OutOfMemoryError later. I'm still analyzing wicket1.5 code for the
> root cause of the memory leakage.
> Is it an existing error with the wicket1.5.x? did any one faced this error
> in wicket1.5 and got solution for this?
> I found  a problem ticket in JIRA for this issue,  "
> https://issues.apache.org/jira/browse/WICKET-3869", but I did not find any
> solution in it.
> Error:
> org.apache.wicket.DefaultExceptionMapper]  Connection lost, give up
> responding.: org.apache.wicket.protocol.http.servlet.ResponseIOException:
> ClientAbortException:  java.io.IOException: JBWEB002012: Socket write
> failed
> Server details:
> JVM Arguments: -D[Standalone] -XX:+UseCompressedOops -Xms2048m -Xmx2048m
> -XX:MaxPermSize=512m
> jdk1.7.0_75
> JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8)
> Browser IE 11 running in compatibility mode IE 7.
> Any help?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message