Question
Warnings during server start up
I am getting the following warnings during server start up. It doesnt seem to affect the functionality though. Could you please help in understanding it and help in steps to remove this warning during server start up.
[3/6/18 12:25:01:484 CET] 00000016 SystemOut O 2018-03-06 12:25:01,484 [ was10000.bc] [ STANDARD] [ ] (res.CacheDataToCandidateMapper) WARN - Unable to load RULE-OBJ-MODEL WBC-DATA-RESOURCESETTINGS LOADCOMMONWBCRESOURCESETTINGS #20160726T150505.931 GMT due to Database-BadClassDef WBC-Data-ResourceSettings; This may cause the wrong rule to run during rule execution.
[3/6/18 12:25:01:546 CET] 00000016 SystemOut O 2018-03-06 12:25:01,546 [ was10000.bc] [ STANDARD] [ ] (res.CacheDataToCandidateMapper) WARN - Unable to load RULE-OBJ-MODEL WBC-DATA-RESOURCESETTINGS LOADFAULTSETTINGS #20150629T155330.808 GMT due to Database-BadClassDef WBC-Data-ResourceSettings; This may cause the wrong rule to run during rule execution.
[3/6/18 12:25:01:546 CET] 00000016 SystemOut O 2018-03-06 12:25:01,546 [ was 10000.bc] [ STANDARD] [ ] (res.CacheDataToCandidateMapper) WARN - Unable to load RULE-OBJ-MODEL WBC-DATA-RESOURCESETTINGS LOADFAULTSETTINGS #20150917T101115.246 GMT due to Database-BadClassDef WBC-Data-ResourceSettings; This may cause the wrong rule to run during rule execution.
[3/6/18 12:25:01:546 CET] 00000016 SystemOut O 2018-03-06 12:25:01,546 [ was10000.bc] [ STANDARD] [ ] (res.CacheDataToCandidateMapper) WARN - Unable to load RULE-OBJ-MODEL WBC-DATA-RESOURCESETTINGS LOADFAULTSETTINGS #20151231T115738.782 GMT due to Database-BadClassDef WBC-Data-ResourceSettings; This may cause the wrong rule to run during rule execution.
[3/6/18 12:25:01:546 CET] 00000016 SystemOut O 2018-03-06 12:25:01,546 [ was10000.bc] [ STANDARD] [ ] (res.CacheDataToCandidateMapper) WARN - Unable to load RULE-OBJ-MODEL WBC-DATA-RESOURCESETTINGS LOADFAULTSETTINGS #20160107T110432.503 GMT due to Database-BadClassDef WBC-Data-ResourceSettings; This may cause the wrong rule to run during rule execution.
[3/6/18 12:25:01:546 CET] 00000016 SystemOut O 2018-03-06 12:25:01,546 [ was10000.bc] [ STANDARD] [ ] (res.CacheDataToCandidateMapper) WARN - Unable to load RULE-OBJ-MODEL WBC-DATA-RESOURCESETTINGS LOADFAULTSETTINGS #20160116T182146.152 GMT due to Database-BadClassDef WBC-Data-ResourceSettings; This may cause the wrong rule to run during rule execution.
[3/6/18 12:25:01:546 CET] 00000016 SystemOut O 2018-03-06 12:25:01,546 [ was10000.bc] [ STANDARD] [ ] (res.CacheDataToCandidateMapper) WARN - Unable to load RULE-OBJ-MODEL WBC-DATA-RESOURCESETTINGS LOADFAULTSETTINGS #20160119T115322.599 GMT due to Database-BadClassDef WBC-Data-ResourceSettings; This may cause the wrong rule to run during rule execution.
[3/6/18 12:25:01:546 CET] 00000016 SystemOut O 2018-03-06 12:25:01,546 [ was10000.bc] [ STANDARD] [ ] (res.CacheDataToCandidateMapper) WARN - Unable to load RULE-OBJ-MODEL WBC-DATA-RESOURCESETTINGS LOADFAULTSETTINGS #20160701T130319.429 GMT due to Database-BadClassDef WBC-Data-ResourceSettings; This may cause the wrong rule to run during rule execution.
[3/6/18 12:25:01:546 CET] 00000016 SystemOut O 2018-03-06 12:25:01,546 [ was10000.bc] [ STANDARD] [ ] (res.CacheDataToCandidateMapper) WARN - Unable to load RULE-OBJ-MODEL WBC-DATA-RESOURCESETTINGS LOADFAULTSETTINGS #20160715T054646.548 GMT due to Database-BadClassDef WBC-Data-ResourceSettings; This may cause the wrong rule to run during rule execution.
Thanks for your reply.
But i don't mind a defect detecting configuration in place which posts this which i checked is not present in our DSS.
The two rules in question which are named here are : WBC-DATA-RESOURCESETTINGS!LOADFAULTSETTINGS
and WBC-DATA-RESOURCESETTINGS!LOADCOMMONWBCRESOURCESETTINGS were already removed. But are still shown under search and on opening them throw the below error:
Unable to open instance WBC-DATA-RESOURCESETTINGS!LOADCOMMONWBCRESOURCESETTINGS - Possible causes may be (1) Rule may no longer exist. (2) Availability of the rule may be set to No/Draft, Blocked or Withdrawn. (3) Circumstance of the rule may be preventing access. (4) Current date is not within the date range specified in the rule.
Hi Jagannath,
Thanks for posting on PSC,
The root cause of this problem is a defect/misconfiguration in the operating environment.Do you have any framework installation as well, if yes? Did you sync all the dependencies of other frameworks?
Also, have you installed "Pega Save Detect" in your environment earlier?
Verify it by checking DSS "PegaSaveDetect/TrackSaves" or "PegaSaveDetect/TrackDeletes" is false?
Hope it helps in identifying root cause at your end.
Regards,
Asif