I just shutdown James through Services, double-checked that the java.exe
process stopped through Task Manager, triple-checked that I couldn't
telnet to port 25, and then restarted James through Services. So I'm
pretty positive that things are shutting down correctly.
-J
Jay Kraly wrote:
I'll confirm in a couple minutes. If it wasn't shutting down properly
wouldn't the new instance of it complain immediately on startup and
then shutdown again? I've seen that happen before when things didn't
really shutdown properly. However, in this case it starts up fine and
will serve mail with no problems until a heavy load is encountered
from the CFMX process on the same machine.
Last night I setup an exact replica of my James installation on
another server in the load-balanced cluster. So now I have a
criss-crossed environment where two CFMX servers are using James on
the other server. Both servers are running CFMX and both are running
the same installation of James. This setup works perfectly and can
handle the load with no problems, even when I turn off spooling in CFMX.
-J
Serge Knystautas wrote:
Jay Kraly wrote:
I'm using j2re1.4.2_05 and I stop and start it as a service. One
thing I tried to test the port conflict theory was switching james
to port 2225 and switching CFMX to use port 2225, but I had the
exact same connection problems as when it was running on port 25.
Can you confirm that James has shutdown before you start it again?
Best bet would be to look in task manager for a java process (though
the service might rename it). I would assume it's one of the top 5
largest processes by memory size.
---------------------------------------------------------------------
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]
