Bug 1088214

Summary:	Server fails to parse configuration with loader, cluster-loader
Product:	[JBoss] JBoss Data Grid 6	Reporter:	Tomas Sykora <tsykora>
Component:	Server	Assignee:	Tristan Tarrant <ttarrant>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Gencur <mgencur>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	jdg-bugs, mgencur
Target Milestone:	ER3
Target Release:	6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-26 14:04:41 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:
Bug Depends On:
Bug Blocks:	1092056

Description Tomas Sykora 2014-04-16 09:07:58 UTC

JDG server 6.3.0 fails to start due to obstacles during parsing the configuration specifying loader or cluster-loader element. 

This is regression from 6.2.1.CR3 (GA) to 6.3.0.DR1/2.

The issue is NOT present in latest ISPN upstream (April 18) = built upstream server can be started without any problems. No JIRA record for this issue as it seems product related.

Example of problematic config snippet:

<loader name="myLoader" class="org.infinispan.persistence.file.SingleFileStore" shared="false" preload="false"/>



Respective message:

10:51:33,071 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
	at org.jboss.as.server.ServerService.boot(ServerService.java:324) [jboss-as-server-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:253) [jboss-as-controller-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
	at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02]
Caused by: java.lang.IllegalArgumentException
	at org.jboss.dmr.StringModelValue.asBoolean(StringModelValue.java:154) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1]
	at org.jboss.dmr.ModelNode.asBoolean(ModelNode.java:262) [jboss-dmr-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1]
	at org.jboss.as.controller.SimpleAttributeDefinition.parse(SimpleAttributeDefinition.java:331) [jboss-as-controller-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
	at org.jboss.as.controller.SimpleAttributeDefinition.parse(SimpleAttributeDefinition.java:188) [jboss-as-controller-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
	at org.jboss.as.controller.SimpleAttributeDefinition.parseAndSetParameter(SimpleAttributeDefinition.java:243) [jboss-as-controller-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
	at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader_6_0.parseLoaderAttribute(InfinispanSubsystemXMLReader_6_0.java:1358)
	at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader_6_0.parseCustomLoader(InfinispanSubsystemXMLReader_6_0.java:690)
	at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader_6_0.parseCacheElement(InfinispanSubsystemXMLReader_6_0.java:477)
	at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader_6_0.parseLocalCache(InfinispanSubsystemXMLReader_6_0.java:283)
	at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader_6_0.parseContainer(InfinispanSubsystemXMLReader_6_0.java:135)
	at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader_6_0.readElement(InfinispanSubsystemXMLReader_6_0.java:47)
	at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader_6_0.readElement(InfinispanSubsystemXMLReader_6_0.java:28)
	at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]
	at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]
	at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:1024) [jboss-as-server-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
	at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:458) [jboss-as-server-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
	at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [jboss-as-server-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
	at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [jboss-as-server-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
	at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]
	at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]
	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.3.2.Final-redhat-1.jar:7.3.2.Final-redhat-1]
	... 3 more

10:51:33,075 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

Comment 2 Martin Gencur 2014-04-16 11:57:42 UTC

This is related to rebasing JDG 6.3 against EAP 6.2.2 GA. JDG now contains newer EAP components which are not able to parse the configuration properly. This rebase was clearly not done for upstream ISPN. That's why this issue does NOT appear neither in JDG 6.2.1 nor ISPN upstream. Only JDG 6.3 was rebased against latest EAP components. I'll investigate further what can be done to fix this.

Comment 3 Martin Gencur 2014-04-22 08:35:19 UTC

*** Bug 1089911 has been marked as a duplicate of this bug. ***

Comment 4 Tomas Sykora 2014-04-25 12:43:49 UTC

The fix didn't make it into ER1. Expecting in 6.3.0.ER2

Comment 5 Tomas Sykora 2014-05-13 11:31:34 UTC

Martin's fix is in place but the problem is still present in JDG ER2 product build. Strange.

Setting back to assigned.

Comment 6 Tomas Sykora 2014-05-13 11:52:27 UTC

ER2 distribution uses <subsystem xmlns="urn:infinispan:server:core:6.1" default-cache-container="local"> and 6.1 parser. Fix is not there.

Comment 7 Martin Gencur 2014-05-13 12:02:55 UTC

The problem is that the fix was only integrated for InfinispanSubsystemXMLReader_6_0.java but there's now a newer parser which does not have the fix: InfinispanSubsystemXMLReader_6_1.java

Comment 8 Tristan Tarrant 2014-05-13 12:07:00 UTC

Pushed corresponding fix for 6.1 parser

Comment 9 Tomas Sykora 2014-05-19 12:58:11 UTC

This is absolutely fantastic as it made to work properly next 2 child resource creation in JON!!!

Nice catch Martin!

(6.3.0.ER3)