(1) Windows only: Sometimes we have a bug where Tomcat cannot pick up the C++ runtime libraries

Solution: Copy C:\Program Files\MailArchiva\jre\bin\msvcr71.dll to C:\Windows\System32 and restart the service

(2) Listening Ports taken

Note: VMWare Server and Symantec Antivirus often use ports 8005 and 8009, so you may need to switch these ports.

(We typically switch them to 8015, and 8019, respectively)

- The server cannot listen on ports 8090, 8005, 8091, 8092, 8009 since they are already taken

- You can check if these ports are taken by doing the following:

From the Windows commandline, type:

netstat -abn > ports.txt
notepad ports.txt
ctrl+F to search for desired port

From the Linux commandline, type:

netstat -l | grep 8090

- On Windows, you can run MailArchiva in Console mode by running the C:\Program Files\MailArchiva\Server\bin\MailArchivaServer.exe file.

- In the console output, if it complains about a port conflict, you know you need to change ports

- On Linux, you should see the symptoms of a port conflict in the /usr/local/mailarchiva/server/logs/catalina.out file.

- Solution:

(a) Edit the file server.xml in C:\Program Files\MailArchiva\Server\conf or /usr/local/mailarchiva/server/conf and and change the ports

(b) Edit the 8091 (smtp) and 8092 (milter) ports in the MailArchiva server GUI or server.conf file

(3) Multiple instances of the Mailarchiva Server running

- You have multiple instances of the server running. Please kill all Java processes before starting the server

(4) There is not enough physical memory on the machine

The server requires an absolute minimum of 768 MB to function effectively in a production environment. The server may not start because you have too little memory. You can lower the amount of memory needed by the product (although this is not recommended for production use). To do this on Windows, right click the task tray applet, click Configure, click Java tab, decrease the size of maximum memory pool size. On Linux, edit file /usr/local/mailarchiva/server/startserver.sh replace -Xmx2048m with a lower value, such as -Xmx768m

[Note: We recommend at least 2 GB of Memory available to MailArchiva]

(5) The location of the JRE is not in the PATH

You need to make sure that the location of the JRE is on the path. On Windows, add your JRE's bin folder to the PATH environment. the file C:\Program Files\MailArchiva\jre\bin. This advice should be taken especially in the case where you get procrun.c errors in C:\Program Files\MailArchiva\Server\logs\jakarta_service*.log files.

(6) Log File Checking

If your problem is not helped by the above, then you need to consult the ServerLog file.

-- JamieBand - 21 Sep 2007