Jeff Longland

Relax, don't worry – have a home brew!

While Searching Something Else

with one comment

While searching for log4j Chainsaw updates re: VFS support, I came across a post on Oliver’s blog (initial author of Chainsaw) that related to an issue I came across a few years ago. My post to the log4j-users mailing list was related to concerns about log4j socket appenders potentially deadlocking the application server – in this case, WebLogic 8.1. A few months later Oliver encountered the problem – which is what I stumbled upon today. So the point of this post? Don’t use socket appenders on a production system – although I thoroughly advocate their use on dev/qa environments. The other point, it’s a small world after all.


Written by jlongland

November 26, 2007 at 2:15 pm

Posted in Uncategorized

One Response

Subscribe to comments with RSS.

  1. I should qualify this with the fact that I don’t really know what I’m talking about, and you probably know much more about this than me. That said, at least I’m contributing!

    If you want meaningful data, shouldn’t you be appending locally anyway? AFAIK, if SocketAppender loses its connection, you lose all events until reconnection.

    “Coming along from the network standpoint,” isn’t it preferable to ‘pull’ when you need, rather than ‘push’ all the time? Does SocketAppender encrypt the serialized object, so as not to “fall by the security wayside”? Annnnnnnd I’ve lost my mind.


    December 3, 2007 at 2:10 pm

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: