Skip to main content

Weblogic: Log Filter Kung Fu

This so made my happy today I have some error/warining messages that annoy the hell out of me and clutter up my dev. (Ignorable messages but we redirect stdout to the log files)

So I know this is just hiding the problem but some messages are just worth the effort to hide and not to fix:

1) Click on your domain (DefaultDomain)  link on the left hand menu. Then Click on the log filter tab (second row of tabs). Then Click new. Give your log filter a funky name.



2) Create the filter info by clicking Edit. The below example shows how to exclude any message with the text 'oracle.adf.share.security.providers.jps.JpsIdentityManagementProvider' in the message see link at the end for all filter syntax. Click Save.




3) Navigate to the  Enviroment>Server link on the LHM and then choose your server. Click on the Logging General tab. Make sure you select the Advanced Hyperlink.


4) Select your new filter for any log you wish to filter - and there you go.



NOTE:
Make sure Redirect stderr logging enabled and Redirect stdout logging enabled are checked on the server (DefaultServer>Logging>General) you wish to filter. (Advanced tab)

Links:
 http://download.oracle.com/docs/cd/E12840_01/wls/docs103/ConsoleHelp/taskhelp/domain_log_filters/CreateLogFilters.html
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/wldf_configuring/appendix_query.html

Comments

  1. Hi, I tried many times but the errors still show up. The version I used is 11.1.1.5. Do you know why?

    ReplyDelete
    Replies
    1. Ok so figured it out...

      I always put the following flags (Redirect stderr logging enabled, Redirect stdout logging enabled) on on my weblogic by default.
      So just switch them on and it will work.
      Sorry about that will update the post.

      Delete
  2. will check it out on 11.1.1.5 tomorrow and let you know.

    ReplyDelete

Post a Comment

Popular posts from this blog

ADF Encountered deferred syntax #{ in template text.

OracleJSP error: oracle.jsp.parse.JspParseException:  Error: Encountered deferred syntax #{ in template text.  If intended as a literal, escape it or set directive  deferredSyntaxAllowedAsLiteral This normally happens when you have some tag lib dependancy problems but this was  not the case for me... My problem: For some reason my model project had web stuff in it(public html etc)  so I had to remove the public html stuff from my project and manually edit the Model.jpr project file and remove the tag lib entries at the bottom o the file. Go figure.    

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop

OJDeploy: Documentation for the tool

Real DOCS:  http://docs.oracle.com/cd/E26098_01/user.1112/e17455/deploying_apps.htm#OJDUG645 OJDeploy Documentation if you run it from the command line - I keep looking for this so I though I would post it here so I remeber. Oracle JDeveloper Deploy 11.1.2.1.0.6081 Copyright (c) 2003, 2010, Oracle and/or its affiliates. All rights reserved. Usage:   ojdeploy -profile <name> -workspace <jws> [ -project <name> ] [ <options> ]   ojdeploy -buildfile <ojbuild.xml> [ <options> ]   ojdeploy -buildfileschema Arguments:   -profile               the name of the Profile to deploy   -workspace      full path to the JDeveloper Workspace file(.jws)   -project              name of the JDeveloper Project within the .jws where the Profile can be found. If omitted, the Profile is assumed to be in the Workspace.   -buildfile            full path to a build file for batch deploy   -buildfileschema  print XML Schema for the build file