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 Garvice Eakins <ga...@gmail.com> on 2012/03/13 18:22:46 UTC
Messages not being sent
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
Re: Messages not being sent
Posted by Garvice Eakins <ga...@gmail.com>.
Eric,
Yes it does. It makes several URI REST webservice calls.
On Wed, Mar 21, 2012 at 10:58 PM, Eric Charles
<er...@u-mangate.com>wrote:
> Hi Garvice,
> Does you custom mailet access an external database/service?
> Thx, Eric
>
>
> On 22/03/12 04:19, Garvice Eakins wrote:
>
>> Thomas,
>>
>> Hi yes I am using beta3 with the default remote delivery (I believe) I
>> did add a custom mailet which is matched with recipient is local. To do
>> email2database processing. Other than that everything is as is.
>>
>> ~Garvice
>>
>> Sent from my iPhone
>>
>> On Mar 21, 2012, at 8:08 PM, Thomas Eichmann<t....@eggsist.com>>
>> wrote:
>>
>> Hi Eric,
>>>
>>> Just to let you know, I unfortunately still didn't have the time to test
>>> with the original remote delivery. I hope I can give you an update soon.
>>>
>>> @Garvice, I'm curious, are you using James Beta3 with the default remote
>>> delivery and other mailets? Or did you customize anything with your own
>>> code?
>>>
>>> Best,
>>> Thomas
>>>
>>>
>>> On Thursday, 22. March 2012 at 03:04, Eric Charles wrote:
>>>
>>> Hi Garvice,
>>>> Thx for the out.txt dump.
>>>> I will have a look at it tomorrow.
>>>> Eric
>>>>
>>>>
>>>> On 21/03/12 18:35, Garvice Eakins wrote:
>>>>
>>>>> Eric I attached my output file to the issue created by Thomas.
>>>>> Sorry it took so long to do. I was caught up on business and just now
>>>>> returned.
>>>>>
>>>>> We too are only using James for smtp-out/in
>>>>>
>>>>> Thanks,
>>>>> Garvice
>>>>>
>>>>> On Thu, Mar 15, 2012 at 4:10 AM, Thomas Eichmann<t.eichmann@eggsist.**
>>>>> com <t....@eggsist.com> (mailto:t.eichmann@eggsist.com**)>wrote:
>>>>>
>>>>> Hi Eric,
>>>>>>
>>>>>> I added a report (Jira issue 1394) and attached the jstack output.
>>>>>> https://issues.apache.org/**jira/browse/JAMES-1394<https://issues.apache.org/jira/browse/JAMES-1394>
>>>>>>
>>>>>> We use James for smtp-out and smtp-in (only for bounced mails), *not*
>>>>>> for
>>>>>> pop3 or imap.
>>>>>>
>>>>>> Please let me know if I should provide any other useful data.
>>>>>>
>>>>>> Thanks,
>>>>>> Thomas
>>>>>>
>>>>>>
>>>>>> On Thursday, 15. March 2012 at 17:04, Eric Charles wrote:
>>>>>>
>>>>>> Hi Garvice and Thomas,
>>>>>>>
>>>>>>> I could be a deadlock...
>>>>>>> Do you exclusively use james for smtp-out, or also for smtp-in and/or
>>>>>>> imap and/or pop3?
>>>>>>>
>>>>>>> When the delivery will still be blocked, could you invoke jstack
>>>>>>> <james-pid> > out.txt and have a look in out.txt for any threads
>>>>>>>
>>>>>>
>>>>>>
>>>>>> deadlock?
>>>>>>
>>>>>>>
>>>>>>> You can paste the result in a mail or attach it to a JIRA.
>>>>>>>
>>>>>>> (<james-pid> is the second james process if you launch with
>>>>>>> 'bin/james
>>>>>>> start' - or the pid listed in var/james.pid + 1).
>>>>>>>
>>>>>>> @Garvin Did you finally had a chance to attach the jstack result on a
>>>>>>> JIRA (read last post of thread
>>>>>>> http://www.mail-archive.com/**server-user@james.apache.org/**
>>>>>>> msg13171.html<http://www.mail-archive.com/server-user@james.apache.org/msg13171.html>
>>>>>>> )
>>>>>>>
>>>>>>> Thx.
>>>>>>>
>>>>>>> On 15/03/12 04:14, Thomas Eichmann wrote:
>>>>>>>
>>>>>>>> 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/**server-user@james.apache.org/**
>>>>>>>> msg13171.html<http://www.mail-archive.com/server-user@james.apache.org/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: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>(mailto:
>>>>>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>>>>> )(**mailto:
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> server-user-unsubscribe@james.**apache.org<se...@james.apache.org>(mailto:
>>>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>>> ))
>>>>>>
>>>>>>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>(mailto:
>>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>>> )(mailto:
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> server-user-help@james.apache.**org<se...@james.apache.org>(mailto:
>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>> ))
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> eric | http://about.echarles.net | @echarles
>>>>>>>
>>>>>>> ------------------------------**------------------------------**
>>>>>>> ---------
>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>(mailto:
>>>>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>>>> )(**mailto:
>>>>>>>
>>>>>>
>>>>>>
>>>>>> server-user-unsubscribe@james.**apache.org<se...@james.apache.org>(mailto:
>>>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>>> ))
>>>>>>
>>>>>>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>(mailto:
>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>> )(mailto:
>>>>>>>
>>>>>>
>>>>>>
>>>>>> server-user-help@james.apache.**org<se...@james.apache.org>(mailto:
>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>> ))
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------**------------------------------**
>>>>>> ---------
>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>(mailto:
>>>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>>> )
>>>>>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>(mailto:
>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>> )
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> eric | http://about.echarles.net | @echarles
>>>>
>>>> ------------------------------**------------------------------**
>>>> ---------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>(mailto:
>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>> )
>>>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>(mailto:
>>>> server-user-help@**james.apache.org <se...@james.apache.org>
>>>> )
>>>>
>>>
>>>
>>>
>>>
>>> ------------------------------**------------------------------**
>>> ---------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>
>>
> --
> eric | http://about.echarles.net | @echarles
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>
>
Re: Messages not being sent
Posted by Eric Charles <er...@u-mangate.com>.
Hi Garvice,
Does you custom mailet access an external database/service?
Thx, Eric
On 22/03/12 04:19, Garvice Eakins wrote:
> Thomas,
>
> Hi yes I am using beta3 with the default remote delivery (I believe) I did add a custom mailet which is matched with recipient is local. To do email2database processing. Other than that everything is as is.
>
> ~Garvice
>
> Sent from my iPhone
>
> On Mar 21, 2012, at 8:08 PM, Thomas Eichmann<t....@eggsist.com> wrote:
>
>> Hi Eric,
>>
>> Just to let you know, I unfortunately still didn't have the time to test with the original remote delivery. I hope I can give you an update soon.
>>
>> @Garvice, I'm curious, are you using James Beta3 with the default remote delivery and other mailets? Or did you customize anything with your own code?
>>
>> Best,
>> Thomas
>>
>>
>> On Thursday, 22. March 2012 at 03:04, Eric Charles wrote:
>>
>>> Hi Garvice,
>>> Thx for the out.txt dump.
>>> I will have a look at it tomorrow.
>>> Eric
>>>
>>>
>>> On 21/03/12 18:35, Garvice Eakins wrote:
>>>> Eric I attached my output file to the issue created by Thomas.
>>>> Sorry it took so long to do. I was caught up on business and just now
>>>> returned.
>>>>
>>>> We too are only using James for smtp-out/in
>>>>
>>>> Thanks,
>>>> Garvice
>>>>
>>>> On Thu, Mar 15, 2012 at 4:10 AM, Thomas Eichmann<t.eichmann@eggsist.com (mailto:t.eichmann@eggsist.com)>wrote:
>>>>
>>>>> Hi Eric,
>>>>>
>>>>> I added a report (Jira issue 1394) and attached the jstack output.
>>>>> https://issues.apache.org/jira/browse/JAMES-1394
>>>>>
>>>>> We use James for smtp-out and smtp-in (only for bounced mails), *not* for
>>>>> pop3 or imap.
>>>>>
>>>>> Please let me know if I should provide any other useful data.
>>>>>
>>>>> Thanks,
>>>>> Thomas
>>>>>
>>>>>
>>>>> On Thursday, 15. March 2012 at 17:04, Eric Charles wrote:
>>>>>
>>>>>> Hi Garvice and Thomas,
>>>>>>
>>>>>> I could be a deadlock...
>>>>>> Do you exclusively use james for smtp-out, or also for smtp-in and/or
>>>>>> imap and/or pop3?
>>>>>>
>>>>>> When the delivery will still be blocked, could you invoke jstack
>>>>>> <james-pid> > out.txt and have a look in out.txt for any threads
>>>>>
>>>>>
>>>>> deadlock?
>>>>>>
>>>>>> You can paste the result in a mail or attach it to a JIRA.
>>>>>>
>>>>>> (<james-pid> is the second james process if you launch with 'bin/james
>>>>>> start' - or the pid listed in var/james.pid + 1).
>>>>>>
>>>>>> @Garvin Did you finally had a chance to attach the jstack result on a
>>>>>> JIRA (read last post of thread
>>>>>> http://www.mail-archive.com/server-user@james.apache.org/msg13171.html)
>>>>>>
>>>>>> Thx.
>>>>>>
>>>>>> On 15/03/12 04:14, Thomas Eichmann wrote:
>>>>>>> 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/server-user@james.apache.org/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: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)(mailto:
>>>>>>
>>>>>
>>>>>
>>>>> server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org))
>>>>>>> For additional commands, e-mail: server-user-help@james.apache.org (mailto:server-user-help@james.apache.org)(mailto:
>>>>>>
>>>>>
>>>>>
>>>>> server-user-help@james.apache.org (mailto:server-user-help@james.apache.org))
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> eric | http://about.echarles.net | @echarles
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)(mailto:
>>>>>
>>>>>
>>>>> server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org))
>>>>>> For additional commands, e-mail: server-user-help@james.apache.org (mailto:server-user-help@james.apache.org)(mailto:
>>>>>
>>>>>
>>>>> server-user-help@james.apache.org (mailto:server-user-help@james.apache.org))
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)
>>>>> For additional commands, e-mail: server-user-help@james.apache.org (mailto:server-user-help@james.apache.org)
>>>>
>>>
>>>
>>>
>>> --
>>> eric | http://about.echarles.net | @echarles
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)
>>> For additional commands, e-mail: server-user-help@james.apache.org (mailto: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
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
--
eric | http://about.echarles.net | @echarles
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Messages not being sent
Posted by Garvice Eakins <ga...@gmail.com>.
Thomas,
Hi yes I am using beta3 with the default remote delivery (I believe) I did add a custom mailet which is matched with recipient is local. To do email2database processing. Other than that everything is as is.
~Garvice
Sent from my iPhone
On Mar 21, 2012, at 8:08 PM, Thomas Eichmann <t....@eggsist.com> wrote:
> Hi Eric,
>
> Just to let you know, I unfortunately still didn't have the time to test with the original remote delivery. I hope I can give you an update soon.
>
> @Garvice, I'm curious, are you using James Beta3 with the default remote delivery and other mailets? Or did you customize anything with your own code?
>
> Best,
> Thomas
>
>
> On Thursday, 22. March 2012 at 03:04, Eric Charles wrote:
>
>> Hi Garvice,
>> Thx for the out.txt dump.
>> I will have a look at it tomorrow.
>> Eric
>>
>>
>> On 21/03/12 18:35, Garvice Eakins wrote:
>>> Eric I attached my output file to the issue created by Thomas.
>>> Sorry it took so long to do. I was caught up on business and just now
>>> returned.
>>>
>>> We too are only using James for smtp-out/in
>>>
>>> Thanks,
>>> Garvice
>>>
>>> On Thu, Mar 15, 2012 at 4:10 AM, Thomas Eichmann<t.eichmann@eggsist.com (mailto:t.eichmann@eggsist.com)>wrote:
>>>
>>>> Hi Eric,
>>>>
>>>> I added a report (Jira issue 1394) and attached the jstack output.
>>>> https://issues.apache.org/jira/browse/JAMES-1394
>>>>
>>>> We use James for smtp-out and smtp-in (only for bounced mails), *not* for
>>>> pop3 or imap.
>>>>
>>>> Please let me know if I should provide any other useful data.
>>>>
>>>> Thanks,
>>>> Thomas
>>>>
>>>>
>>>> On Thursday, 15. March 2012 at 17:04, Eric Charles wrote:
>>>>
>>>>> Hi Garvice and Thomas,
>>>>>
>>>>> I could be a deadlock...
>>>>> Do you exclusively use james for smtp-out, or also for smtp-in and/or
>>>>> imap and/or pop3?
>>>>>
>>>>> When the delivery will still be blocked, could you invoke jstack
>>>>> <james-pid> > out.txt and have a look in out.txt for any threads
>>>>
>>>>
>>>> deadlock?
>>>>>
>>>>> You can paste the result in a mail or attach it to a JIRA.
>>>>>
>>>>> (<james-pid> is the second james process if you launch with 'bin/james
>>>>> start' - or the pid listed in var/james.pid + 1).
>>>>>
>>>>> @Garvin Did you finally had a chance to attach the jstack result on a
>>>>> JIRA (read last post of thread
>>>>> http://www.mail-archive.com/server-user@james.apache.org/msg13171.html)
>>>>>
>>>>> Thx.
>>>>>
>>>>> On 15/03/12 04:14, Thomas Eichmann wrote:
>>>>>> 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/server-user@james.apache.org/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: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)(mailto:
>>>>>
>>>>
>>>>
>>>> server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org))
>>>>>> For additional commands, e-mail: server-user-help@james.apache.org (mailto:server-user-help@james.apache.org)(mailto:
>>>>>
>>>>
>>>>
>>>> server-user-help@james.apache.org (mailto:server-user-help@james.apache.org))
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> eric | http://about.echarles.net | @echarles
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)(mailto:
>>>>
>>>>
>>>> server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org))
>>>>> For additional commands, e-mail: server-user-help@james.apache.org (mailto:server-user-help@james.apache.org)(mailto:
>>>>
>>>>
>>>> server-user-help@james.apache.org (mailto:server-user-help@james.apache.org))
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)
>>>> For additional commands, e-mail: server-user-help@james.apache.org (mailto:server-user-help@james.apache.org)
>>>
>>
>>
>>
>> --
>> eric | http://about.echarles.net | @echarles
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)
>> For additional commands, e-mail: server-user-help@james.apache.org (mailto: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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Messages not being sent
Posted by Thomas Eichmann <t....@eggsist.com>.
Hi Eric,
Just to let you know, I unfortunately still didn't have the time to test with the original remote delivery. I hope I can give you an update soon.
@Garvice, I'm curious, are you using James Beta3 with the default remote delivery and other mailets? Or did you customize anything with your own code?
Best,
Thomas
On Thursday, 22. March 2012 at 03:04, Eric Charles wrote:
> Hi Garvice,
> Thx for the out.txt dump.
> I will have a look at it tomorrow.
> Eric
>
>
> On 21/03/12 18:35, Garvice Eakins wrote:
> > Eric I attached my output file to the issue created by Thomas.
> > Sorry it took so long to do. I was caught up on business and just now
> > returned.
> >
> > We too are only using James for smtp-out/in
> >
> > Thanks,
> > Garvice
> >
> > On Thu, Mar 15, 2012 at 4:10 AM, Thomas Eichmann<t.eichmann@eggsist.com (mailto:t.eichmann@eggsist.com)>wrote:
> >
> > > Hi Eric,
> > >
> > > I added a report (Jira issue 1394) and attached the jstack output.
> > > https://issues.apache.org/jira/browse/JAMES-1394
> > >
> > > We use James for smtp-out and smtp-in (only for bounced mails), *not* for
> > > pop3 or imap.
> > >
> > > Please let me know if I should provide any other useful data.
> > >
> > > Thanks,
> > > Thomas
> > >
> > >
> > > On Thursday, 15. March 2012 at 17:04, Eric Charles wrote:
> > >
> > > > Hi Garvice and Thomas,
> > > >
> > > > I could be a deadlock...
> > > > Do you exclusively use james for smtp-out, or also for smtp-in and/or
> > > > imap and/or pop3?
> > > >
> > > > When the delivery will still be blocked, could you invoke jstack
> > > > <james-pid> > out.txt and have a look in out.txt for any threads
> > >
> > >
> > > deadlock?
> > > >
> > > > You can paste the result in a mail or attach it to a JIRA.
> > > >
> > > > (<james-pid> is the second james process if you launch with 'bin/james
> > > > start' - or the pid listed in var/james.pid + 1).
> > > >
> > > > @Garvin Did you finally had a chance to attach the jstack result on a
> > > > JIRA (read last post of thread
> > > > http://www.mail-archive.com/server-user@james.apache.org/msg13171.html)
> > > >
> > > > Thx.
> > > >
> > > > On 15/03/12 04:14, Thomas Eichmann wrote:
> > > > > 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/server-user@james.apache.org/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: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)(mailto:
> > > >
> > >
> > >
> > > server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org))
> > > > > For additional commands, e-mail: server-user-help@james.apache.org (mailto:server-user-help@james.apache.org)(mailto:
> > > >
> > >
> > >
> > > server-user-help@james.apache.org (mailto:server-user-help@james.apache.org))
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > eric | http://about.echarles.net | @echarles
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)(mailto:
> > >
> > >
> > > server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org))
> > > > For additional commands, e-mail: server-user-help@james.apache.org (mailto:server-user-help@james.apache.org)(mailto:
> > >
> > >
> > > server-user-help@james.apache.org (mailto:server-user-help@james.apache.org))
> > >
> > >
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)
> > > For additional commands, e-mail: server-user-help@james.apache.org (mailto:server-user-help@james.apache.org)
> >
>
>
>
> --
> eric | http://about.echarles.net | @echarles
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)
> For additional commands, e-mail: server-user-help@james.apache.org (mailto: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: Messages not being sent
Posted by Eric Charles <er...@apache.org>.
Hi Garvice,
Thx for the out.txt dump.
I will have a look at it tomorrow.
Eric
On 21/03/12 18:35, Garvice Eakins wrote:
> Eric I attached my output file to the issue created by Thomas.
> Sorry it took so long to do. I was caught up on business and just now
> returned.
>
> We too are only using James for smtp-out/in
>
> Thanks,
> Garvice
>
> On Thu, Mar 15, 2012 at 4:10 AM, Thomas Eichmann<t....@eggsist.com>wrote:
>
>> Hi Eric,
>>
>> I added a report (Jira issue 1394) and attached the jstack output.
>> https://issues.apache.org/jira/browse/JAMES-1394
>>
>> We use James for smtp-out and smtp-in (only for bounced mails), *not* for
>> pop3 or imap.
>>
>> Please let me know if I should provide any other useful data.
>>
>> Thanks,
>> Thomas
>>
>>
>> On Thursday, 15. March 2012 at 17:04, Eric Charles wrote:
>>
>>> Hi Garvice and Thomas,
>>>
>>> I could be a deadlock...
>>> Do you exclusively use james for smtp-out, or also for smtp-in and/or
>>> imap and/or pop3?
>>>
>>> When the delivery will still be blocked, could you invoke jstack
>>> <james-pid> > out.txt and have a look in out.txt for any threads
>> deadlock?
>>>
>>> You can paste the result in a mail or attach it to a JIRA.
>>>
>>> (<james-pid> is the second james process if you launch with 'bin/james
>>> start' - or the pid listed in var/james.pid + 1).
>>>
>>> @Garvin Did you finally had a chance to attach the jstack result on a
>>> JIRA (read last post of thread
>>> http://www.mail-archive.com/server-user@james.apache.org/msg13171.html)
>>>
>>> Thx.
>>>
>>> On 15/03/12 04:14, Thomas Eichmann wrote:
>>>> 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/server-user@james.apache.org/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: server-user-unsubscribe@james.apache.org(mailto:
>> server-user-unsubscribe@james.apache.org)
>>>> For additional commands, e-mail: server-user-help@james.apache.org(mailto:
>> server-user-help@james.apache.org)
>>>>
>>>
>>>
>>>
>>> --
>>> eric | http://about.echarles.net | @echarles
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org(mailto:
>> server-user-unsubscribe@james.apache.org)
>>> For additional commands, e-mail: server-user-help@james.apache.org(mailto:
>> 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
>>
>>
>
--
eric | http://about.echarles.net | @echarles
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Messages not being sent
Posted by Garvice Eakins <ga...@gmail.com>.
Eric I attached my output file to the issue created by Thomas.
Sorry it took so long to do. I was caught up on business and just now
returned.
We too are only using James for smtp-out/in
Thanks,
Garvice
On Thu, Mar 15, 2012 at 4:10 AM, Thomas Eichmann <t....@eggsist.com>wrote:
> Hi Eric,
>
> I added a report (Jira issue 1394) and attached the jstack output.
> https://issues.apache.org/jira/browse/JAMES-1394
>
> We use James for smtp-out and smtp-in (only for bounced mails), *not* for
> pop3 or imap.
>
> Please let me know if I should provide any other useful data.
>
> Thanks,
> Thomas
>
>
> On Thursday, 15. March 2012 at 17:04, Eric Charles wrote:
>
> > Hi Garvice and Thomas,
> >
> > I could be a deadlock...
> > Do you exclusively use james for smtp-out, or also for smtp-in and/or
> > imap and/or pop3?
> >
> > When the delivery will still be blocked, could you invoke jstack
> > <james-pid> > out.txt and have a look in out.txt for any threads
> deadlock?
> >
> > You can paste the result in a mail or attach it to a JIRA.
> >
> > (<james-pid> is the second james process if you launch with 'bin/james
> > start' - or the pid listed in var/james.pid + 1).
> >
> > @Garvin Did you finally had a chance to attach the jstack result on a
> > JIRA (read last post of thread
> > http://www.mail-archive.com/server-user@james.apache.org/msg13171.html)
> >
> > Thx.
> >
> > On 15/03/12 04:14, Thomas Eichmann wrote:
> > > 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/server-user@james.apache.org/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: server-user-unsubscribe@james.apache.org(mailto:
> server-user-unsubscribe@james.apache.org)
> > > For additional commands, e-mail: server-user-help@james.apache.org(mailto:
> server-user-help@james.apache.org)
> > >
> >
> >
> >
> > --
> > eric | http://about.echarles.net | @echarles
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org(mailto:
> server-user-unsubscribe@james.apache.org)
> > For additional commands, e-mail: server-user-help@james.apache.org(mailto:
> 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: Messages not being sent
Posted by Thomas Eichmann <t....@eggsist.com>.
Hi Eric,
I added a report (Jira issue 1394) and attached the jstack output.
https://issues.apache.org/jira/browse/JAMES-1394
We use James for smtp-out and smtp-in (only for bounced mails), *not* for pop3 or imap.
Please let me know if I should provide any other useful data.
Thanks,
Thomas
On Thursday, 15. March 2012 at 17:04, Eric Charles wrote:
> Hi Garvice and Thomas,
>
> I could be a deadlock...
> Do you exclusively use james for smtp-out, or also for smtp-in and/or
> imap and/or pop3?
>
> When the delivery will still be blocked, could you invoke jstack
> <james-pid> > out.txt and have a look in out.txt for any threads deadlock?
>
> You can paste the result in a mail or attach it to a JIRA.
>
> (<james-pid> is the second james process if you launch with 'bin/james
> start' - or the pid listed in var/james.pid + 1).
>
> @Garvin Did you finally had a chance to attach the jstack result on a
> JIRA (read last post of thread
> http://www.mail-archive.com/server-user@james.apache.org/msg13171.html)
>
> Thx.
>
> On 15/03/12 04:14, Thomas Eichmann wrote:
> > 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/server-user@james.apache.org/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: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)
> > For additional commands, e-mail: server-user-help@james.apache.org (mailto:server-user-help@james.apache.org)
> >
>
>
>
> --
> eric | http://about.echarles.net | @echarles
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org (mailto:server-user-unsubscribe@james.apache.org)
> For additional commands, e-mail: server-user-help@james.apache.org (mailto: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: Messages not being sent
Posted by Eric Charles <er...@apache.org>.
Hi Garvice and Thomas,
I could be a deadlock...
Do you exclusively use james for smtp-out, or also for smtp-in and/or
imap and/or pop3?
When the delivery will still be blocked, could you invoke jstack
<james-pid> > out.txt and have a look in out.txt for any threads deadlock?
You can paste the result in a mail or attach it to a JIRA.
(<james-pid> is the second james process if you launch with 'bin/james
start' - or the pid listed in var/james.pid + 1).
@Garvin Did you finally had a chance to attach the jstack result on a
JIRA (read last post of thread
http://www.mail-archive.com/server-user@james.apache.org/msg13171.html)
Thx.
On 15/03/12 04:14, Thomas Eichmann wrote:
> 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/server-user@james.apache.org/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: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
--
eric | http://about.echarles.net | @echarles
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Messages not being sent
Posted by Thomas Eichmann <t....@eggsist.com>.
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/server-user@james.apache.org/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: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Messages not being sent
Posted by Garvice Eakins <ga...@gmail.com>.
I don't think the time matters...
Here are a couple samples from the James-Server.log file They are not in
order but grouped by UID showing times.
INFO 09:50:19,270 | james.smtpserver | ID=528451432 Successfully spooled
mail Mail1331743819262-65633bfa-48ad-4124-b711-1c24ee259f50 from
support@USEnergy.high5work.com on 192.168.55.42 for [xxxxx@xxxxx.com]
DEBUG 09:50:19,278 | james.mailspooler | ==== Begin processing mail
Mail1331743819262-65633bfa-48ad-4124-b711-1c24ee259f50====
INFO 10:21:41,522 | james.mailetcontext | Attempting delivery of
Mail1331743819262-65633bfa-48ad-4124-b711-1c24ee259f50-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
xxxxx@xxxxx.com]
DEBUG 10:21:41,525 | james.mailprocessor | End of mailetprocessor for state
root reached
INFO 10:21:42,229 | james.mailetcontext | Mail
(Mail1331743819262-65633bfa-48ad-4124-b711-1c24ee259f50-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [xxxxx@xxxxx.com]
****************************
NFO 10:18:39,982 | james.smtpserver | ID=731812744 Successfully spooled
mail Mail1331745519974-48c450f5-a967-4d13-aee1-a7e185c41a50 from
support@USEnergy.high5work.com on 192.168.55.42 for [xxxxx@xxxxx.com]
DEBUG 10:18:39,989 | james.mailspooler | ==== Begin processing mail
Mail1331745519974-48c450f5-a967-4d13-aee1-a7e185c41a50====
INFO 11:18:39,115 | james.mailetcontext | Attempting delivery of
Mail1331745519974-48c450f5-a967-4d13-aee1-a7e185c41a50-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
xxxxx@xxxxx.com]
INFO 11:18:40,561 | james.mailetcontext | Mail
(Mail1331745519974-48c450f5-a967-4d13-aee1-a7e185c41a50-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [xxxxx@xxxxx.com]
There are examples like this all over the place Here is a full listing
between the last two entries.
NFO 10:18:39,892 | james.smtpserver | ID=731812744 Connection established
from 192.168.55.42 (192.168.55.42)
INFO 10:18:39,982 | james.smtpserver | ID=731812744 Successfully spooled
mail Mail1331745519974-48c450f5-a967-4d13-aee1-a7e185c41a50 from
support@USEnergy.high5work.com on 192.168.55.42 for [xxxxx@xxxxx.com]
DEBUG 10:18:39,989 | james.mailspooler | ==== Begin processing mail
Mail1331745519974-48c450f5-a967-4d13-aee1-a7e185c41a50====
DEBUG 10:18:39,990 | james.mailprocessor | Call MailProcessor root
DEBUG 10:18:40,001 | james.mailprocessor | Call MailProcessor transport
DEBUG 10:18:40,062 | james.mailprocessor | End of mailetprocessor for state
root reached
INFO 10:18:40,160 | james.mailetcontext | Attempting delivery of
Mail1331741294668-7f0d937b-f714-4b0c-a0df-7c6d9b7ed297-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
xxxxx@xxxxx.com]
INFO 10:18:42,650 | james.mailetcontext | Mail
(Mail1331741294668-7f0d937b-f714-4b0c-a0df-7c6d9b7ed297-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [xxxxx@xxxxx.com]
INFO 10:19:04,274 | james.smtpserver | ID=731812744 Connection closed for
192.168.55.42 (192.168.55.42)
INFO 10:19:10,982 | james.smtpserver | ID=894104423 Connection established
from 192.168.55.42 (192.168.55.42)
INFO 10:19:11,022 | james.smtpserver | ID=894104423 Successfully spooled
mail Mail1331745551015-71228233-138b-4a93-8287-3df389c0fee5 from
support@USEnergy.high5work.com on 192.168.55.42 for [xxxxx@xxxxx.com]
DEBUG 10:19:11,030 | james.mailspooler | ==== Begin processing mail
Mail1331745551015-71228233-138b-4a93-8287-3df389c0fee5====
DEBUG 10:19:11,031 | james.mailprocessor | Call MailProcessor root
DEBUG 10:19:11,042 | james.mailprocessor | Call MailProcessor transport
DEBUG 10:19:11,099 | james.mailprocessor | End of mailetprocessor for state
root reached
INFO 10:19:11,108 | james.mailetcontext | Attempting delivery of
Mail1331741325687-09ec5b98-2cfe-4f24-8912-f87eece03faf-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
xxxxx@xxxxx.com]
INFO 10:19:11,980 | james.mailetcontext | Mail
(Mail1331741325687-09ec5b98-2cfe-4f24-8912-f87eece03faf-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [xxxxx@xxxxx.com]
INFO 10:19:24,509 | james.smtpserver | ID=894104423 Connection closed for
192.168.55.42 (192.168.55.42)
INFO 10:20:07,521 | james.smtpserver | ID=1436939877 Connection
established from 192.168.55.42 (192.168.55.42)
INFO 10:20:07,559 | james.smtpserver | ID=1436939877 Successfully spooled
mail Mail1331745607552-a8ea8087-4eb3-4b6d-9fdb-2c6da2ea79f4 from
support@USEnergy.high5work.com on 192.168.55.42 for [yyyyyy@yyyyy.com]
DEBUG 10:20:07,567 | james.mailspooler | ==== Begin processing mail
Mail1331745607552-a8ea8087-4eb3-4b6d-9fdb-2c6da2ea79f4====
DEBUG 10:20:07,567 | james.mailprocessor | Call MailProcessor root
DEBUG 10:20:07,591 | james.mailprocessor | Call MailProcessor transport
DEBUG 10:20:07,667 | james.mailprocessor | End of mailetprocessor for state
root reached
INFO 10:20:07,698 | james.mailetcontext | Attempting delivery of
Mail1331741631414-bc0f326f-7e0f-4ff2-8451-5205575638d5-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
xxxxx@xxxxx.com]
INFO 10:20:08,344 | james.mailetcontext | Mail
(Mail1331741631414-bc0f326f-7e0f-4ff2-8451-5205575638d5-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [xxxxx@xxxxx.com]
INFO 10:20:15,028 | james.smtpserver | ID=1436939877 Connection closed for
192.168.55.42 (192.168.55.42)
INFO 10:20:20,254 | james.smtpserver | ID=1248467040 Connection
established from 192.168.55.42 (192.168.55.42)
INFO 10:20:20,291 | james.smtpserver | ID=1248467040 Successfully spooled
mail Mail1331745620283-09c23bcb-efe8-4151-8a2c-809ad517c7b5 from
support@USEnergy.high5work.com on 192.168.55.42 for [zzzzz@zzz.com]
DEBUG 10:20:20,299 | james.mailspooler | ==== Begin processing mail
Mail1331745620283-09c23bcb-efe8-4151-8a2c-809ad517c7b5====
DEBUG 10:20:20,299 | james.mailprocessor | Call MailProcessor root
DEBUG 10:20:20,309 | james.mailprocessor | Call MailProcessor transport
DEBUG 10:20:20,368 | james.mailprocessor | End of mailetprocessor for state
root reached
INFO 10:20:20,373 | james.mailetcontext | Attempting delivery of
Mail1331741761455-23771c43-5d15-4f06-b2b9-89d6f944f9c2-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
xxxxx@xxxxx.com]
INFO 10:20:21,018 | james.mailetcontext | Mail
(Mail1331741761455-23771c43-5d15-4f06-b2b9-89d6f944f9c2-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [xxxxx@xxxxx.com]
INFO 10:20:45,463 | james.smtpserver | ID=1248467040 Connection closed for
192.168.55.42 (192.168.55.42)
INFO 10:21:09,316 | james.smtpserver | ID=1041440458 Connection
established from 192.168.55.42 (192.168.55.42)
INFO 10:21:09,353 | james.smtpserver | ID=1041440458 Successfully spooled
mail Mail1331745669346-ffa776fb-7da6-48b6-a0ca-64fd773f2c8b from
support@USEnergy.high5work.com on 192.168.55.42 for [zzzzz@zzzzz.com]
DEBUG 10:21:09,362 | james.mailspooler | ==== Begin processing mail
Mail1331745669346-ffa776fb-7da6-48b6-a0ca-64fd773f2c8b====
DEBUG 10:21:09,362 | james.mailprocessor | Call MailProcessor root
DEBUG 10:21:09,373 | james.mailprocessor | Call MailProcessor transport
DEBUG 10:21:09,448 | james.mailprocessor | End of mailetprocessor for state
root reached
INFO 10:21:09,472 | james.mailetcontext | Attempting delivery of
Mail1331743676112-8ecf3008-6684-4c9d-8f60-4f48a05170e3-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
xxxxx@xxxxx.com]
INFO 10:21:10,207 | james.mailetcontext | Mail
(Mail1331743676112-8ecf3008-6684-4c9d-8f60-4f48a05170e3-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [xxxxx@xxxxx.com]
INFO 10:21:41,396 | james.smtpserver | ID=1618183416 Connection
established from 192.168.55.42 (192.168.55.42)
INFO 10:21:41,433 | james.smtpserver | ID=1618183416 Successfully spooled
mail Mail1331745701426-317f6e99-1ede-4f9e-92c4-632441d6a131 from
support@USEnergy.high5work.com on 192.168.55.42 for [yyyyy@yyyy.com]
DEBUG 10:21:41,439 | james.mailspooler | ==== Begin processing mail
Mail1331745701426-317f6e99-1ede-4f9e-92c4-632441d6a131====
DEBUG 10:21:41,439 | james.mailprocessor | Call MailProcessor root
DEBUG 10:21:41,452 | james.mailprocessor | Call MailProcessor transport
INFO 10:21:41,522 | james.mailetcontext | Attempting delivery of
Mail1331743819262-65633bfa-48ad-4124-b711-1c24ee259f50-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
xxxxx@xxxxx.com]
DEBUG 10:21:41,525 | james.mailprocessor | End of mailetprocessor for state
root reached
INFO 10:21:42,229 | james.mailetcontext | Mail
(Mail1331743819262-65633bfa-48ad-4124-b711-1c24ee259f50-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [xxxxx@xxxxx.com]
INFO 10:22:06,528 | james.smtpserver | ID=1618183416 Connection closed for
192.168.55.42 (192.168.55.42)
INFO 10:23:51,269 | james.smtpserver | ID=1041440458 Connection closed for
192.168.55.42 (192.168.55.42)
INFO 11:18:38,735 | james.smtpserver | ID=296606629 Connection established
from Gates.local (192.168.55.21)
INFO 11:18:38,870 | james.smtpserver | ID=296606629 Successfully spooled
mail Mail1331749118861-6acb16ae-3ee6-4494-8054-701f420d251a from
support@dbunit.high5work.com on 192.168.55.21 for [yyyyyyy@yyyyy.com,
zzzzz@zzzzz.com]
DEBUG 11:18:38,877 | james.mailspooler | ==== Begin processing mail
Mail1331749118861-6acb16ae-3ee6-4494-8054-701f420d251a====
DEBUG 11:18:38,878 | james.mailprocessor | Call MailProcessor root
DEBUG 11:18:38,906 | james.mailprocessor | Call MailProcessor transport
DEBUG 11:18:39,003 | james.mailprocessor | End of mailetprocessor for state
root reached
INFO 11:18:39,115 | james.mailetcontext | Attempting delivery of
Mail1331745519974-48c450f5-a967-4d13-aee1-a7e185c41a50-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
xxxxx@xxxxx.com]
INFO 11:18:40,561 | james.mailetcontext | Mail
(Mail1331745519974-48c450f5-a967-4d13-aee1-a7e185c41a50-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [xxxxx@xxxxx.com]
INFO 11:24:38,940 | james.smtpserver | ID=296606629 Connection closed for
Gates.local (192.168.55.21)
There aren't any warning messages or anything. It seems like it's just not
spooling correctly. And that new additions are pushing queued ones out.
I originally thought it wasn't sending them out at all but now it's looking
like there just has to be enough in the queue to push some out.
However when I stop and restart James all the messages purge. After
shutdown here is the log of restart:
INFO 12:10:14,594 | james.mailrepositorystore | JamesMailStore init...
INFO 12:10:14,628 | james.mailrepositorystore | Registering Repository
instance of class org.apache.james.mailrepository.file.FileMailRepository
to handle file protocol requests for repositories with key file
INFO 12:10:14,628 | james.mailrepositorystore | Registering Repository
instance of class org.apache.james.mailrepository.jdbc.JDBCMailRepository
to handle db protocol requests for repositories with key db
INFO 12:10:14,632 | james.mailrepositorystore | Registering Repository
instance of class org.apache.james.mailrepository.jdbc.JDBCMailRepository
to handle dbfile protocol requests for repositories with key dbfile
INFO 12:10:14,633 | james.mailrepositorystore | Registering Repository
instance of class org.apache.james.mailrepository.file.MBoxMailRepository
to handle mbox protocol requests for repositories with key mbox
INFO 12:10:16,676 | james.dnsservice | Autodiscovery is enabled - trying
to discover your system's DNS Servers
INFO 12:10:16,694 | james.dnsservice | Adding autodiscovered server
192.168.55.27
INFO 12:10:16,694 | james.dnsservice | Adding autodiscovered server
192.168.0.27
INFO 12:10:16,695 | james.dnsservice | Adding autodiscovered search path
high5software.local.
INFO 12:10:16,695 | james.dnsservice | DNS Server is: 192.168.55.27
INFO 12:10:16,695 | james.dnsservice | DNS Server is: 192.168.0.27
INFO 12:10:16,719 | james.dnsservice | Registered cache, resolver and
search paths as DNSJava defaults
INFO 12:10:17,338 | james.domainlist | Set autodetect to: true
INFO 12:10:17,338 | james.domainlist | Set autodetectIP to: true
WARN 12:10:18,914 | james.mailetcontext | The specified postmaster address
( postmaster@localhost ) is not a local address. This is not necessarily a
problem, but it does mean that emails addressed to the postmaster will be
routed to another server. For some configurat
ions this may cause problems.
INFO 12:10:19,079 | james.mailprocessor | Matcher All instantiated.
INFO 12:10:19,099 | james.mailprocessor | Mailet PostmasterAlias
instantiated.
INFO 12:10:19,104 | james.mailprocessor | Matcher RelayLimit=30
instantiated.
INFO 12:10:19,108 | james.mailprocessor | Mailet Null instantiated.
INFO 12:10:19,112 | james.mailprocessor | Matcher SMTPAuthSuccessful
instantiated.
INFO 12:10:19,123 | james.mailprocessor | Mailet ToProcessor instantiated.
INFO 12:10:19,128 | james.mailprocessor | Matcher InSpammerBlacklist=
dnsbl.njabl.org. instantiated.
INFO 12:10:19,129 | james.mailprocessor | Mailet ToProcessor instantiated.
INFO 12:10:19,130 | james.mailprocessor | Matcher All instantiated.
INFO 12:10:19,130 | james.mailprocessor | Mailet ToProcessor instantiated.
INFO 12:10:21,247 | james.mailprocessor | Matcher SMTPAuthSuccessful
instantiated.
INFO 12:10:21,278 | james.mailprocessor | Mailet SetMimeHeader
instantiated.
INFO 12:10:21,278 | james.mailprocessor | Matcher All instantiated.
INFO 12:10:21,341 | james.mailprocessor | Mailet RecipientRewriteTable
instantiated.
INFO 12:10:21,346 | james.mailprocessor | Matcher RecipientIsLocal
instantiated.
INFO 12:10:21,371 | james.mailprocessor | Mailet RecipientToLowerCase
instantiated.
INFO 12:10:21,372 | james.mailprocessor | Matcher RecipientIsLocal
instantiated.
INFO 12:10:21,420 | james.mailprocessor | Mailet
com.high5software.smo.james.SMOMailet instantiated.
INFO 12:10:21,420 | james.mailprocessor | Matcher RecipientIsLocal
instantiated.
INFO 12:10:21,843 | james.mailprocessor | Mailet LocalDelivery
instantiated.
INFO 12:10:21,852 | james.mailprocessor | Matcher HostIsLocal instantiated.
INFO 12:10:21,853 | james.mailprocessor | Mailet ToProcessor instantiated.
INFO 12:10:21,853 | james.mailprocessor | Matcher All instantiated.
INFO 12:10:21,892 | james.mailetcontext | maxRetries is larger than total
number of attempts specified. Increasing last delayTime with 19 attempts
INFO 12:10:21,892 | james.mailetcontext | Delay of 21600000 msecs is now
attempted: 20 times
INFO 12:10:21,979 | james.mailprocessor | Mailet RemoteDelivery
instantiated.
INFO 12:10:23,521 | james.mailetcontext | Attempting delivery of
Mail1331745551015-71228233-138b-4a93-8287-3df389c0fee5-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
xxxxx@xxxxx.com]
INFO 12:10:23,527 | james.mailetcontext | Attempting delivery of
Mail1331749118861-6acb16ae-3ee6-4494-8054-701f420d251a-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from support@dbunit.high5work.com for
addresses [yyyyy@yyyyy.com, marks@h5sw.com]
INFO 12:10:23,541 | james.mailetcontext | Attempting delivery of
Mail1331745620283-09c23bcb-efe8-4151-8a2c-809ad517c7b5-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
zzzzz@zzzzz.com]
INFO 12:10:23,548 | james.mailetcontext | Attempting delivery of
Mail1331745669346-ffa776fb-7da6-48b6-a0ca-64fd773f2c8b-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
zzzzz@zzzzz.com]
INFO 12:10:23,549 | james.mailetcontext | Attempting delivery of
Mail1331745607552-a8ea8087-4eb3-4b6d-9fdb-2c6da2ea79f4-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
yyyyyy@yyyyy.com]
INFO 12:10:24,076 | james.mailprocessor | Matcher All instantiated.
INFO 12:10:24,148 | james.mailrepositorystore | Init
org.apache.james.repository.file.FilePersistentObjectRepository Store
INFO 12:10:24,161 | james.mailrepositorystore |
org.apache.james.repository.file.FilePersistentObjectRepository opened in
../var/mail/error
INFO 12:10:24,163 | james.mailrepositorystore | Init
org.apache.james.repository.file.FilePersistentStreamRepository Store
INFO 12:10:24,164 | james.mailrepositorystore |
org.apache.james.repository.file.FilePersistentStreamRepository opened in
../var/mail/error
INFO 12:10:24,178 | james.mailrepositorystore | added repository:
file://var/mail/error/->org.apache.james.mailrepository.file.FileMailRepository
INFO 12:10:24,178 | james.mailprocessor | Mailet ToRepository instantiated.
INFO 12:10:24,501 | james.mailprocessor | Matcher All instantiated.
INFO 12:10:24,502 | james.mailrepositorystore | Init
org.apache.james.repository.file.FilePersistentObjectRepository Store
INFO 12:10:24,502 | james.mailrepositorystore |
org.apache.james.repository.file.FilePersistentObjectRepository opened in
../var/mail/spam
INFO 12:10:24,503 | james.mailrepositorystore | Init
org.apache.james.repository.file.FilePersistentStreamRepository Store
INFO 12:10:24,503 | james.mailrepositorystore |
org.apache.james.repository.file.FilePersistentStreamRepository opened in
../var/mail/spam
INFO 12:10:24,503 | james.mailrepositorystore | added repository:
file://var/mail/spam/->org.apache.james.mailrepository.file.FileMailRepository
INFO 12:10:24,503 | james.mailprocessor | Mailet ToRepository instantiated.
INFO 12:10:24,589 | james.mailetcontext | Mail
(Mail1331745620283-09c23bcb-efe8-4151-8a2c-809ad517c7b5-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [yyyyy@yyyyy.com]
INFO 12:10:24,886 | james.mailprocessor | Matcher All instantiated.
INFO 12:10:24,891 | james.mailetcontext | Mail
(Mail1331749118861-6acb16ae-3ee6-4494-8054-701f420d251a-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@dbunit.high5work.com for [zzzzz@zzzzz.com, yyyyy@yyyyyy.com]
INFO 12:10:24,922 | james.mailrepositorystore | Init
org.apache.james.repository.file.FilePersistentObjectRepository Store
INFO 12:10:24,922 | james.mailrepositorystore |
org.apache.james.repository.file.FilePersistentObjectRepository opened in
../var/mail/address-error
INFO 12:10:24,922 | james.mailrepositorystore | Init
org.apache.james.repository.file.FilePersistentStreamRepository Store
INFO 12:10:24,922 | james.mailrepositorystore |
org.apache.james.repository.file.FilePersistentStreamRepository opened in
../var/mail/address-error
INFO 12:10:24,923 | james.mailrepositorystore | added repository:
file://var/mail/address-error/->org.apache.james.mailrepository.file.FileMailRepository
INFO 12:10:24,923 | james.mailprocessor | Mailet ToRepository instantiated.
INFO 12:10:25,249 | james.mailetcontext | Mail
(Mail1331745607552-a8ea8087-4eb3-4b6d-9fdb-2c6da2ea79f4-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [yyyyyy@yyyyy.com]
INFO 12:10:25,308 | james.mailprocessor | Matcher All instantiated.
INFO 12:10:25,309 | james.mailrepositorystore | Init
org.apache.james.repository.file.FilePersistentObjectRepository Store
INFO 12:10:25,309 | james.mailrepositorystore |
org.apache.james.repository.file.FilePersistentObjectRepository opened in
../var/mail/relay-denied
INFO 12:10:25,310 | james.mailrepositorystore | Init
org.apache.james.repository.file.FilePersistentStreamRepository Store
INFO 12:10:25,310 | james.mailrepositorystore |
org.apache.james.repository.file.FilePersistentStreamRepository opened in
../var/mail/relay-denied
INFO 12:10:25,310 | james.mailrepositorystore | added repository:
file://var/mail/relay-denied/->org.apache.james.mailrepository.file.FileMailRepository
INFO 12:10:25,310 | james.mailprocessor | Mailet ToRepository instantiated.
INFO 12:10:25,397 | james.mailetcontext | Mail
(Mail1331745669346-ffa776fb-7da6-48b6-a0ca-64fd773f2c8b-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [zzzzz@zzzzz.com]
INFO 12:10:25,434 | james.mailetcontext | Mail
(Mail1331745551015-71228233-138b-4a93-8287-3df389c0fee5-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [xxxxx@xxxxx.com]
INFO 12:10:25,704 | james.mailprocessor | Matcher All instantiated.
INFO 12:10:25,761 | james.mailprocessor | Mailet DSNBounce instantiated.
INFO 12:10:26,043 | james.mailspooler |
org.apache.james.mailetcontainer.impl.JamesMailSpooler init...
INFO 12:10:26,048 | james.mailspooler |
org.apache.james.mailetcontainer.impl.JamesMailSpooler uses 20 Thread(s)
INFO 12:10:26,065 | james.mailspooler | Run
org.apache.james.mailetcontainer.impl.JamesMailSpooler: dequeuer-1
INFO 12:10:26,065 | james.mailspooler | Queue=MailQueue:spool
INFO 12:10:26,086 | james.fetchmail | FetchMail Disabled
INFO 12:10:26,093 | james.mailspooler | Run
org.apache.james.mailetcontainer.impl.JamesMailSpooler: dequeuer-2
INFO 12:10:26,094 | james.mailspooler | Queue=MailQueue:spool
INFO 12:10:26,278 | james.smtpserver | SMTP Service bound to: 0.0.0.0:25
INFO 12:10:26,278 | james.smtpserver | SMTP Service is running on: ubuntu
INFO 12:10:26,278 | james.smtpserver | SMTP Service handler hello name is:
ubuntu
INFO 12:10:26,278 | james.smtpserver | SMTP Service handler connection
timeout is: 360
INFO 12:10:26,279 | james.smtpserver | SMTP Service connection backlog is:
200
INFO 12:10:26,279 | james.smtpserver | This SMTP server requires
authentication.
INFO 12:10:26,280 | james.smtpserver | No maximum message size is enforced
for this server.
INFO 12:10:26,967 | james.smtpserver | Init SMTP Service done
INFO 12:10:26,990 | james.lmtpserver | LMTP Service disabled by
configuration
INFO 12:10:27,021 | james.pop3server | POP3 Service bound to: 0.0.0.0:110
INFO 12:10:27,022 | james.pop3server | POP3 Service is running on: ubuntu
INFO 12:10:27,022 | james.pop3server | POP3 Service handler hello name is:
ubuntu
INFO 12:10:27,022 | james.pop3server | POP3 Service handler connection
timeout is: 1200
INFO 12:10:27,022 | james.pop3server | POP3 Service connection backlog is:
200
INFO 12:10:27,318 | james.pop3server | Init POP3 Service done
INFO 12:10:28,089 | james.imapserver | IMAP Service bound to: 0.0.0.0:143
INFO 12:10:28,089 | james.imapserver | IMAP Service is running on: ubuntu
INFO 12:10:28,089 | james.imapserver | IMAP Service handler hello name is:
ubuntu
INFO 12:10:28,089 | james.imapserver | IMAP Service handler connection
timeout is: 300
INFO 12:10:28,089 | james.imapserver | IMAP Service connection backlog is:
200
INFO 12:10:28,127 | james.imapserver | Init IMAP Service done
INFO 12:10:28,319 | james.mailetcontext | Attempting delivery of
Mail1331745701426-317f6e99-1ede-4f9e-92c4-632441d6a131-to-h5sw.com to host
aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.comfor addresses [
yyyyy@yyyy.com]
INFO 12:10:28,683 | org.apache.james.container.spring.Main | Apache James
Server is successfully started in 28572 milliseconds.
INFO 12:10:29,177 | james.mailetcontext | Mail
(Mail1331745701426-317f6e99-1ede-4f9e-92c4-632441d6a131-to-h5sw.com) sent
successfully to aspmx.l.google.com. at 209.85.225.27 from
support@USEnergy.high5work.com for [yyyyyy@yyyyy.com]
On Wed, Mar 14, 2012 at 7:34 AM, Eric Charles <er...@apache.org> wrote:
> Hi Garvice,
>
>
> Is the time or the number of mail important here?
> Do you see any exception in the log? In any case, just post here what you
> get in the log when it stops sending out.
>
> Thx.
> Eric
>
>
>
> On 13/03/12 18: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
>>
>>
> --
> eric | http://about.echarles.net | @echarles
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>
>
Re: Messages not being sent
Posted by Eric Charles <er...@apache.org>.
Hi Garvice,
Is the time or the number of mail important here?
Do you see any exception in the log? In any case, just post here what
you get in the log when it stops sending out.
Thx.
Eric
On 13/03/12 18: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
>
--
eric | http://about.echarles.net | @echarles
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org