Bug 1373187 - [GSS](6.4.z) The datasource statistics-enabled=true does not persist after a server reload or restart
Summary: [GSS](6.4.z) The datasource statistics-enabled=true does not persist after a ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: jbossas
Version: 6.4.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Fedor Gavrilov
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-05 12:50 UTC by Prageetika Sharma
Modified: 2019-12-16 06:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-25 16:33:05 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-7520 0 Major Closed [GSS](7.1.z) The datasource statistics-enabled=true does not persist after a server reload or restart 2017-04-10 12:22:49 UTC

Description Prageetika Sharma 2016-09-05 12:50:05 UTC 
Description of problem:
When enable the datasource statistics using CLI, the statistics-enabled=true does not persist after a server reload or restart.

[standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS/statistics=pool:write-attribute(name=statistics-enabled,value=true)
{"outcome" => "success"}

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


How reproducible:


Steps to Reproduce:
1. Enable the datasource statistics using CLI
2. Reload the server
3. After restarting the server, datasource statistics is disabled .

Actual results:
statistics-enabled=false after reload of server

Expected results:
statistics-enabled=true after reload of server

Additional info:
Comment 4 Peter Palaga 2016-11-25 16:33:05 UTC 
Closing as NOTABUG here for 6.4.x, because (citing bstansberry) "the attribute is described as not being persistent in the read-resource-definition output" and making it persistent would be a "management API change" that we cannot commit in a CP. Anyway, the issue was filled for EAP 7.1 https://issues.jboss.org/browse/JBEAP-7520
Note You need to log in before you can comment on or make changes to this bug.