summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJorge Hernandez <jh1730@att.com>2018-05-07 20:10:45 -0500
committerJorge Hernandez <jh1730@att.com>2018-05-07 20:32:04 -0500
commit66b23ab7056a9da529534cd069cc19111c9201f4 (patch)
tree118e23f33f63ba766b6e2178b39dcebeb810f564
parentc9116710c277a18515dc88cac36ba4bafcf17ead (diff)
fix PE DB transaction lock timeouts.
I hope this fixes all DB related issues that are being seen by integration teams. The failOver jdbc parameters + perhaps some changes in underlying code and persistence libraries may have been causing the PAP to become useless. A thread dump shows that a significant number of threads were in timed-wait state, waiting on a lock trying to acquire a connection. In SB07, the system became useless in terms wouldn't accept any transaction. These changes to the PE provided jdbc parameters seems to be behaving in the expected way, and the expectation is that fixes the problems (behavior is good in own OOM lab). It is thought that this may perhaps solve POLICY-773, POLICY-775, POLICY-779, and perhaps POLICY-776. Change-Id: Ib2319b68b5a503f61c2cb04998c549b7b97f9f31 Issue-ID: POLICY-777 Signed-off-by: Jorge Hernandez <jh1730@att.com>
-rw-r--r--config/pe/base.conf4
1 files changed, 2 insertions, 2 deletions
diff --git a/config/pe/base.conf b/config/pe/base.conf
index e5aec35f..a172fb7f 100644
--- a/config/pe/base.conf
+++ b/config/pe/base.conf
@@ -17,8 +17,8 @@ POLICY_LOGS=/var/log/onap
KEYSTORE_PASSWD=Pol1cy_0nap
JDBC_DRIVER=org.mariadb.jdbc.Driver
-JDBC_URL=jdbc:mariadb://mariadb:3306/onap_sdk?failOverReadOnly=false&autoReconnect=true
-JDBC_LOG_URL=jdbc:mariadb://mariadb:3306/log?failOverReadOnly=false&autoReconnect=true
+JDBC_URL=jdbc:mariadb://mariadb:3306/onap_sdk?connectTimeout=30000&socketTimeout=60000&log=true&sessionVariables=max_statement_time=30
+JDBC_LOG_URL=jdbc:mariadb://mariadb:3306/log?connectTimeout=30000&socketTimeout=60000&log=true&sessionVariables=max_statement_time=30
JDBC_USER=policy_user
JDBC_PASSWORD=policy_user