I certainly wouldn't shy away from it. We use it heavily on our project
with great success.
The deadlock seems to occur when log4j is logging at the "debug" level and
we are using load time weaving (LTW). LTW is only used during development
so we don't encounter the issue very often
On Fri, Aug
No currently using aspectj, but that's bad news about the deadlock risk. I was
considering using it later on for various things... :-(
"Kevin Conaway" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
Are you using aspectj at all? I've seen aspectj and log4j deadlock in
certain ca
Are you using aspectj at all? I've seen aspectj and log4j deadlock in
certain cases.
On Fri, Aug 8, 2008 at 1:11 PM, Aaron Crow <[EMAIL PROTECTED]> wrote:
> It turns out that the connection problem was a symptom and not a root
> cause. The root cause seems to have something to do with our use of
It turns out that the connection problem was a symptom and not a root cause.
The root cause seems to have something to do with our use of log4j... it
seems to
cause hanging, perhaps due to deadlocks. For now we've turned off file
logging via log4j. We're going to experiment with log4j's asyncapp
4 matches
Mail list logo
