Error after upgrade from 12.2.1 to 12.3.0 and back to 12.2.1

Experience Manager (PaaS/OnPrem)
1

Hello all,

I encounter an error when I upgraded from version 12.2.1 to 12.3.0, then when I want to go back to version 12.2.1 for some reason, I get the following error when I start the application .

09:40:46.256 [main] ERROR org.onehippo.cm.engine.ConfigurationServiceImpl - Failed to apply config
javax.jcr.RepositoryException: The following node type change contains non-trivial changes.Up until now only trivial changes are supported. (see javadoc for org.apache.jackrabbit.spi.commons.nodetype.NodeTypeDefDiff):
org.apache.jackrabbit.spi.commons.nodetype.NodeTypeDefDiff[
	nodeTypeName={http://www.hippoecm.org/hst/nt/2.1}prototypemeta,
	mixinFlagDiff=NONE,
	supertypesDiff=NONE,
	propertyDifferences=[
		org.apache.jackrabbit.spi.commons.nodetype.NodeTypeDefDiff$PropDefDiff[itemName={http://www.hippoecm.org/hst/nt/2.1}displayname, type=NONE, operation=NONE],
		org.apache.jackrabbit.spi.commons.nodetype.NodeTypeDefDiff$PropDefDiff[itemName={http://www.hippoecm.org/hst/nt/2.1}primarycontainer, type=NONE, operation=NONE],
		org.apache.jackrabbit.spi.commons.nodetype.NodeTypeDefDiff$PropDefDiff[itemName={http://www.hippoecm.org/hst/nt/2.1}applicationId, type=MAJOR, operation=REMOVED]
	],
	childNodeDifferences=[
	]
]

	at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.checkForConflictingContent(NodeTypeRegistry.java:947) ~[jackrabbit-core-2.16.1-h1.jar:2.16.1-h1]

Does anyone have an idea what the cause is and how I can fix it?

Regards,
Wim.

1 Like
2

Hi Wim,
In 12.3 there’s a new property hst:applicationId added to the [hst:prototypemeta] mixin, which is an allowed change. After you’ve upgraded, it is present in hst.cnd. If you then deploy an older version on the same database, it tries to sync it again, but removing a property definition is not an allowed change.

So you have to reinstate the 12.2.1 database for a full revert.
In general, deploying a previous version on an already upgraded database is not supported.

Regards, Jeroen

1 Like
3

Hello Jeroen,

Thanks for your quick response.
It is clear to me.

Kind regards,
Wim.

4

@WimKG Oh thank God i am not only one who is facing this error. But keep going we will get solution.