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 <jrh3@att.com>
Change-Id: If46e85a81cfc952e561174fea670df81efb8309a
6 files changed
tree: a1aa4867c2922ff18ca4cdc8d39505ee28010efc
  1. api-active-standby-management/
  2. api-state-management/
  3. feature-active-standby-management/
  4. feature-controller-logging/
  5. feature-distributed-locking/
  6. feature-eelf/
  7. feature-healthcheck/
  8. feature-lifecycle/
  9. feature-mdc-filters/
  10. feature-pooling-dmaap/
  11. feature-session-persistence/
  12. feature-simulators/
  13. feature-state-management/
  14. feature-test-transaction/
  15. packages/
  16. policy-core/
  17. policy-management/
  18. policy-utils/
  19. releases/
  20. .gitignore
  21. .gitreview
  22. INFO.yaml
  23. LICENSE.txt
  24. lombok.config
  25. pom.xml
  26. README.md
  27. version.properties
README.md

Copyright 2018 AT&T Intellectual Property. All rights reserved. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE Full license text at https://creativecommons.org/licenses/by/4.0/legalcode

This source repository contains the ONAP Policy DroolsPDP code. To build it:

  1. using Maven 3
  2. git clone http://gerrit.onap.org/r/oparent and copy oparent/settings.xml to ~/.m2
  3. mvn clean install