There has been some recent tuning on the Datasource definition (not sure if this will help).

The configuration is now (in spring-server.xml)

<bean id="datasource" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close"> <property name="driverClassName" value="${database.driverClassName}" />
        <property name="url" value="${database.url}" />
        <property name="username" value="${database.username}" />
        <property name="password" value="${database.password}" />
<!--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"/>
    </bean>

Eric


On 13/02/12 16:43, Kendrick C. Wilson wrote:

No.

I am connecting via java mail.

Kendrick C. Wilson



From: [email protected]
To: [email protected]
Subject: RE: James 3.0 Version
Date: Mon, 13 Feb 2012 15:01:21 +0000

Kendrick,

Are you using the Vlogin plugin as well?

Thanks!

-----Original Message-----
From: Kendrick C. Wilson [mailto:[email protected]]
Sent: Monday, February 13, 2012 9:59 AM
To: [email protected]
Subject: RE: James 3.0 Version


I did that also.....

Kendrick C. Wilson


From: [email protected]
To: [email protected]
Subject: RE: James 3.0 Version
Date: Mon, 13 Feb 2012 14:41:46 +0000

I am currently researching the exact same problem.

I have tried appending autoReconnect=true and create=true in 
database.properties and that did not help.

I am hoping someone has a solution.

I am running apache-james-3.0-beta2.

Thanks,

Cindy

-----Original Message-----
From: Kendrick C. Wilson [mailto:[email protected]]
Sent: Monday, February 13, 2012 9:32 AM
To: [email protected]
Subject: James 3.0 Version


I am having a problem with James maintaining communication with a MySql db 
server after sometime(8 hours).
This is forcing us to restart James.
To reproduce....1) start mysql2) start james3) stop mysql4) start mysql5) 
request something from james
Is there a way to force James to reconnect to the database?
Thanks.
Kendrick C. Wilson




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

                                        

--
eric | http://about.echarles.net | @echarles

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to