Tony W. Freeman wrote:
Copied the *i18n*.jar file to the lib folder. Restarted with no
success. Now this in the logs...
Tony, I understood from this
http://issues.apache.org/jira/browse/JAMES-460?page=comments#action_12371781
that you finally have been succesfull...
Is this message still
-Original Message-
From: Stefano Bagnara [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 25, 2006 8:37 AM
To: James Users List
Subject: Re: FW: Running current trunk as a NT service
Tony W. Freeman wrote:
Copied the *i18n*.jar file to the lib folder. Restarted with no
success. Now
Ok. I've downloaded version 3.2.0 and replaced wrapper.exe, wrapper.jar,
wrapper.dll.
Then I installed the service using wrapper -i ..\conf\wrapper.conf.
When I start the service either using net start James Mail Server 2.3.0 or
wrapper -t ..\conf\wrapper.conf the same error appears on the
instead.
STATUS | wrapper | 2006/03/24 09:15:10 | -- Wrapper Stopped
-Original Message-
From: Bernd Fondermann [mailto:[EMAIL PROTECTED]
Sent: Friday, March 24, 2006 4:48 AM
To: James Users List
Subject: Re: Running current trunk as a NT service
Ok. I've downloaded version 3.2.0
Tony Freeman @ TeamXL wrote:
Tried to install as a service and found the same errors as originally noted
in this topic. Downloaded and moved the wrapper.* stuff to my server.
Tried again and got the wrapper.pidfile error. Removed same from my
wrapper.conf file and tried again. I am now
Copied the *i18n*.jar file to the lib folder. Restarted with no
success. Now this in the logs...
PHOENIX LOG...
INFO2006-03-24 10:06:49.894 [Phoenix ] (): Logger started
WRAPPER LOG...
STATUS | wrapper | 2006/03/24 10:06:48 | -- Wrapper Started as Service
STATUS | wrapper | 2006/03/24
Hi,
I've checked out the current trunk from svn.
I've built it without problem.
.\build.bat clean
.\build.bat dist-lite
I've installed James as a NT service using the supplyed wrapper:
.\dist\james-2.3-dev\bin\wrapper -i ..\conf\wrapper.conf
When I try to launch the
Hi Carlos,
this is a bug. Can you file an issue in our issue tracker?
https://issues.apache.org/jira/browse/JAMES
The problem is that DaemonLauncher look for
org.tanukisoftware.wrapper.WrapperListener
while we bundle a newer wrapper that has been repackaged:
Stefano Bagnara wrote:
The problem is that DaemonLauncher look for
org.tanukisoftware.wrapper.WrapperListener
while we bundle a newer wrapper that has been repackaged:
com.silveregg.wrapper.WrapperListener
Ops, it is the exact opposite ;-)
Can you try downloading the 3.x wrapper from
