Hi,

I am experiencing a problem with the database connection pooling on
James, 2.2.0a9. I have recently increased the number of threads for the
RemoteDelivery mailet from 20 to 40, in order to cope with increased
server load.

However, I soon experienced the following exception while spooling mail
onto James:

10/10/03 07:39:03 INFO  James.Mailet: RemoteDelivery: Exception caught
in RemoteDelivery.run()
org.apache.commons.dbcp.DbcpException: java.sql.SQLException:
Communication failure during handshake. Is there a server running on
127.0.0.1:3306?
        at
org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverC
onnectionFactory.java:85)
        at
org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableCon
nectionFactory.java:184)
        at
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(Unknown
Source)
        at
org.apache.commons.dbcp.AbandonedObjectPool.borrowObject(AbandonedObject
Pool.java:117)
        at
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSourc
e.java:110)
        at
org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.ja
va:312)
        at
org.apache.james.util.dbcp.JdbcDataSource.getConnection(JdbcDataSource.j
ava:208)
        at
org.apache.james.mailrepository.JDBCMailRepository.getConnection(JDBCMai
lRepository.java:945)
        at
org.apache.james.mailrepository.MimeMessageJDBCSource.getInputStream(Mim
eMessageJDBCSource.java:163)
        at
org.apache.james.core.MimeMessageWrapper.writeTo(MimeMessageWrapper.java
:287)
        at
org.apache.james.core.MimeMessageWrapper.writeTo(MimeMessageWrapper.java
:271)
        at
com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:390)
        at
org.apache.james.transport.mailets.RemoteDelivery.deliver(RemoteDelivery
.java:346)
        at
org.apache.james.transport.mailets.RemoteDelivery.run(RemoteDelivery.jav
a:797)
        at java.lang.Thread.run(Thread.java:534)
Caused by: java.sql.SQLException: Communication failure during
handshake. Is there a server running on 127.0.0.1:3306?
        at org.gjt.mm.mysql.MysqlIO.init(Unknown Source)
        at org.gjt.mm.mysql.Connection.connectionInit(Unknown Source)
        at org.gjt.mm.mysql.jdbc2.Connection.connectionInit(Unknown
Source)
        at org.gjt.mm.mysql.Driver.connect(Unknown Source)
        at
org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverC
onnectionFactory.java:83)
        ... 14 more

Naturally, the first step was to increase the maximum number of
connections in the <data-source> block of config.xml, which I increased
from 20 to 50. The problem has however persisted, and I have had to go
back to my earlier configuration, which runs without exceptions but
causes a backlog in the spool. I am running Mysql 3.23 on the backend.
The number of threads for the spoolmanager is currently 20. All
repositories (except the inbox on dbfile) use a db repository.

Any help to increase the scaling on this server would be appreciated.

Thanks,
Craig




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to