Hello,
Our test environment configuration is the following:
- JBoss 4.2.2 GA;
- Jersey 1.1.5 ( jersey-client-1.1.5-ea-SNAPSHOT.jar,
jersey-core-1.1.5-ea-SNAPSHOT.jar, jersey-fastinfoset-1.1.5-ea-SNAPSHOT.jar,
jersey-json-1.1.5-ea-SNAPSHOT.jar, jersey-server-1.1.5-ea-SNAPSHOT.jar,
jersey-spring-1.0.1-SNAPSHOT.jar, jettison-1.0.1.jar)
- Spring 2.5.5;
We're having a weird exception on our test environment. Jersey logs error
that starts as: "ClientAbortException: java.net.SocketException: Broken
pipe." (bigger print-out can be found attached
http://n2.nabble.com/file/n3859286/server.log server.log ).
And what is more, logging does not stop (in my case the log file grew
400MB in minutes). Had to roughly re-start the server.
We have saw this error as well on 1.0.3 and thought that moving to 1.1.5
would solve the problem.
I have also seen similar error on Atlassian Jira
(
http://jira.atlassian.com/browse/JRA-15405). What they did is simply caught
and quietened the exception.
The questions are:
- what might have caused this exception to get infinitely cycled?
- is there a standard way of suppressing this exception with Jersey?
Roman
--
View this message in context: http://n2.nabble.com/Issue-with-jersey-1-1-5-ClientAbortException-java-net-SocketException-Broken-pipe-tp3859286p3859286.html
Sent from the Jersey mailing list archive at Nabble.com.