[
http://jira.codehaus.org/browse/CONTINUUM-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197409#action_197409
]
Andreas Christoforides commented on CONTINUUM-2302:
---------------------------------------------------
I believe the problem is related to mySQL and the way the database connection
pool was set-up.
We added the following settings to our datasource configuration in Tomcat:
1. The setting "autoReconnect=true" on the JDBC url parameter
2. A new parameter validationQuery="SELECT 1"
> Error when running scheduler:
> org.jpox.exceptions.TransactionNotActiveException: Transaction is not active
> ----------------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-2302
> URL: http://jira.codehaus.org/browse/CONTINUUM-2302
> Project: Continuum
> Issue Type: Bug
> Components: Core system
> Affects Versions: 1.2.3, 1.3.3
> Environment: CentOS 5. Tomcat 5.5.25 and mySQL 5
> Reporter: Andreas Christoforides
> Fix For: Backlog
>
> Attachments: Stacktrace.txt
>
>
> The attached exception occurs when trying to run a schedule. The error
> prevents the schedule from running and as a result all
> builds associated with that schedule do not run! Builds need to run manually
> which defeats one of the main reasons of having a CI server.
> This problem existed in version 1.2.3 and I was hoping that a fresh install
> (new database) of 1.3.3 would eliminate the problem.
> However, week after the upgraded it started happening again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
