SystemOut.log How configure logLevel - Websphere

This is a discussion on SystemOut.log How configure logLevel - Websphere ; I would like to disable some messages which pollutes our SystemOut.log. So I tried whith /exec/products/WebSphere/AppServer/v5.1/java/jre/lib/logging.properties with adding our polutting packages at the end : ################################################## ########## # Facility specific properties. # Provides extra control for each logger. ################################################## ########## ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: SystemOut.log How configure logLevel

  1. SystemOut.log How configure logLevel

    I would like to disable some messages which pollutes our SystemOut.log.
    So I tried whith /exec/products/WebSphere/AppServer/v5.1/java/jre/lib/logging.properties
    with adding our polutting packages at the end :
    ################################################## ##########
    # Facility specific properties.
    # Provides extra control for each logger.
    ################################################## ##########

    # For example, set the com.xyz.foo logger to only log SEVERE
    # messages:
    com.xyz.foo.level = SEVERE

    #ours are :
    com.ibm.ws.webservices.engine.WebServicesFault = OFF
    com.ibm.ws.webservices.engine.enterprise = OFF

    But it does nothing, we have always (after restarting) theses pollutes :
    [8/30/07 11:20:24:270 CEST] 3d1ece88 enterprise I com.ibm.ws.webservices.engi
    ne.enterprise TRAS0014I:


  2. Re: SystemOut.log How configure logLevel

    Why try to cover up the message? Why not fix them? What exactly are you seeing?


    John Pape
    IBM WebSphere / WebSphere Portal Specialist

  3. Re: SystemOut.log How configure logLevel

    My developpers told me that they can't catch the WSException and that's a normal way of operation ... So I didn't check yet if it is true or not, but i'm surprised not to find a way to manage WAS log level in SystemOut.

    Developers says:
    A cyclic timer checks the machine status;
    In case it is a server not reachable, the SystemOut.log is systematically polluted with the exception.
    That is a normal way of operation (machine could be unreachable, but the systemOut.log should not be impacted); Especially since there has been trouble with systemOut.log reaching a given size
    There is likely a printStackTrace, or a badly caught exception.
    Log incriminated in systemOut:
    [7/23/07 10:27:25:187 CEST] 46bdb082 enterprise I com.ibm.ws.webservices.engine.enterprise WSWS3243I: Info: Mapping Exception to WebServicesFault.
    [7/23/07 10:27:25:188 CEST] 46bdb082 enterprise I com.ibm.ws.webservices.engine.enterprise TRAS0014I: The following exception was logged WebServicesFault
    faultCode: Server.generalException
    faultString: java.net.NoRouteToHostException: No route to host
    faultActor: null
    faultDetail:

    java.net.NoRouteToHostException: No route to host
    at com.ibm.ws.webservices.engine.WebServicesFault.mak eFault(WebServicesFault.java:161)

  4. Re: SystemOut.log How configure logLevel

    Please go through the following link and set the log level for the component which is generaing log.

    http://publib.boulder.ibm.com/infoce...igjavalog.html

    Hope this will resolve your issue.

    Warm Regards
    Sunil Kumar Gupta

  5. Re: SystemOut.log How configure logLevel

    Yes I am on WAS 5.1 and i tried Application Servers > server1 > Logging and Tracing >
    Diagnostic Trace Service

    But I think it acts only on trace.log, assistant permit to add
    com.ibm.ws.webservices.engine.WebServicesFault=deb ug=enabled:com.ibm.ws.webservices.engine.WebServic esEngine=debug=enabled

    So I tried another level =off=disabled =off=enabled =severe=enabled =fatal=enabled
    But on each time I have an error :
    Trace specification should not be empty and must match registered WebSphere components.

    In fact I think WASConsole permit only log level Higher than Info, disabled=Info

+ Reply to Thread