No, trace is just a finer level of debugging info. The choice of using
debug vs trace is one of will the log message show up in propotion
to some method invocation(EJB call, JMS msg delivery, etc.). The
usage I recommended(here: http://www.jboss.org/developers/guide/logging.jsp)
was that debug gave detailed info on one-time life cycle type of
events, while trace gave info on method invocation related activity.
Logging the behavior of the transaction manager is an example of
something that should be done at trace level as this is a huge amount
of logging per method invocation. The startup and binding of the transaction
manager service are info or debug level messages depending on the
detail of the log message.


----- Original Message -----
From: "marc fleury" <[EMAIL PROTECTED]>
To: "Scott M Stark" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Wednesday, February 20, 2002 1:59 PM
Subject: RE: [JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb
Container.java StatefulSessionContainer.java


> |Its not a question of the expense of log.debug vs log.trace here.
> |Both are used under a guard in this code and will only incur the
> |cost of generating the log message string if logging is requested.
>
> Ok so we don't create the Strings.
>
> |The issue is that a lot of useful information is issued using
> |debug level messages that are not related to method invocations.
> |Using trace vs debug is simply a question of isolating logging messages
> |that are issued O(N) or higher with respect to method invocation vs debug
> |msgs that may be verbose, but are still O(1) with respect to method
> |invocations. Basically, if I am running with a filter that allows DEBUG
> |level messages, the log should not fill up because I run a trival
stateless
> |session test with 100,000 method invocations.  If I run with TRACE
> |enabled, I might be getting 1Gb of data detailing the activity at the
> |method invocation level.
>
> This is unclear.  Can you explain this again? Is trace something like a
> "stack trace" where we follow one method invocation and see what goes on?
> If so that is useful, please help me understand what you are saying above.
> Keep it simple please.
>
> marcf
>
>


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to