You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Lutz Michael <mi...@siemens.com> on 2004/09/29 21:24:58 UTC

recursive stack failure


Has anyone run into the following situation?  If so please share how you
handled it.

Scenario: Objects paced into MDC overload their toString() methods (which
determine log content), but they make logging calls in their toString()
methods themselves resulting in stack recursion failure.  JVM crash & burn.

I'm hoping there's a recommended approach for handling this.  Obviously we
can try to avoid placing logging calls in our toString() methods for objects
placed into MDC, but we wanted to make sure there's not a more robust
approach.

Thanks in advance.

Mike

_______________________________________________
Siemens Medical Solutions Health Services 
Michael Lutz
Software Engineer, Soarian Common Components
51 Valley Stream Parkway, Malvern, PA 19355 
Office / Voice Mail	+01 610-219-8613 
Cell			+01 610-952-2289
Home Office		+01 610-989-3623
Fax			+01 610-219-4004 
E-mail <ma...@siemens.com> 
_______________________________________________


-------------------------------------------------------------------------------
This message and any included attachments are from Siemens Medical Solutions 
USA, Inc. and are intended only for the addressee(s).  
The information contained herein may include trade secrets or privileged or 
otherwise confidential information.  Unauthorized review, forwarding, printing, 
copying, distributing, or using such information is strictly prohibited and may 
be unlawful.  If you received this message in error, or have reason to believe 
you are not authorized to receive it, please promptly delete this message and 
notify the sender by e-mail with a copy to Central.SecurityOffice@shs.siemens.com 

Thank you

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org