1 Reply Latest reply on Dec 7, 2012 8:08 AM by jgrasett

    Invalid namespace index after declustering

    jgrasett

      After running the declustering script, on startup we get a number of errors such as this:

      (Note: this is CRX version 2.1 running under WebSphere 6.1)

       

      [27/06/12 17:11:41:352 BST] 00000014 SystemOut O 27.06.2012 17:11:41 *ERROR* PersistenceManagerUtils: Failed to read bundle: cafebabe-cafe-babe-cafe-babecafebabe: java.lang.IllegalArgumentException: Invalid namespace index: 13 (PersistenceManagerUtils.java, line 94) java.lang.IllegalArgumentException: Invalid namespace index: 13

       

      [27/06/12 17:12:11:353 BST] 00000014 SystemOut O 27.06.2012 17:12:11 *ERROR* PersistenceManagerUtils: Failed to read bundle: 21232f29-7a57-35a7-8389-4a0e4a801fc3: java.lang.IllegalArgumentException: Invalid namespace index: 23 (PersistenceManagerUtils.java, line 94)java.lang.IllegalArgumentException: Invalid namespace index: 23

       

      [27/06/12 17:12:11:357 BST] 00000014 SystemOut O 27.06.2012 17:12:11 *ERROR* CRXRepositoryImpl: loadModules: Cannot initialize module com.day.crx.replication.ReplicationManager (CRXRepositoryImpl.java, line 454)

      javax.jcr.RepositoryException: failed to retrieve item state of item 21232f29-7a57-35a7-8389-4a0e4a801fc3

       

      and yet...it does say this:

       

      [27/06/12 17:12:11:403 BST] 00000014 SystemOut O 27.06.2012 17:12:11 *INFO * CRXRepositoryStartupServlet: CRXRepository successfully created. (CRXDiagnostic.java, line 233)
      [27/06/12 17:12:11:404 BST] 00000014 SystemOut O 27.06.2012 17:12:11 *INFO * RepositoryStartupServlet: Repository bound to JNDI with name: xxxxxxxxxxxxx (RepositoryStartupServlet.java, line 452)
      [27/06/12 17:12:11:405 BST] 00000014 SystemOut O 27.06.2012 17:12:11 *INFO * RepositoryStartupServlet: RepositoryStartupServlet initialized. (RepositoryStartupServlet.java, line 241)

      [27/06/12 17:12:11:405 BST] 00000014 ServletWrappe I   SRVE0242I: [xxxxxxxxxExplorer] [/crx] [Repository]: Initialization successful.

        • 1. Re: Invalid namespace index after declustering
          jgrasett Level 1

          We determined that the script, lacking in any error checking whatsoever, was not functioning properly, assuming certain directories existed when they did not, and hence not moving things correctly. I have since rewritten the script to test for and create destination directories, and skip missing source directories. Never did get the sed command to comment out clustering in the repository.xml to work though.