You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Eric Charles <er...@apache.org> on 2013/11/09 07:44:45 UTC
Re: 64-bit Java Service Wrapper
Sounds to me like we should rather move to
http://commons.apache.org/proper/commons-daemon/
On 07/11/13 22:40, Net Dawg wrote:
> 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....
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org