We are using weblogic (10.3.4.0) to deploy java applications. The applications themselves have their own logging set up (using logback). We want to use the wls_server1.log/out files to just log errors/warnings regarding
weblogic; not the deployments. Our current stumbling block is that exceptions thrown by the deployments end up both in their log and the wls_server logs.
Is there any way using log filters or even tampering with java.util.logging properties file to avoid this? The problem is that exceptions are used in the applications to propagate errors to users, say an authentication error, so the wls logs gets rapidly clyttered.
If anybody has a solution or a general idea of what we can do to solve this it would be much appreciated.
There was no buildt in expression logic for exceptions but i managed to filter it on MESSAGE (exception class). Not super pretty, but it seems to work. Thanks for the fast reply and the help!
Edited by: 995329 on Mar 21, 2013 8:43 AM