Bugfix, creating only one DmaapProducer 71/3671/2
authorPatrikBuhr <patrik.buhr@est.tech>
Tue, 12 May 2020 11:27:37 +0000 (13:27 +0200)
committerPatrikBuhr <patrik.buhr@est.tech>
Tue, 12 May 2020 14:10:26 +0000 (16:10 +0200)
commit083393d0affc7dca6a5cea89f4f9759801a91591
tree50f8c7fc91b620ea1f677abf078ea160e9630f0d
parent0b10c7fa768f05ae5146ce2f3a69998bb8f97a9f
Bugfix, creating only one DmaapProducer

Each DmaapProducer starts a thread that is never terminated.
This class works around that by only creating one DmaapProducer
and will reuse that.

Change-Id: I3f8f9369a948f1cb5e3ae119c62c03bf4f5d180a
Issue-ID: NONRTRIC-210
Signed-off-by: PatrikBuhr <patrik.buhr@est.tech>
policy-agent/config/application.yaml
policy-agent/pom.xml
policy-agent/src/main/java/org/oransc/policyagent/dmaap/DmaapMessageConsumer.java
policy-agent/src/main/java/org/oransc/policyagent/dmaap/DmaapRequestMessage.java
policy-agent/src/test/java/org/oransc/policyagent/ApplicationTest.java
policy-agent/src/test/java/org/oransc/policyagent/ConcurrencyTestRunnable.java
policy-agent/src/test/java/org/oransc/policyagent/dmaap/DmaapMessageConsumerTest.java
policy-agent/src/test/java/org/oransc/policyagent/dmaap/DmaapMessageHandlerTest.java
policy-agent/src/test/resources/test_application_configuration.json