auto-commit keeps LabKey 15.3 from starting

Installation Forum (Inactive)
auto-commit keeps LabKey 15.3 from starting bill c white  2015-11-25 19:26
Status: Closed
 
I have setup LabKey several times (13.3, 14.1, 14.2, 14.3), and the 15.3 webapp is running, but this time I can't get past this JDBC error on first access. The labkey user has superuser access. I added the defaultAutoCommit line to try and resolve it, but no go. Any ideas? Thanks.

Linux insilico 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Java 8 (installed apt-get PPA)
Tomcat 7 (installed apt-get)
PostgreSQL 9.3 (installed apt-get)
LabKey 15.3 (download and fresh install to /usr/local/labkey)

labkey.xml data source section:

   <Resource name="jdbc/labkeyDataSource" auth="Container"
        type="javax.sql.DataSource"
        defaultAutoCommit="true"
        username="labkey"
        password="l@bk3y"
        driverClassName="org.postgresql.Driver"
        url="jdbc:postgresql://localhost/labkey"
        maxActive="20"
        maxIdle="10"
        accessToUnderlyingConnectionAllowed="true"
        validationQuery="SELECT 1"
        />

Configuration Error Detected at LabKey Server Startup

A database connection is in an unexpected state: auto-commit is false. This indicates a configuration problem with the datasource definition or the database connection pool.

This is a problem with your configuration. Please contact your local server administrator for assistance, or LabKey Software at support@labkey.com for operational assistance with correcting the configuration error.

org.labkey.api.util.ConfigurationException: A database connection is in an unexpected state: auto-commit is false. This indicates a configuration problem with the datasource definition or the database connection pool.
       at org.labkey.api.data.DbScope._getConnection(DbScope.java:737)
.
 
 
Jon (LabKey DevOps) responded:  2015-11-25 22:33
Hi Bill,

The XML looks fine.

With your previous instances of LabKey, did you utilize the OS Package Manager for those versions of Tomcat or did you use a downloaded tar.gz installed version instead? I know from personal past experiences with other applications that the OS Package Manager versions seem to never work 100% perfectly in one way or another and I've had to download the zip or tar.gz file and install it instead.

Any chance you can update Tomcat with the tar.gz installer from Apache's website and give it another try?

Regards,

Jon
 
bill c white responded:  2015-11-26 08:09
Yes, I have always used the package manager, but I can try the tarball approach. Thanks.
 
jeckels responded:  2015-11-26 08:10
Hi Bill,

To add to Jon's comments, we've seen differences in the database connection pool implementations in particular between the OS package managers and the direct Tomcat download. As this has caused subtle issues in the past, we've gotten more aggressive at detecting potential incompatibilities in newer versions, which seems like what's happening here.

Thanks,
Josh
 
bill c white responded:  2015-11-26 08:16
Which version of Tomcat do you suggest for LK 15.3?
 
jeckels responded:  2015-11-26 08:57
Hi Bill,

15.3 supports both Tomcat 7 and 8, and we recommend using the latest release in either version. Since you're installing fresh, I'd suggest going with Tomcat 8.

https://www.labkey.org/wiki/home/Documentation/page.view?name=supported

Happy Thanksgiving!

Thanks,
Josh
 
bill c white responded:  2015-11-26 10:34
Tomcat 8 it is.

Happy Thanksgiving to you too!

Bill
 
bill c white responded:  2015-11-30 18:33
We are up and running with the tarball Tomcat 8! Thanks again for the advice.