For completeness sake, here's the resolution of this issue:
We did find the double (and in one case triple) nodes in the public instance.
(There was just one of each in the author instance.) To find them we used the
export function in AdminCentral > Tools, then opened the XML file in an editor
and searched for the node name. (We also found them with xpath queries. We must
have made a mistake the first time.)
When we had the culprits, we deleted all of them with groovy scripts on the
public instance and reactivated them from the author instance.
Thanks for your help Jan,
Anne
On 12.06.2012, at 15:30, Will Scheidegger wrote:
> Hi Jan
>
> Thanks for the help. I don't see them neither with JCR queries nor by
> "walking" through the nodes with the Groovy console. That's why I thought
> that dumping the content to XML would not give my an other result. But I'll
> give that a try as soon as I'm on a broadband connection again. ;-)
>
> Thanks!
> -will
>
> On 12.06.2012, at 15:25, Jan Haderka wrote:
>
>> just because you don't see the node doesn't mean it doesn't exist. :)
>>
>> you can try to dump the workspace to xml and search that for the culprit.
>>
>> Also if this is any older version of Magnolia then the latest, you might
>> want to clean up mgnlSystem workspace as well.
>>
>> HTH,
>> Jan
>>
>> On Jun 11, 2012, at 4:57 PM, Will Scheidegger wrote:
>>
>>> Dear Magnolians
>>>
>>> We're experiencing big troubles with same named siblings in the DMS – don't
>>> ask me how they got there in the first place. We thought that they would
>>> only exist on the public instance, but… when I activate a branch one folder
>>> or document at the time, everything is fine. When I activate with sub
>>> nodes, I get:
>>>
>>> 2012-06-11 16:49:06,018 INFO
>>> info.magnolia.module.exchangesimple.ReceiveFilter : Moving content from
>>> /path/to/MyNode[2] to /path/to/MyNode/ due to activation request.
>>> 2012-06-11 16:49:06,027 ERROR
>>> info.magnolia.module.exchangesimple.ReceiveFilter : Exception caught
>>> javax.jcr.InvalidSerializedDataException: illegal node name:
>>> {http://www.jcp.org/jcr/sv/1.0}node: empty name: empty name
>>> at
>>> org.apache.jackrabbit.core.xml.SysViewImportHandler.startElement(SysViewImportHandler.java:137)
>>> at
>>> org.apache.jackrabbit.core.xml.ImportHandler.startElement(ImportHandler.java:165)
>>> at
>>> org.apache.jackrabbit.commons.xml.DefaultContentHandler.startElement(DefaultContentHandler.java:161)
>>> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
>>> Source)
>>> at
>>> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
>>> Source)
>>> at
>>> org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown
>>> Source)
>>> at
>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>>> Source)
>>> at
>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>>> Source)
>>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>>> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>>> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
>>> Source)
>>> at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
>>> at
>>> org.apache.jackrabbit.commons.xml.ParsingContentHandler.parse(ParsingContentHandler.java:62)
>>> at
>>> org.apache.jackrabbit.commons.AbstractSession.importXML(AbstractSession.java:354)
>>>
>>> So it seems as if a node with the same name would still exist on author.
>>> But neither in author nor in public a "[2]" node shows up at that path
>>> (tested with JCR queries). Any ideas how to debug and fix this?
>>> Thanks!
>>>
>>> -will
>>>
>>> ----------------------------------------------------------------
>>> For list details, see
>>> http://www.magnolia-cms.com/community/mailing-lists.html
>>> Alternatively, use our forums: http://forum.magnolia-cms.com/
>>> To unsubscribe, E-mail to: <[email protected]>
>>> ----------------------------------------------------------------
>>
>>
>>
>>
>> ----------------------------------------------------------------
>> For list details, see
>> http://www.magnolia-cms.com/community/mailing-lists.html
>> Alternatively, use our forums: http://forum.magnolia-cms.com/
>> To unsubscribe, E-mail to: <[email protected]>
>> ----------------------------------------------------------------
>>
>
>
>
> ----------------------------------------------------------------
> For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
> Alternatively, use our forums: http://forum.magnolia-cms.com/
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
>
>
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
