Bug 1017035

Summary:	Change of Transaction object store requires restart (not just reload)
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Ondrej Chaloupka <ochaloup>
Component:	Domain Management	Assignee:	Tomaz Cerar <tcerar>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kremensky <pkremens>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	brian.stansberry, emuckenh, kkhan
Target Milestone:	DR6
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-28 15:40:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ondrej Chaloupka 2013-10-09 08:01:37 UTC

The transaction object store change requires restart of the server. Currently the reload is required after the CLI operation is done.

The operation should define restart required.

Comment 1 Brian Stansberry 2013-10-11 03:54:46 UTC

Not a client side issue, so CLI is not the correct component.

Comment 2 Brian Stansberry 2013-10-11 03:57:25 UTC

A number of attributes in TransactionSubsystemRootResourceDefinition (and perhaps in otehr resources in the subsystem) have .setFlags(AttributeAccess.Flag.RESTART_JVM) but then the write-attribute handler is ReloadRequiredWriteAttributeHandler.

Comment 3 Ondrej Chaloupka 2014-01-06 11:32:36 UTC

We have the same problem when switching from JTA to JTS
/subsystem=transaction:write-attribute(name=jts, value=true)

The restart should be required (but it is just reload).

Comment 6 Ondrej Chaloupka 2014-04-01 12:22:45 UTC

Thank you. The flag for restart required is set for setting the object store type and jts.
Verified for EAP 6.3.0.DR6