Hi there, please take a thread-dump to see why its blocked...
Anything in the logs ? Bye, Norman 2011/9/15 Zach Cox <zcox...@gmail.com>: > We upgraded to James 3.0-beta3 on Tuesday night. Things worked fine > until around 9pm last night, where exactly the same problem started > occurring: mail would get spooled, but not processed. After > restarting James, some of the mail was then processed successfully, > but most was lost. > > We consider this an emergency situation for our company and need to > find a resolution ASAP. What kind of information can we provide to > help find a resolution? If financial resources need to be involved to > find a resolution or move things along, that is an option. > > Any help is most greatly appreciated. > > Thanks, > Zach > > > On Tue, Sep 13, 2011 at 12:41 PM, Norman Maurer > <norman.mau...@googlemail.com> wrote: >> No problems... >> >> If you still can replicate then please open a issue with a stack trace >> attached.. >> >> Bye, >> Norman >> >> >> 2011/9/13 Raju Buchi <raju.bu...@contentpilot.net>: >>> James 3.0-M2. I will try to stand up a new server with beta3 and see if I >>> can replicate the issue. >>> >>> Thanks >>> >>> - Raju >>> >>> On Tue, Sep 13, 2011 at 12:37 PM, Norman Maurer < >>> norman.mau...@googlemail.com> wrote: >>> >>>> Do you use beta3 ? >>>> >>>> Bye, >>>> Norman >>>> >>>> >>>> 2011/9/13 Raju Buchi <raju.bu...@contentpilot.net>: >>>> > Hello >>>> > >>>> > We are also facing exactly the same issues. Tried to debug my custom >>>> mailets >>>> > and seems to be everything is working fine. Logs did not show any >>>> exception >>>> > messages except it will always spool a mail and will never attempt to >>>> send >>>> > it. i.e. all mails are stuck in the spool. >>>> > >>>> > - Raju >>>> > >>>> > On Tue, Sep 13, 2011 at 12:20 PM, Zach Cox <zcox...@gmail.com> wrote: >>>> > >>>> >> We are having a severe problem with James 3.0-M2 where it will operate >>>> >> correctly for hours or days, and then all of a sudden it will not >>>> >> process a lot of the mail it spools. Sometimes it will not process >>>> >> *any* mail that it spools, and other times it will spool a bunch of >>>> >> mail, and then process others seemingly at random. I have to restart >>>> >> James to get that spooled mail to be processed. But even then, >>>> >> sometimes the spooled mail is completely lost after a restart. I have >>>> >> seen several other threads lately with similar problems, but they >>>> >> haven't helped our situation. >>>> >> >>>> >> We do not store mail in James for personal accounts and we have IMAP & >>>> >> POP3 disabled. Every inbound email has one of two things done to it: >>>> >> - it is processed locally by custom mailets & matchers >>>> >> - or it is relayed to our corporate Google Apps account >>>> >> >>>> >> A previous thread recommended checking all custom mailets and >>>> >> matchers. As far as I can tell, they are all working properly. There >>>> >> are no exceptions or errors in log/james-server.log, and in the >>>> >> scenario where James spools some mail & processes others, the mail >>>> >> that is processed is handled properly by our custom mailets & >>>> >> matchers. >>>> >> >>>> >> I've tried connecting to James JMX remotely via JConsole but have not >>>> >> been able to connect. Which port does James run JMX on? Any help >>>> >> with JMX would be appreciated. >>>> >> >>>> >> Does anyone have any other ideas about what we should look for? I >>>> >> noticed 3.0-beta3 is out now, were there fixes in beta3 related to >>>> >> mail being spooled but not processed? >>>> >> >>>> >> Thanks, >>>> >> Zach >>>> >> >>>> >> --------------------------------------------------------------------- >>>> >> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >>>> >> For additional commands, e-mail: server-user-h...@james.apache.org >>>> >> >>>> >> >>>> > >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >>>> For additional commands, e-mail: server-user-h...@james.apache.org >>>> >>>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >> For additional commands, e-mail: server-user-h...@james.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
