Michael,
Thanks for that - the problems have been resolved. I would never have guessed
that from the variable name.
Cheers,
David
----- Original Message -----
From: "michael brader" <[EMAIL PROTECTED]>
To: "David Hobley" <[EMAIL PROTECTED]>
Cc: "rt-users" <rt-users@lists.bestpractical.com>
Sent: Friday, 16 May, 2008 3:23:51 PM (GMT+1000) Auto-Detected
Subject: Re: [rt-users] Help! Suddenly getting stacktraces
David Hobley writes:
> Michael,
>
> Thanks for the quick response. Are you saying that these
> stacktraces are not indicative of any issues and that I can ignore
> them?
Well, you should set that variable to 0, because generating the stack
trace will have some overhead (presumably mostly in writing the lines
to the log).
> Normally I would expect that anything that generated a stacktrace
> would also require a fix to not generate them!
Normally you'd be right, but if it's LogStackTrace, it's not a stack
trace generated by Perl, but by RT. From RT.pm:
if( $RT::LogStackTraces ) {
$str .= "\nStack trace:\n";
# skip calling of the Log::* subroutins
$frame++ while( caller($frame) && (caller($frame))[3] =~ /^Log::/ );
while( my ($package, $filename, $line, $sub) = caller($frame++) ) {
$str .= "\t". $sub ."() called at $filename:$line\n";
}
}
Cheers,
Michael
--
Michael Brader [EMAIL PROTECTED]
--
Cheers,
David Hobley
IT Manager
Creators of Miessence, MiVitality and MiEnviron
Phone: +61 (7) 5582 7020
Fax: +61 (7) 5539 6719
USA Fax 1800 840 0827
Email : [EMAIL PROTECTED]
Website: www.mionegroup.com
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
