[
https://issues.apache.org/jira/browse/AMBARI-21000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035198#comment-16035198
]
Hudson commented on AMBARI-21000:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7566 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7566/])
AMBARI-21000. Ambari does not work with PGBouncer/PostgreSQL. (Robert (swagle:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4283211592c6813e02d74b7ef801da39711042cb])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/scheduler/ExecutionSchedulerImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
> Ambari does not work with PGBouncer/PostgreSQL
> ----------------------------------------------
>
> Key: AMBARI-21000
> URL: https://issues.apache.org/jira/browse/AMBARI-21000
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.5.2
> Reporter: Robert Yokota
> Fix For: 2.5.2
>
> Attachments: AMBARI-21000.01.patch
>
>
> When using JDBC with PGBouncer (a connection pooler for PostgreSQL), prepared
> statements must be disabled on the client side. According to the PgBouncer
> FAQ, this is done by passing "prepareThreshold=0" in the JDBC URL. Even when
> using "prepareThreshold=0", Ambari returns errors of the form "prepared
> statement "S_1" does not exist". This is because Ambari uses Quartz, which
> uses C3P0. Quartz by default configures C3P0 to cache prepared statements by
> setting maxStatementsPerConnection=120. Fortunately, Quartz also allows you
> to override this C3P0 setting by passing a property named
> "maxCachedStatementsPerConnection". When setting this property to 0 (which
> is the default in C3P0), then Ambari works properly with PGBouncer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
