[
https://issues.apache.org/jira/browse/AMBARI-12438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630809#comment-14630809
]
Hudson commented on AMBARI-12438:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3127 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3127/])
AMBARI-12438 - MySQL Connection Pooling Defaults Should Be Correct And Present
In ambari.properties (jonathanhurley) (jhurley:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a56a5912ac6947ba534a75e3b43e46ae35c0cbdb)
* ambari-server/src/main/python/ambari_server/dbConfiguration_linux.py
* ambari-server/src/test/python/TestAmbariServer.py
* ambari-server/src/main/python/ambari_server/serverConfiguration.py
> MySQL Connection Pooling Defaults Should Be Correct And Present In
> ambari.properties
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-12438
> URL: https://issues.apache.org/jira/browse/AMBARI-12438
> Project: Ambari
> Issue Type: Task
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-12438.patch
>
>
> The following are properties that are exposed via {{ambari.properties}} and
> which have hard coded defaults in the Java code but appear no where in
> {{ambari.properties}} in a default installation:
> {noformat}
> server.jdbc.connection-pool=c3p0
> server.jdbc.connection-pool.acquisition-size=5
> server.jdbc.connection-pool.max-age=0
> server.jdbc.connection-pool.max-idle-time=14400
> server.jdbc.connection-pool.max-idle-time-excess=0
> server.jdbc.connection-pool.idle-test-interval=7200
> {noformat}
> We should write these properties into {{ambari.properties}} at install-time
> when configuring the database. MySQL will get c3p0 by default while other
> database providers will get "internal" (JPA) as their pooling mechanism.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
