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 Thilo Götz <tw...@gmx.de> on 2010/08/30 15:37:35 UTC
Running James 2.3.2 as a Windows service
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
Re: Fwd: Running James 2.3.2 as a Windows service
Posted by Thilo Götz <tw...@gmx.de>.
Just FYI, I've given up on Commons Daemon and will write my
own .exe that starts James and that I can register as a service.
I spent another afternoon on it and although I made some little
progress, I never got it working properly.
--Thilo
On 9/1/2010 16:58, Thilo Götz wrote:
> On 9/1/2010 16:43, Norman Maurer wrote:
>> Hi there,
>>
>> in current trunk we use maven-appassembler plugin to build the
>> scripts. could you give it a try and see if its fixed there ?
>
> Hi, not sure I get your meaning. You use maven-appassembler to
> build what scripts? And what would that fix exactly? The fact
> that ServiceWrapper doesn't run on Windows Server 2008 64bit?
>
> I have been playing around with Commons Daemon for a day now,
> and it's tough going. Should I get it to run, I'll let you know.
>
> --Thilo
>
>>
>> Thx,
>> Norman
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Norman Maurer <no...@apache.org>
>> Date: 2010/9/1
>> Subject: Re: Running James 2.3.2 as a Windows service
>> To: James Users List <se...@james.apache.org>
>>
>>
>> Hi there,
>>
>> in current trunk we use maven-appassembler plugin to bui
>>
>> 2010/8/30 Thilo Götz <tw...@gmx.de>:
>>> 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
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Fwd: Running James 2.3.2 as a Windows service
Posted by Thilo Götz <tw...@gmx.de>.
On 9/1/2010 16:43, Norman Maurer wrote:
> Hi there,
>
> in current trunk we use maven-appassembler plugin to build the
> scripts. could you give it a try and see if its fixed there ?
Hi, not sure I get your meaning. You use maven-appassembler to
build what scripts? And what would that fix exactly? The fact
that ServiceWrapper doesn't run on Windows Server 2008 64bit?
I have been playing around with Commons Daemon for a day now,
and it's tough going. Should I get it to run, I'll let you know.
--Thilo
>
> Thx,
> Norman
>
>
>
> ---------- Forwarded message ----------
> From: Norman Maurer <no...@apache.org>
> Date: 2010/9/1
> Subject: Re: Running James 2.3.2 as a Windows service
> To: James Users List <se...@james.apache.org>
>
>
> Hi there,
>
> in current trunk we use maven-appassembler plugin to bui
>
> 2010/8/30 Thilo Götz <tw...@gmx.de>:
>> 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
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Fwd: Running James 2.3.2 as a Windows service
Posted by Norman Maurer <no...@apache.org>.
Hi there,
in current trunk we use maven-appassembler plugin to build the
scripts. could you give it a try and see if its fixed there ?
Thx,
Norman
---------- Forwarded message ----------
From: Norman Maurer <no...@apache.org>
Date: 2010/9/1
Subject: Re: Running James 2.3.2 as a Windows service
To: James Users List <se...@james.apache.org>
Hi there,
in current trunk we use maven-appassembler plugin to bui
2010/8/30 Thilo Götz <tw...@gmx.de>:
> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Running James 2.3.2 as a Windows service
Posted by Norman Maurer <no...@apache.org>.
Hi there,
in current trunk we use maven-appassembler plugin to bui
2010/8/30 Thilo Götz <tw...@gmx.de>:
> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org