cancel
Showing results for 
Search instead for 
Did you mean: 

'Multiple primary associations' exception

emil
Champ in-the-making
Champ in-the-making
Hi, Alfresco engineer, I am using Alfresco 1.4.1 now.
However, I encouter an strange exception during get children from category via webservice (calling categoryService.getChildren)

*************************************************************
the error log is:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString:
faultActor:
faultNode:
faultDetail:
   {http://www.alfresco.org/ws/service/classification/1.0}ClassificationFault:<ns1:errorCode>0</ns1:errorCode><ns1:message>Multiple primary associations:
   child: workspace://SpacesStore/57878ca1-3a83-11dc-b8d3-f920b0707297
   first primary assoc: ChildAssoc[ id=38162, parent=22246, child=37921, child name=4ada522a-3a87-11dc-b8d3-f920b0707297, child name crc=-1, assoc type={http://www.alfresco.org/model/content/1.0}contains, assoc name={http://www.ericsson.com.cn/model/content/1.0}content, isPrimary=true]
   second primary assoc: ChildAssoc[ id=38160, parent=22246, child=37921, child name=4aaaddab-3a87-11dc-b8d3-f920b0707297, child name crc=-1, assoc type={http://www.alfresco.org/model/content/1.0}contains, assoc name={http://www.ericsson.com.cn/model/content/1.0}content, isPrimary=true]</ns1:message>
   {http://xml.apache.org/axis/}exceptionNameSmiley Surprisedrg.alfresco.repo.webservice.classification.ClassificationFa...
   {http://xml.apache.org/axis/}stackTrace:
*************************************************************

It didn't happen in the first time but sometime.
How can I handle this?

//BR
Emil
2 REPLIES 2

emil
Champ in-the-making
Champ in-the-making
The scenario I got this exception is that contents were created via webservice API by a performance test.

The test case is that several threads concurrently create contents.
It is realy odd….

derek
Star Contributor
Star Contributor
Hi,

Does the problem persist on the latest 1.4.x?  There was a fix/workaround for the issue issue in 1.4.3.

Regards