[
https://issues.apache.org/jira/browse/JAMES-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117358#comment-13117358
]
Zach Cox commented on JAMES-1317:
---------------------------------
This should be fixed in 3.0-beta4. The fix has been working for us in
production for about 1.5 weeks now, no spooled-but-not-processed mail anymore.
You should do a jstack and ensure that the Camel and spooler threads are not
blocked anywhere they're not supposed to be.
You can use JMX and in MBeans, check out org.apache.james > component >
mailetcontainer > mailspooler > threadpool.
> Mail spooled but not processed
> ------------------------------
>
> Key: JAMES-1317
> URL: https://issues.apache.org/jira/browse/JAMES-1317
> Project: JAMES Server
> Issue Type: Bug
> Components: SpoolManager & Processors
> Affects Versions: 3.0-M1, 3.0-M2, 3.0-beta3
> Reporter: Raju Buchi
> Priority: Critical
> Fix For: 3.0-beta4
>
> Attachments: jstack.zip
>
>
> Mails sent to James server are spooled but they are not processed and sent
> out.
> The issue is similar to the one faced by Zach.
> The server seems to be working fine for a few hours or few days, but some
> time all the mails are spooled but they will not be processed and sent out.
> Restarted the server several times and some time a few of the mails will be
> processed and all the others are lost.
> As Norman suggested I have took a jstack trace.
> Please let me how we can resolve this issue
> Thanks
> - Raju
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
