hard-code connection parameters in an attempt to get Hikari working

This commit is contained in:
Joshua Chaitin-Pollak
2015-03-12 03:45:17 -04:00
parent ce34a9d651
commit ec5ced8de8
3 changed files with 5 additions and 4 deletions

View File

@@ -1,3 +1,2 @@
version=1.1.2.BUILD-SNAPSHOT
version=1.1.2.AL2-SNAPSHOT
group=org.springframework.cloud

View File

@@ -202,7 +202,7 @@ public class Cloud {
* </pre>
*
* <p>
* If a there is only a single service of a given type (as defined by the {@link ServiceInfo.ServiceLabel}
* If a there is only a single service of a given type (as defined by the {link ServiceInfo.ServiceLabel}
* annoation's value of the corresponding {@link ServiceInfo} class), that service is aliased
* to the service type. Keys for such properties start in <code>cloud.services.&lt;service-type&gt;</code>.
* For example, if there is only a single MySQL service bound to the application, the service properties

View File

@@ -34,8 +34,10 @@ public class HikariCpPooledDataSourceCreator<SI extends RelationalServiceInfo> i
if (serviceConnectorConfig == null) {
// choose sensible values so that we set max connection pool size to what
// free tier services on Cloud Foundry and Heroku allow
target.setPropertyValue("maximumPoolSize", 4);
target.setPropertyValue("maximumPoolSize", 10);
target.setPropertyValue("connectionTimeout", 30000);
target.setPropertyValue("idleTimeout", 30000);
target.setPropertyValue("maxLifetime", 55000);
}
configurer.configure(basicDataSource, (DataSourceConfig)serviceConnectorConfig);
}