Found a 64-bit compile of the Java Service Wrapper.
http://www.krenger.ch/blog/tag/java-service-wrapper Specifically, with Simon’s compile of the open-source Tanuki product, you will not need to pay for the 64-bit license, generate keys for trial etc. Would be glad to be proven wrong...but this is likely REQUIRED for a 64-bit windows install. Apache James will not install properly as a windows service or unix daemon without the corresponding 64-bit Java Service Wrapper. The errors, stacktrace of using the wrong version (32 bit) are extremely confusing (suggesting problems with IO file/folder permissions etc). The only workaround I have heard so far is that to use the 32-bit wrapper in a 64-bit environment, just rename it (from Eric Charles). Therefore, I propose the following to make this seamless for future users - include Simon's 64-bit wrapper in the James release as follows: 1. Modify the batch file to consider the 64-bit wrapper first, not the 32-bit 2. Use Simon's wrapper for 64-bit - since Tanuki does not release one... I will create JIRA if no objections....
