[ALF-19094] Crash server by adding cyclic model to "Data Dictionary/Models" Created: 19-Jun-13  Updated: 27-May-16  Resolved: 26-May-16

Status: Closed
Project: Alfresco
Component/s: Repository
Affects Version/s: 4.2.c Community
Fix Version/s: None
Security Level: external (External user)

Type: Bug Priority: Major
Reporter: Matthieu Laborie (Inactive) Assignee: Closed Issues
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
is duplicated by MNT-15345 Dynamic Deployment of Models can caus... Closed
is related to by MNT-14332 Alfresco stops working when Type Hier... Closed
is related to by MNT-16279 Repo hangs if content model has a cir... Closed
Date of First Response:


Creating a model with cyclic import :

<model name="ncwf:claim-process"><author>beCPG</author><version>1.0</version>
<imports><import uri="http://www.alfresco.org/model/dictionary/1.0" prefix="d"/><import uri="http://www.alfresco.org/model/bpm/1.0" prefix="bpm"/><import uri="http://www.bcpg.fr/model/nc-workflow/1.0" prefix="ncwf"/></imports><namespaces><namespace uri="http://www.bcpg.fr/model/nc-workflow/1.0" prefix="ncwf"/></namespaces><data-types/><constraints/>

and deploy it into "Data Dictionnary/Models"

Make system crash and unrecoverable:

Caused by: java.lang.StackOverflowError
at org.alfresco.repo.dictionary.M2Model.getName(M2Model.java:170)
at org.alfresco.repo.dictionary.DictionaryRepositoryBootstrap.loadModel(DictionaryRepositoryBootstrap.java:489)
at org.alfresco.repo.dictionary.DictionaryRepositoryBootstrap.loadModel(DictionaryRepositoryBootstrap.java:489)


The only way to restart system is to modify repo-admin-context.xml to ignore "Data Dictionary/Models"


Comment by Derek Hulley [X] (Inactive) [ 19-Jun-13 ]

Do you have a patch with a suggested fix?

Comment by Matthieu Laborie (Inactive) [ 19-Jun-13 ]

No sorry

Comment by Derek Hulley [X] (Inactive) [ 19-Jun-13 ]

Admin task that is avoided by testing. Pushing to Product Management for evaluation.

Comment by Jan Vonka [ 19-May-16 ]

Richard Esplin [X] Just an FYI ...

Fix for MNT-15345 (duplicate) is targeted for Enterprise 5.1.1 SP. Hence, when that SP is released and then eventually merged to HEAD this issue can be re-opened and marked as fixed in a future Community build/release.

There are three semi-related fixes targeted for 5.1.1, namely: MNT-14332, MNT-15345MNT-16279.

Comment by Richard Esplin [X] (Inactive) [ 26-May-16 ]

@Jan Vonka Thank you for connecting this issue to the duplicates.

I'm was disappointed to see that I closed this as "Won't Fix" without a comment. I don't know what I was thinking.

It is now closed as "Duplicate", and connected with the issues that are progressing toward resolution.

Generated at Fri Apr 23 12:38:59 BST 2021 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.