Question
Wellsfargo
IN
Last activity: 26 Nov 2020 0:10 EST
Clear node level Data page cache through System management API NOT working
Clearing node level Data page cache through System management API NOT working. PFA...
Accepted Solution
Updated: 26 Nov 2020 0:08 EST
Pegasystems Inc.
AU
Hi @SantoshGollapudi !
There are some special characters in the page identifier - the spaces and the hash in particular. Try URL-encoding the node identifier before using it in the URL. From what I can see in your screenshot:
D_DemoList^RULE-DECLARE-PAGES D_DEMOLIST #20201124T105520.164
... URL encodes to ...
D_DemoList%5ERULE-DECLARE-PAGES%20D_DEMOLIST%20%2320201124T105520.164
... but I may not see the full identifier. Check that the corresponding GET request is successful first, and then try DELETE.
https://www.urlencoder.org/ is a convenient online tool for one-time URL encoding
Perficient
US
A 400 status response like that might be caused by an invalid page identifier string in the request, can you double check that the identifier you are using is correct?
The same error can also occur when the data page has not been loaded into memory, can you check if the page identifier works in the GET /nodes/{nodeID}/caches/declarative_page/nodepages/{pageIdentifier} API or shows up in the results of the GET /nodes/{nodeID}/caches/declarative_page/nodepages API?
Accepted Solution
Updated: 26 Nov 2020 0:08 EST
Pegasystems Inc.
AU
Hi @SantoshGollapudi !
There are some special characters in the page identifier - the spaces and the hash in particular. Try URL-encoding the node identifier before using it in the URL. From what I can see in your screenshot:
D_DemoList^RULE-DECLARE-PAGES D_DEMOLIST #20201124T105520.164
... URL encodes to ...
D_DemoList%5ERULE-DECLARE-PAGES%20D_DEMOLIST%20%2320201124T105520.164
... but I may not see the full identifier. Check that the corresponding GET request is successful first, and then try DELETE.
https://www.urlencoder.org/ is a convenient online tool for one-time URL encoding