Your dbcp pool must be configured to have a bigger "max". Every
spoolthreads + smptserver threads + pop3server threads + remote delivery
threads can open db connections, so you have to increase it to support
your max numeber of threads.
About the recipients number issue this is probably a bug. Can you create
a JIRA issue for that?
Stefano
Marcello Marangio wrote:
Hi all
I have a james with all the repositories on a oracle db.
A am trying to perform a stress test: senting an email to 50 recipients.
It failed at the first attempt, because the recipients column in the spool
table is "only" a varchar2(1000).
I decreased the number of recipients to 27 (and 800 chars), and james
crashed:
javax.mail.MessagingException: Unable to parse stream:
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool
exhausted;
nested exception is:
java.io.IOException: org.apache.commons.dbcp.SQLNestedException:
Cannot get a connection, pool exhausted
at
org.apache.james.core.MimeMessageWrapper.loadMessage(MimeMessageWrapper.java
:151)
at
org.apache.james.core.MimeMessageWrapper.setHeader(MimeMessageWrapper.java:9
42)
......
Is it related to the "threads" parameter of the spoolmanager or something
about my db connections?
Marcello
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
