Eric, Yes it does. It makes several URI REST webservice calls.
On Wed, Mar 21, 2012 at 10:58 PM, Eric Charles <[email protected]>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.eichmann@eggsist.**com<[email protected]>> >> 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 <[email protected]> (mailto:[email protected]**)>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/**[email protected]/** >>>>>>> msg13171.html<http://www.mail-archive.com/[email protected]/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/**[email protected]/** >>>>>>>> msg13171.html<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: >>>>>>>> server-user-unsubscribe@james.**apache.org<[email protected]>(mailto: >>>>>>>> server-user-**[email protected]<[email protected]> >>>>>>>> )(**mailto: >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> server-user-unsubscribe@james.**apache.org<[email protected]>(mailto: >>>>>> server-user-**[email protected]<[email protected]> >>>>>> )) >>>>>> >>>>>>> For additional commands, e-mail: >>>>>>> [email protected].**org<[email protected]>(mailto: >>>>>>>> server-user-help@**james.apache.org<[email protected]> >>>>>>>> )(mailto: >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> [email protected].**org<[email protected]>(mailto: >>>>>> server-user-help@**james.apache.org<[email protected]> >>>>>> )) >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> eric | http://about.echarles.net | @echarles >>>>>>> >>>>>>> ------------------------------**------------------------------** >>>>>>> --------- >>>>>>> To unsubscribe, e-mail: >>>>>>> server-user-unsubscribe@james.**apache.org<[email protected]>(mailto: >>>>>>> server-user-**[email protected]<[email protected]> >>>>>>> )(**mailto: >>>>>>> >>>>>> >>>>>> >>>>>> server-user-unsubscribe@james.**apache.org<[email protected]>(mailto: >>>>>> server-user-**[email protected]<[email protected]> >>>>>> )) >>>>>> >>>>>>> For additional commands, e-mail: >>>>>>> [email protected].**org<[email protected]>(mailto: >>>>>>> server-user-help@**james.apache.org<[email protected]> >>>>>>> )(mailto: >>>>>>> >>>>>> >>>>>> >>>>>> [email protected].**org<[email protected]>(mailto: >>>>>> server-user-help@**james.apache.org<[email protected]> >>>>>> )) >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------**------------------------------** >>>>>> --------- >>>>>> To unsubscribe, e-mail: >>>>>> server-user-unsubscribe@james.**apache.org<[email protected]>(mailto: >>>>>> server-user-**[email protected]<[email protected]> >>>>>> ) >>>>>> For additional commands, e-mail: >>>>>> [email protected].**org<[email protected]>(mailto: >>>>>> server-user-help@**james.apache.org<[email protected]> >>>>>> ) >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> eric | http://about.echarles.net | @echarles >>>> >>>> ------------------------------**------------------------------** >>>> --------- >>>> To unsubscribe, e-mail: >>>> server-user-unsubscribe@james.**apache.org<[email protected]>(mailto: >>>> server-user-**[email protected]<[email protected]> >>>> ) >>>> For additional commands, e-mail: >>>> [email protected].**org<[email protected]>(mailto: >>>> server-user-help@**james.apache.org <[email protected]> >>>> ) >>>> >>> >>> >>> >>> >>> ------------------------------**------------------------------** >>> --------- >>> To unsubscribe, e-mail: >>> server-user-unsubscribe@james.**apache.org<[email protected]> >>> For additional commands, e-mail: >>> [email protected].**org<[email protected]> >>> >>> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> server-user-unsubscribe@james.**apache.org<[email protected]> >> For additional commands, e-mail: >> [email protected].**org<[email protected]> >> >> > -- > eric | http://about.echarles.net | @echarles > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > server-user-unsubscribe@james.**apache.org<[email protected]> > For additional commands, e-mail: > [email protected].**org<[email protected]> > >
