Did you explicitly register the DLL with regsvr32 or equivalent (like
an installer program) as administrator? The DLL does try to register
itself when used, however that is blocked under Windows Vista by
default and may be blocked under earlier versions by configuration.
On Jun 18, 2009,
Did you look at the quoted messages? It's all right there. I cut out the
other responses so you can see just what I posted.
On Wed, Jun 17, 2009 at 3:41 PM, Jacob Kjome wrote:
> List your entire logging properties and restate your requirements. I'm
> lost on what you tried and didn't try.
>
>
Hi -
I am using the appender dll from log4j 1.2.15. I believe I have found all
the threads on this subject of the EventViewer complaining about not being
able to find the event description. And I've read bug 41169 and perused the
appender code. It all makes sense and it ought to work, but when
Hi Lesley,
Looking at your log4j.xml file it appears that you are defining several
AsyncAppenders, actually 6 of them which does not explain why there are 12
AsyncAppender threads. At some point in time, you have probably restarted the
web-application (or reloaded log4j) without shutting down
Hi Ceki / all,
Since then I've done abit more investigation and found a few odd things
which support the theory that there is more than 1 thread writing
to the same log file thus causing our log file to get corrupted and have
missing entries.
I noticed that:
* a thread dump via Weblogic 10.3 i
