[prev in list] [next in list] [prev in thread] [next in thread] 

List:       james-user
Subject:    Running James 2.3.2 as a Windows service
From:       Thilo_Götz <twgoetz () gmx ! de>
Date:       2010-08-30 13:37:35
Message-ID: 4C7BB41F.6010004 () gmx ! de
[Download RAW message or body]

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: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]