I don't think the administrators of the application server would appreciate it 
if I redirected the standard error output stream of their Websphere instances. 
:)

Seriously, in the real world here. Our application is hosted on a System 
running Websphere. Many applications run there. The administrators decide on 
the deployement configuration and how logging is to be done. The administrators 
of that System monitor the logs vary closely. The system is HA. People get 
paged in the middle of the night when errors get logged. People get fired when 
system goes down.

I stand by what I said. Logging like this is inappropriate in library code. 

anyways. its a deal breaker for me. but just trying to convince anyone who will 
listen why  why you shouldn't be doing this.

-
Jennifer

-----Original Message-----
From: Michael Landon - IBN [mailto:[EMAIL PROTECTED]
Sent: February 21, 2006 2:56 PM
To: [email protected]
Subject: Re: Logging to SystemErr not acceptable.


http://www.devx.com/tips/Tip/5616


----- Original Message ----- 
From: "Petersen, Jennifer" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, February 21, 2006 11:57 AM
Subject: RE: Logging to SystemErr not acceptable.


I can't. I do not have control over the environment.

I would argue that it is incorrect for library/infrastructure code to be 
logging this way.
I need to control how/where/when errors and messages are reported. In this 
case it is a critical app where logs are closely monitored. Even so, I can't 
see this requirement being terribly unusual even for non-critical apps.

In any case I need to get rid of this. or not use the library :(
So is the approach to create my own patch?

thanks.

-
Jennifer


-----Original Message-----
From: Schölver, Andreas [mailto:[EMAIL PROTECTED]
Sent: February 21, 2006 12:39 PM
To: [email protected]
Subject: RE: Logging to SystemErr not acceptable.


Simply redirect shell output on System.err to /dev/null.

Andreas

> -----Original Message-----
> From: Petersen, Jennifer [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 20, 2006 4:25 PM
> To: [email protected]
> Subject: Logging to SystemErr not acceptable.
>
>
> I need to stop the client from logging to SystemErr.
> Any help would be appreciated.
>
> Here's an example:
>
> [20/02/06 9:44:10:015 EST] 60936093 SystemErr     R Avoiding
> obscuring previous error by supressing error encountered
> while ending request:
> org.apache.xmlrpc.XmlRpcClientException: Exception closing
> URLConnection
>
> --
> Jennifer Petersen
>

Reply via email to