Fixing issue where PdpHeartbeats are incorrectly processed by PAP 35/120935/1
authora.sreekumar <ajith.sreekumar@bell.ca>
Tue, 27 Apr 2021 15:51:45 +0000 (16:51 +0100)
committera.sreekumar <ajith.sreekumar@bell.ca>
Tue, 27 Apr 2021 15:51:53 +0000 (16:51 +0100)
commitcc70129c67ed6284c3d13593e6b19e19d73d3084
tree79d8f359c9d7d5f4593cfe9efc9a531e53f46829
parentcc6a0ac3a3f76de375aeb04bcc254208c70ce0be
Fixing issue where PdpHeartbeats are incorrectly processed by PAP

The below 2 issues are fixed in this review:
1) When updating the policiesToBeUndeployed, the policies list in the
   message itself was getting removed, which resulted in incorrect
   processing. This was the reason for continuos UPDATE and STATE_CHANGE
   messages from PAP to PDP.
2) In case if the policy list in heartbeat doesn't include one or more
   policies that are supposed to be deployed(as per DB), the PAP should
   send UPDATE messages to PDP asking to deploy them too. But this was
   not working as the policiesToBeDeployed list was not getting
   initialized properly before getting processed.

Change-Id: I06dbfd1d40bae8a510fc5500fbd38fb87c203c0d
Issue-ID: POLICY-3248
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
main/src/main/java/org/onap/policy/pap/main/comm/PdpStatusMessageHandler.java