Re: How-to: Displaying SQL taking longer than x milliseconds?

From: Ricardo J. Parada (rparad..ac.com)
Date: Wed Apr 21 2010 - 13:43:44 EDT

  • Next message: David Avendasora: "woproject.jar"

    Thanks Kieran!

    It's working now. I think the er.extensions.ERXAdaptorChannelDelegate.enabled=true is what I was missing.
    And I see now where in the code it is output so I understand better now. :-)

    On Apr 21, 2010, at 1:17 PM, Kieran Kelleher wrote:

    > #########################################################################
    > # ERXAdaptorChannelDelegate
    > #########################################################################
    > ## Enable delegate to emit SQL debugging info. The Logger used is
    > ## log4j.category.er.extensions.ERXAdaptorChannelDelegate.sqlLogging
    > er.extensions.ERXAdaptorChannelDelegate.enabled=true
    >
    > ## How long a statement must run to cause a log message. Messages with longer than
    > ## error also emit a stack-trace
    > er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.debug=0
    > er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.info=100
    > er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.warn=2000
    > er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.error=15000
    >
    > ## MaxLength of the message
    > er.extensions.ERXAdaptorChannelDelegate.trace.maxLength = 3000
    >
    > ## What entities to watch
    > er.extensions.ERXAdaptorChannelDelegate.trace.entityMatchPattern = .*
    >
    > ## Actually set the log level
    > log4j.logger.er.extensions.ERXAdaptorChannelDelegate.sqlLogging=WARN
    >

    This archive was generated by hypermail 2.0.0 : Wed Apr 21 2010 - 13:45:01 EDT