Re: Persisting james shutdown problem

[Sudip Shekhawat]

I had upgraded to James2.2.0 since we had some database connectivity 
problem. We had our server running james2.2.0 for 3 mothns without any 
problems. So basically James2.2 with our mailets have been tested on our 
systems. There should be a argument to roll back to 2.1.3, and that will be 
a long process for us.

Sudip

Sudip,

I may be missing something here, but is there a compelling reason you're 
not running James 2.1.3?

Regards,
Dick Dowdell
Argosy Solutions


Sudip Shekhawat wrote:

We have 3 James servers running on different machines. And invariably all 
go down on an average, once a day.

1) The log files created on all the three servers running James2.2.0a8 
show that all the three mail servers go down at the same time. I have 
noticed this behavior more than a couple of time, so I will rule this out 
as a coincidence.

2) The common things these three mail server share are
a) The network
b) James version, all 2.2.0a8
c) Our servers (the machine running red hat 9.0, kernel 2.4.20)
3) The current logging of JVM didn�t report any alarming output. Currently 
I have to find a way to increase the logging level for JVM.
_________________________________________________________________
Take advantage of our limited-time introductory offer for dial-up Internet 
access. http://join.msn.com/?page=dept/dialup

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]