Decision Management (ODM,ADS)

 View Only
  • 1.  ODM DS Nodes - XOM Changes Sync Issue

    Posted Fri February 05, 2021 07:33 AM
    Edited by Charan Paladugu Fri February 05, 2021 01:46 PM
    Below are ODM DS details that we use

    Version: Decision Server 8.9.1.0 , Decision Engine 1.40.5
    Patch level: Build #1 on 2017-10-11 14:45:02 Release status: COMMERCIAL
    Persistence Type: datasource (Oracle Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, Real Application Clusters, OLAP, Advanced Analytics and Real Application Testing options)
    Startup Time: Wed, 20 Jan 2021 06:16:29 GMT
    Last Update Time: Fri, 05 Feb 2021 12:09:24 GMT

    Lately, at the time of RuleApp deployment, we notice that the XOM changes we deploy for a few RuleApps don't sync to one of the two DS nodes we have configured. The node which is gone out of sync still refers to the old XOM (possibly from the cache), resulting in two variety of decisions by HTDS for the same Open API - JSON payload. To overcome this issue, we follow the below practice during the RuleApp deployment using the RES console, and we will make sure the RuleApp is making the correct decisions before we inform the client.

    1. Delete XOM
        a. XOM: XXXXXXXXXXXXXX-XOM-Domain.zip
        b. XOM: XXXXXXXXXXXXXX-XOM-Interface.zip
        c. XOM: XXXXXXXXXXXXXX-XOM-Support.zip

    2. Delete RuleApp
        a. File: XXXXXXXXXXXXXXRuleApp.jar

    3. Deploy XOM
        a. File: XXXXXXXXXXXXXX-XOM-Domain.zip
        b. File: XXXXXXXXXXXXXX-XOM-Interface.zip
        c. File: XXXXXXXXXXXXXX-XOM-Support.zip

    4. Update Library
        a. Library: ADAMgmtRuleApp_1.0
        b. XOM Reference: XXXXXXXXXXXXXX-XOM-Domain.zip
        c. XOM Reference: XXXXXXXXXXXXXX-XOM-Interface.zip
        d. XOM Reference: XXXXXXXXXXXXXX-XOM-Support.zip

    5. Deploy RuleApp
        a. File: XXXXXXXXXXXXXXRuleApp.jar
        b. Option: 'Increment RuleApp major version'

    However, yesterday, we noticed the same XOM sync issue for the RuleApp serving fine for a couple of months. We had to do a rolling restart of the nodes to fix the problem.

    Any idea what caused the issue to trigger?
    Anything on ODM WAS?
    Anything that helps to identify the issue using the Execution Unit Dump cache on the RES console?

    ------------------------------
    Charan Paladugu
    ------------------------------


  • 2.  RE: ODM DS Nodes - XOM Changes Sync Issue

    Posted Fri February 05, 2021 07:11 PM
    Hi,

    The logs in  RES Console and  each Execution Unit should show notification update sent and received at the INFO level.
    You should be able to determine if the RES Console is properly propagating the ruleset deployment information to each instance of XU.

    If you can't diagnose the issue please contact the ODM Support team with the following information: 

    How many RES Console instances do you have?
    What type of notification are you using JMX(default) or TCPIP?
    What is the cluster configuration?

    ------------------------------
    Alain Robert
    ------------------------------



  • 3.  RE: ODM DS Nodes - XOM Changes Sync Issue

    Posted Mon February 08, 2021 04:02 PM
    Edited by Charan Paladugu Sat February 13, 2021 10:07 PM
    Hello Alain,

    There was no deployment done last week. Still, we ran into the RuleMgrSvr node issue was gone out of the sync, and the corresponding node's XU serving the clients with the old XOM file, which had been deleted during the deployment done a couple of months ago. Can you direct me to a specific log file to find out the odd behavior or any idea what is going on?

    ------------------------------
    Charan Paladugu
    ------------------------------



  • 4.  RE: ODM DS Nodes - XOM Changes Sync Issue

    Posted Fri February 12, 2021 12:28 PM
    Edited by Charan Paladugu Sat February 13, 2021 10:05 PM
    I am working with IBM ODM L2 support; they recommend clearing class caches in WAS to resolve the out of sync XOM issue.

    ------------------------------
    Charan Paladugu
    ------------------------------