There are 3 logs:
logs/phoenix.log
tmp/phoenix.console (or the console if you run it as a service)
apps/james/logs/*.log
You should check all of them in the last seconds before it shutdown.
A clean shutdown task should only happen when you kill the process from
the outside.
Can you provide the script that restart exim? If it kills james because
it binds the port 25 then the shutdown is the correct consequence.
Stefano
philguillard wrote:
Thanks a lot Stefano,
The server starts and stops a few hours later. James 2.2.0, jvm 5,
redhat enterprise 9.
From default configuration i added a mailet to configure my mailinglist
from DB, and setted users from DB also.
From last news it could be done from another script from my provider
trying to restart another mail service called exim so i don't know what
to think about it right now. I didn't find any more interesting logs at
the moment.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]