Bug 724778 (BRMS-616)

Summary: When starting server, using ModeShape as repo, error - Supertype 'nt:hierarchyNode' from type 'drools:configurationNodeType' does not exist
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Van Halbert <vhalbert>
Component: ModeshapeAssignee: Kurt Stam <kurt.stam>
Status: CLOSED WORKSFORME QA Contact:
Severity: unspecified Docs Contact:
Priority: high    
Version: BRMS 5.2.0-Dev1CC: psiroky, rhauch, vhalbert
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-616
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-12 18:28:11 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:
Attachments:
Description Flags
modeshape-config.xml
none
modeshape-brms-store-ds.xml none

Description Van Halbert 2011-06-29 17:55:45 UTC
securitylevel_name: Public

When starting the server, when ModeShape is used as the repo, the following error is seen in the log:

2011-06-29 12:48:32,553 ERROR [org.modeshape.jcr.RepositoryNodeTypeManager] (modeshape-start-repo-2-thread-1) Node types were read from the system content, and appear to be inconsistent or invalid: org.modeshape.jcr.nodetype.InvalidNodeTypeDefinitionException: Supertype 'nt:hierarchyNode' from type 'drools:configurationNodeType' does not exist

Restarted server after deleting the default/data/modeshape directory, and still see the error.

Comment 1 Van Halbert 2011-07-12 13:13:29 UTC
Can you attached the modeshape configuration, if its been changed from the default.

Comment 2 Randall Hauch 2011-07-12 13:13:37 UTC
Can you please include a link to the configuration file?

Comment 3 Van Halbert 2011-07-12 13:17:04 UTC
Default delivered configuration.

Comment 4 Van Halbert 2011-07-12 13:17:04 UTC
Attachment: Added: modeshape-config.xml


Comment 5 Van Halbert 2011-07-12 13:27:11 UTC
ModeShape brms hsql datasource file

Comment 6 Van Halbert 2011-07-12 13:27:11 UTC
Attachment: Added: modeshape-brms-store-ds.xml


Comment 7 Van Halbert 2011-07-12 14:06:57 UTC
Link: Added: This issue Cloned to BRMS-634


Comment 8 Randall Hauch 2011-07-12 17:44:06 UTC
I've written a unit test in ModeShape's codebase that:
# starts a new engine (using a disk-based JPA source),
# loads the Drools node types,
# gets all of the available node types (which would include the built-ins plus the Drools node types)
# shuts down the engine
# starts up a new engine (using the same disk-based JPA source),
# gets all of the available node types (which would include the built-ins plus the Drools node types)
# compares the node types from step 3 and step 6, making sure that the node types match

I cannot get the test case to fail. Furthermore, based upon the information in this defect, we should be getting an error in step 5, and we are not.

It's strange that the error message reports that the 'nt:hierarchyNode' cannot be found, because that is a built-in node that is always available. This error makes no sense to me at all.


Comment 10 Van Halbert 2011-07-12 18:27:25 UTC
Try to replicate by running within JBoss AS 5.1.   Changed modeshape-config.xml to add the drools related .cnd files

Tried the order that BRMS uses:

                <mode:resource>configuration_node_type.cnd</mode:resource>
		<mode:resource>tag_node_type.cnd</mode:resource>
		<mode:resource>state_node_type.cnd</mode:resource>
		<mode:resource>versionable_node_type.cnd</mode:resource>
		<mode:resource>versionable_asset_folder_node_type.cnd</mode:resource>
                <mode:resource>rule_node_type.cnd</mode:resource>
                <mode:resource>rulepackage_node_type.cnd</mode:resource>

and tried the order that modeshape using in integration tests:

                <mode:resource>versionable_node_type.cnd</mode:resource>	
                <mode:resource>versionable_asset_folder_node_type.cnd</mode:resource>
                <mode:resource>rule_node_type.cnd</mode:resource>
                <mode:resource>rulepackage_node_type.cnd</mode:resource>
                <mode:resource>state_node_type.cnd</mode:resource>
                <mode:resource>tag_node_type.cnd</mode:resource>					
                <mode:resource>configuration_node_type.cnd</mode:resource>

and neither produced the error.

Going to replace the modeshape in BRMS with the version I used to see if the issue still occurs.