# The Problem With Logging

**URL:** <https://discourse.codinghorror.com/t/the-problem-with-logging/250>\
**Category:** blog\
**Created:** [December 3, 2008, 12:00am UTC](https://discourse.codinghorror.com/t/the-problem-with-logging/250 "2008-12-03T00:00:00Z")\
**Posts on this page:** 1\
**Showing post:** 161

<div class="post-metadata">

**Author:** ![Simon](https://discourse-cdn.codinghorror.com/letter_avatar_proxy/v2/letter/s/f07891/32.png) [@Simon](https://discourse.codinghorror.com/u/Simon)\
**Post date:** [February 6, 2010, 12:00am UTC](https://discourse.codinghorror.com/t/the-problem-with-logging/250/161 "2010-02-06T00:00:00Z")

</div>

Regarding how logging might cause deadlocks, I’m not familiar with Log4Net, but the scenario I envisage would be that some complex object has been passed to the logger, the logger has attempted to convert it to a string, and the object’s method for obtaining a string representation is doing complex stuff - maybe causing object state to be lazy-loaded from the database, that kind of thing.

---

_[View the full topic](https://discourse.codinghorror.com/t/the-problem-with-logging/250)._