Hi Garvice The problem you describe sounds a lot like the one we are having with James Beta3 too. See my message to the mailing list here: http://www.mail-archive.com/[email protected]/msg13171.html
In our case it happens every few days after sending out several hundred to max 10,000 mails. I added a lot of logging to our mailets, but they always seem to process the mails without problems. Just somehow the mails are not sent out, except after a restart as you describe as well. As a workaround we are simply restarting James once per day for now, but I hope there is a solution to this issue. It also happened a few times that the server became completely unresponsive. Btw did you try to flush the queue? It sometimes helped in our case, but not every time. The only way to be sure is to restart the whole server. (execute flush on the following JMX bean): org.apache.james:type=component,name=queue,queue=outgoing Best, Thomas -- Thomas Eichmann EGGsist limited suite 27a, tower b, oriental kenzo dongzhimen, beijing, china +86 (010) 84477066 On Wednesday, 14. March 2012 at 01:22, Garvice Eakins wrote: > I'm having a problem where Jamesv3 beta 3 stops sending messages. > After several hours and not more than 20 messages, James stops sending out > emails. > I can see the log where the message is being processed but aren't sent out. > I then have to stop and restart James and all messages get sent out > immediately. > Is there a setting I'm missing? > > ~Garvice --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
