[
https://issues.apache.org/jira/browse/JAMES-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188528#comment-13188528
]
Michael Herrmann commented on JAMES-1317:
-----------------------------------------
Okay, our final resolution of the problem was to set the maximum connection
size to 50.
Stefano and Norman, I think it is not unlikely that other James 3 users will
run into the same problem. Do you maybe want to consider setting at least some
of the following properties on James's datasource?
{noformat}
<!--The value for maxActive should always be larger than the number of
spooler threads. The-->
<!--reason is that a spooler thread normally requires 1 connection to
process a mail, however-->
<!--sometimes OpenJPA requires 1 connection to finish the processing on
top of that. If-->
<!-- maxActive <= num spooler threads,-->
<!--it can happen that the spooler threads grab all maxActive
connections but then cannot-->
<!--finish processing because each of them blocks waiting for OpenJPA
which itself is waiting-->
<!--for a connection. See
https://issues.apache.org/jira/browse/JAMES-1317.-->
<property name="maxActive" value="21"/>
<!-- This lets a mail fail to be processed rather than the server
freezing. -->
<property name="maxWait" value="30000"/>
<!-- This keeps the number of connections in the pool low on average -->
<property name="timeBetweenEvictionRunsMillis" value="300000"/>
<property name="minEvictableIdleTimeMillis" value="300000"/>
<property name="removeAbandoned" value="true"/>
<property name="logAbandoned" value="true"/>
<property name="removeAbandonedTimeout" value="300"/>
{noformat}
> 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: Dump.txt, Dump2.txt,
> james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar,
> james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar, jstack.zip,
> logs.zip, logs.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
