You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Ioan Eugen Stan (Jira)" <se...@james.apache.org> on 2020/06/08 19:52:00 UTC
[jira] [Closed] (JAMES-799) dbcp causes "Address already in use:
connect" exception and server fails
[ https://issues.apache.org/jira/browse/JAMES-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ioan Eugen Stan closed JAMES-799.
---------------------------------
Resolution: Abandoned
Please reopen if still relevant. I'm on a cleaning spree.
> dbcp causes "Address already in use: connect" exception and server fails
> ------------------------------------------------------------------------
>
> Key: JAMES-799
> URL: https://issues.apache.org/jira/browse/JAMES-799
> Project: James Server
> Issue Type: Bug
> Components: MailStore & MailRepository
> Affects Versions: 2.3.1
> Environment: Windows XP, MySQL 4.1.22
> Reporter: Amichai Rothman
> Priority: Major
>
> I've tried using FromRepository servlet (manual one-time configuration) to migrate a file store with ~1.5K messages to a database store. however afte a few hundred inserts, the logs started filling with exceptions, whose root cause is "Address already in use: connect". After much investigation, I found out using netstat that there are thousands of ports open (all local - both JAMES and MySQL are on the same server), and as some googled post suggested, the available TCP ports may have been exhausted. The result was that some of the message never made it through the conversion - the logs showed that after 3 db connection retries JAMES gave up on them.
> I tried lowering the number of threads in the db source configuration, spool configuration, and default thread pool configuration (all in config.xml) but nothing helped. Eventually, I reverted all my configuration attempts, and applied the single change of using mordred instead of dbcp, and now everything works fine. I don't know if this is a JAMES or a dbcp bug, but it's definitely unacceptible for db connections to fail when there is a bit of load on the system (a few hundred messages).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org