You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Sudip Shekhawat <su...@hotmail.com> on 2003/12/29 21:34:12 UTC

Persisting james shutdown problem

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.

Any ideas on this is greatly appreciated

Sudip

_________________________________________________________________
Have fun customizing MSN Messenger — learn how here!  
http://www.msnmessenger-download.com/tracking/reach_customize


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org

Re: Persisting james shutdown problem

Posted by Dick Dowdell <dd...@argsol.com>.
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.
>
> Any ideas on this is greatly appreciated
>
> Sudip
>
> _________________________________________________________________
> Have fun customizing MSN Messenger — learn how here! 
> http://www.msnmessenger-download.com/tracking/reach_customize
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>





---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org

Re: Persisting james shutdown problem

Posted by "Corey A. Johnson" <cj...@cniweb.net>.
Hello Sudip,

When you say "go down" Does the JVM completely exit? Or does James stop 
processing email and needs to be restarted manually?

Do you have DEBUG level logging configured in James for all blocks?

Cj

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.
>
> Any ideas on this is greatly appreciated
>
> Sudip
>
> _________________________________________________________________
> Have fun customizing MSN Messenger — learn how here! 
> http://www.msnmessenger-download.com/tracking/reach_customize
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>

-- 
Corey A. Johnson
Creative Network Innovations
http://www.cniweb.net/
1-800-CNi-5547 ** 1-321-259-1984


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org

RE: Persisting james shutdown problem

Posted by "Noel J. Bergman" <no...@devtech.com>.
Sudip Shekhawat wrote:
> 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 missed that ... they go down IN SYNCH?  There is nothing in James that
should account for that behavior.  Are you sure you don't have something odd
in a crontab?

>     c) Our servers (the machine running red hat 9.0, kernel 2.4.20)

There have been all sorts of reported problems with Java on RedHat 9 due to
its version of NPTL.  As an interim solution, before updating your servers,
you can set

  LD_ASSUME_KERNEL=2.4.1

before running James.

See: http://developer.java.sun.com/developer/bugParade/bugs/4959566.html

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org