my dog learned polymorphism*
The moose likes BEA/Weblogic and the fly likes Frequent Exceptions: Broken Pipe, Conn. Reset, Socket Write error, etc... Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Frequent Exceptions: Broken Pipe, Conn. Reset, Socket Write error, etc..." Watch "Frequent Exceptions: Broken Pipe, Conn. Reset, Socket Write error, etc..." New topic
Author

Frequent Exceptions: Broken Pipe, Conn. Reset, Socket Write error, etc...

Ted Smyth
Ranch Hand

Joined: May 28, 2008
Posts: 73
Good Afternoon!

I've recently taken over maintenance and development of a Struts 1.2.x-based Web Application deployed to a Weblogic 9.2 server.

My server admin complains a lot about this app, as it produces a lot exceptions in the server logs. I've traced the issue down to users hitting refresh, stop, or clicking wildly during a page-load. So, the server throws a ServletException telling me about one of the following (or some variation):

- Broken Pipe (seems common on unix)
- Response contained no data (seems more common on my windows localhost)
- Connection reset by Peer, Software caused connection abort: socket write error.

My research so far has revealed that these are "notification" exceptions thrown by Weblogic, simply indicating a recovery from an interruption while writing a response to a given client.

So my question is: what is a simple way to disable, or at least filter, these messages?

Cheers & Regards,
Edward Smith (display name already taken!)

P.S. Here's an example of the exceptions in question:

[ May 28, 2008: Message edited by: Ted Smyth ]

Edward Smith
Marcos Maia
Ranch Hand

Joined: Jan 06, 2001
Posts: 977
Hi,

as you can see in your message:

<Apr 25, 2008 10:02:36 AM EDT> <Notice> <Stdout> <000000> <179914009 [[ACTIVE] ExecuteThread: '5' for queue:


This is a NOTICE message. You can change severity logging messages selecting a server from the admin console then logging and then changig the attribute :
Severity Level for logging, standard out and domain log broadcaster.

This should stop this kind of message.
Ted Smyth
Ranch Hand

Joined: May 28, 2008
Posts: 73
Originally posted by Marcos Maia:
Hi,

as you can see in your message:



This is a NOTICE message. You can change severity logging messages selecting a server from the admin console then logging and then changig the attribute :
Severity Level for logging, standard out and domain log broadcaster.

This should stop this kind of message.


Thanks for the tip Marcos.

Regards,
Edward
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Frequent Exceptions: Broken Pipe, Conn. Reset, Socket Write error, etc...