Hi Karthik,

this "error" only tells you that the config files are already in place
and will not get replaced when unpacking the sar. So nothing to worry
about.

About your problem, I would start digging in the mailet-*.log file.

Bye,
Norman

Ps: You should really think about upgrading to james 2.3.2, 2.2.0 is
really old and many bugs where fix since the release of it..

2009/11/9 karthik <[email protected]>:
> Hi All,
>
>        Today, When I was informed that users are not receiving mails, I
> found an errors in the Phoenix.log like below
>
> <Phoenix Snip >
>
>     Phoenix was not started by the daemon thus it will not be possible to
> restart the JVM via the Management interface.
> INFO 2009-11-01 15:31:08.804 [Phoenix.] (): Installing Sar located at
> file:/mnt/james/james-2.2.0/apps/james.sar.
>
> WARN 2009-11-01 15:31:08.816 [Phoenix.] (): The file SAR-INF/assembly.xml
> can not be extracted from the Sar
> "file:/mnt/james/james-2.2.0/apps/james.sar" into directory
>
> /mnt/james/james-2.2.0/apps/james/SAR-INF/assembly.xml because there is a
> file in the way.
>
> WARN 2009-11-01 15:31:08.818 [Phoenix.] (): The file SAR-INF/config.xml can
> not be extracted from the Sar
> "file:/mnt/james/james-2.2.0/apps/james.sar" into directory
> /mnt/james/james-2.2.0/apps/james/SAR-INF/config.xml because there is a file
> in the way.
> WARN 2009-11-01 15:31:08.820 [Phoenix.] (): The file SAR-INF/environment.xml
> can not be extracted from the Sar
> "file:/mnt/james/james-2.2.0/apps/james.sar" into directory
> /mnt/james-2.2.0/apps/james/SAR-INF/environment.xml because there is a file
> in the way.
>
>     <Phoenix Snip>
>
> How do i rectify the errors and ensure the mails start flowing for the
> users.
>
>
>
> Regards,
> Karthik
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to