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 >
