Don't stop controller on dmaap failure

Modified feature-pooling-dmaap so that it continues to work even
if it's unable to communicate with the internal DMaaP topic.  When
that happens, it simply starts processing locally, until communication
is re-established and it receives a bucket assignment.
Fixed typo in comment.
Added to comment for State.internalTopicFailed().
Removed extra space before @Ignore.

Change-Id: I9c851c66c9162c608f2df98e11d49fc526539434
Issue-ID: POLICY-878
Signed-off-by: Jim Hahn <jrh3@att.com>
11 files changed
tree: 3e89b22420e80f7be82db22460da72e2bb58feb9
  1. api-active-standby-management/
  2. api-state-management/
  3. feature-active-standby-management/
  4. feature-distributed-locking/
  5. feature-eelf/
  6. feature-healthcheck/
  7. feature-pooling-dmaap/
  8. feature-session-persistence/
  9. feature-simulators/
  10. feature-state-management/
  11. feature-test-transaction/
  12. packages/
  13. policy-core/
  14. policy-endpoints/
  15. policy-management/
  16. policy-utils/
  17. .gitignore
  18. .gitreview
  19. docker_build.sh
  20. docker_merge.sh
  21. docker_verify.sh
  22. INFO.yaml
  23. LICENSE.txt
  24. pom.xml
  25. README.md
  26. 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