Closed GoogleCodeExporter closed 9 years ago
The real problem is this:
"Caused by: ClientAbortException: java.net.SocketException: Software caused
connection abort: socket write error"
This error message generally means that the end that reported the error tried
to write data, but the other end has already closed the connection.
It can easily be reproduced by hitting F5 in browser in "hammer" mode. This
problem is harmless for both: client and server and there little that can be
done, unless you want to make those logs less verbose..
Closing the issue with WONTFIX resolution. Feel free to reopen it if you don't
agree.
Original comment by alex.obj...@gmail.com
on 30 Aug 2012 at 11:47
Thank you for reply.
So I want to suppress logs since it's too verbose.
Is the following setting reasonable solution?
log4j.logger.ro.isdc.wro.http.WroFilter=FATAL
Original comment by h.shiros...@gmail.com
on 30 Aug 2012 at 12:39
I would recommend using:
log4j.logger.ro.isdc.wro.http.WroFilter=NONE
Btw, I can suppress that log in next release.
Will change the title and description of this issue.
Original comment by alex.obj...@gmail.com
on 30 Aug 2012 at 12:42
Fixed in branch 1.4.x
Original comment by alex.obj...@gmail.com
on 30 Aug 2012 at 2:26
Thank you for fix.
BTW `log4j.logger.ro.isdc.wro.http.WroFilter=NONE`
didn't work for me. Log output was not suppressed. DEBUG level log was also
shown.
I'll use `log4j.logger.ro.isdc.wro.http.WroFilter=FATAL` for now.
Original comment by h.shiros...@gmail.com
on 31 Aug 2012 at 1:27
Issue 540 has been merged into this issue.
Original comment by alex.obj...@gmail.com
on 6 Sep 2012 at 8:21
Original issue reported on code.google.com by
h.shiros...@gmail.com
on 30 Aug 2012 at 12:45