From 9a5f9a2e295efbdcb143d03ceda320ae484534af Mon Sep 17 00:00:00 2001 From: Jim Hahn Date: Thu, 24 Oct 2019 10:17:07 -0400 Subject: Handle DB error codes in distributed locking The commons library wraps the SQLExceptions within its own SQLException, so changed the code to simply look for a cause that's SQLTransientException, eliminating the need to check specific error codes. Deleted the error code property now that it is no longer needed. Also updated the distributed locking properties to include examples. Issue-ID: POLICY-2113 Signed-off-by: Jim Hahn Change-Id: If46e85a81cfc952e561174fea670df81efb8309a --- .../src/test/resources/feature-distributed-locking.properties | 1 - 1 file changed, 1 deletion(-) (limited to 'feature-distributed-locking/src/test/resources') diff --git a/feature-distributed-locking/src/test/resources/feature-distributed-locking.properties b/feature-distributed-locking/src/test/resources/feature-distributed-locking.properties index 061cc608..0fca3c04 100644 --- a/feature-distributed-locking/src/test/resources/feature-distributed-locking.properties +++ b/feature-distributed-locking/src/test/resources/feature-distributed-locking.properties @@ -23,7 +23,6 @@ javax.persistence.jdbc.url=jdbc:h2:mem:pooling javax.persistence.jdbc.user=user javax.persistence.jdbc.password=password -distributed.locking.transient.error.codes=500 distributed.locking.expire.check.seconds=900 distributed.locking.retry.seconds=60 distributed.locking.max.retries=2 -- cgit 1.2.3-korg