On Jul 10, 2009, at 4:43 PM, [email protected] wrote:
https://issues.apache.org/bugzilla/show_bug.cgi?id=44386
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |
[email protected]
--- Comment #12 from [email protected] 2009-07-10 14:43:24
PST ---
I am moving our web serviceon Tomcat to 64 bit. So I found this bug
and used
the patch in attachment. I followed the instructions in your
patch_readme,
although the webservice and Tomcat 64bit both work fine, I don't see
any logs
output. Tomcat logs don't give any errors or complaints though. So
would you
please have a look of what I'm doing wrong? This is what I did:
1) build.xml I put AppenderNT.jar before log4j-1.2.14.jar
...
<pathelement location="${AppenderNT-jar}"/>
<pathelement location="${log4j-jar}"/>
2) put the NTEventLogAppender64.dll under tomcat\bin
3) put AppenderNT.jar under tomcat\lib
4) check tomcat\webapps\mine\WEB-INF\lib, verify that file
AppenderNT.jar is there
BTW, it's been almost a year since the last update on this bug. Any
update?
Will there be any official support of 64bit NTEventLogAppender from
log4j?
Thanks!
In newer OS's, you may need to explicitly register the DLL as admin,
but I think that failing to do that would only result in the messages
being formatted.
I think the DLL needs to be in the path of the process that launced
java on on java.library.path (http://forums.sun.com/thread.jspa?threadID=780109
). I don't think placing the DLL on the java classpath is sufficient.
I guess my Hurricane Ike excuse is getting old. Ike, marriage and a
new job has been keeping me busy. Won't promise but hopefully a nice
surprise soon..
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
