Hi, I'm running James 2.3.2 on various versions of Windows as a service. Up till now, I was using the ServiceWrapper exe that comes with the James distribution. However, the ServiceWrapper has problems on Windows Server 2008 64bit, it does not reliably communicate with the embedded JVM.
These issues are fixed with newer versions of the ServiceWrapper, but that newer version is under GPL. This makes it a no-go area for me, and I guess is also the reason it doesn't come prepackaged with James. I have started investigating Commons Daemon as a replacement for ServiceWrapper. I noticed that James even comes with a ready-to-use Commons Daemon controller class, though I haven't tried it yet: org.apache.avalon.phoenix.launcher.DaemonLauncher. So before I spend a lot of time on this: are there known issues with using Commons Daemon instead of ServiceWrapper? Is there a particular reason James ships ServiceWrapper, and not, e.g., instructions on how to set it up with Commons Daemon? Thanks, and keep up the good work! --Thilo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
