Description of problem: The subsystem=transaction/log-store=log-store has a 'probe' operation that inadvertently clears the 'type' attribute from the resource. How reproducible: Always Steps to Reproduce: 1. Invoke /subsystem=transaction/log-store=log-store:probe 2. Invoke /subsystem=transaction/log-store=log-store:read-resource Actual results: The 'type' attribute is undefined Expected results: The 'type' attribute should be defined Additional info: LogStoreProbeHandler replaces the 'delegate' held by LogStoreResource. Doing this removes any data from the existing delegate's 'model' field, i.e. the "type" attribute.
The steps to reproduce were incomplete. You only see the problem if the type attribute does not have value 'default'. So, before the step I listed, either add the <use-hornetq-store/> element to the transaction subsystem config, or do it via the CLI with batch /subsystem=transactions:write-attribute(name=use-hornetq-store,value=true) /subsystem=transactions:write-attribute(name=use-jdbc-store,value=false) run-batch reload
Thank you for the additional info about verification the issue. I've checked the behavior of EAP 6.3.0.ER3 and I have one cosmetic note about the failure behavior. After the probe() operation is run the type of the log-store is not put to 'undefined' but is changed back to default 'default' value.
Agreed. I've changed the text. Thanks!
Verified on EAP 6.3.0.ER4