Bug 1308960 - Newly added parameters (PARTITION_EVENT_PURGE and RESOURCE_CONFIG_HISTORY_PURGE) do not have a description and it seems they do not work
Summary: Newly added parameters (PARTITION_EVENT_PURGE and RESOURCE_CONFIG_HISTORY_PUR...
Keywords:
Status: CLOSED DUPLICATE of bug 1290436
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Core Server
Version: JON 3.3.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Michael Burman
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On: 1308963
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-16 15:06 UTC by bkramer
Modified: 2019-09-12 09:56 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-17 16:45:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description bkramer 2016-02-16 15:06:12 UTC
Description of problem:
In System Settings page in JBoss ON 3.3.5 there are two new parameters: PARTITION_EVENT_PURGE and RESOURCE_CONFIG_HISTORY_PURGE. These parameters are mandatory but by default their value is not set. Also, although, we can assume what the meaning of these parameters are, there are no description on the page. 

When setting both parameters to 1 - I assumed that all partition events older then a day would be deleted. However, this is not a case. 

Version-Release number of selected component (if applicable):
JBoss ON 3.3.5

How reproducible:
Always

Steps to Reproduce:
1. Install JBoss ON 3.3.5
2. Navigate to JBoss ON UI -> Administration -> System Settings and set PARTITION_EVENT_PURGE and RESOURCE_CONFIG_HISTORY_PURGE to 1;
3. Save newly added values (having in mind a workaround from the Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1290436);
4. Wait for the Data Purge Job;

Actual results:
Nothing has been deleted. To confirm this, navigate to JBoss ON UI -> Administration -> Partition Events and confirm that the Total Rows number is not changed;

Expected results:
All events older then a day are deleted.


Additional info:

Comment 1 bkramer 2016-02-17 16:45:23 UTC

*** This bug has been marked as a duplicate of bug 1290436 ***


Note You need to log in before you can comment on or make changes to this bug.