Unable add new decision service to Corticon Server since the Total Number of Rules exceeds the license limit with CcServerLicenseException

"CcServerLicenseViolationException: New Reactor could not be added because Total Number Of Rules exceeds Server License Total Rules.", when deploying/adding/loading decision services to Corticon using a cdd file ( although the number of rules deployed is less than the number of rules allowed by the license file)



 

The user has a perpetual license in axis/web-inf/lib folder.
The license jar allows the user TAG_MAX_NUMBER_OF_RULES = 100000
There are 14K rules spread across 10 Decision Services ( approximately 1k to 2k rulues per decision service ).
10 decision services are loaded using one cdd file.

9 out of the 10 decision services are deployed/loaded successfully by the cdd.

When the 10th decision service is deployed/loaded using the same cdd,  there is a CcServerLicenseException saying that their Rule Count exceeds License limitation. ( although only 14k rules are deployed and the license allows 100k rules to be deployed ).


 

 The issue seen with cdd and rule counts leading to the license exception has been identified as a defect.
The problem is in a line of code, which uses a += to calculate the proposed Rule Count rather than just an =. 

Current code: 
///////////////////////////////////////////// 
// Validate Rule Count 
liProposedDeployServicesRuleCount += lCcServerDeploymentObject.getRuleCount(); 


Proposed Change to fix the issue : 
///////////////////////////////////////////// 
// Validate Rule Count 
liProposedDeployServicesRuleCount = lCcServerDeploymentObject.getRuleCount(); 

Fixed in hot fix 5.3.4.2.

Use the following workaround:
Create a new cdd to split the decision services across cdd's. 
In this scenario: Break up the Decision Services into 2 CDD files (5 Decision Services in each), the CcServer will deploy all the Decision Services without an Exception.

Please note that as more decision services or more rules are added , based on the number of rules in the each decision service , the issue may re-surface with 2 cdd's .
In such situations it may be  ideal to split the decision services across more than 2 cdd's to overcome the license exception.