Uploaded image for project: 'Service Packs and Hot Fixes'
  1. Service Packs and Hot Fixes
  2. MNT-16712

Upgrading from 4.2.2 to 4.2.6.4 with Centera Connector patch RenameSiteAuthorityDisplayName fails

    Details

    • Type: Hot Fix Request
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: Centera Connector 1.0.5, 4.2.6.4
    • Fix Version/s: Centera Connector 1.0.7
    • Component/s: Centera Connector, Upgrades
    • Labels:
      None
    • Environment:
      RHEL
      Alfresco 4.2.6
      Centera 1.0.5-22

      Description

      Summary:
      Customer has Alfresco 4.2.2 in production with Centera Connector 1.0.1-11 working fine. When they attempt to upgrade to Alfresco 4.2.6.4 with Centera Connector 1.0.5-22 it fails at: org.alfresco.repo.admin.patch.impl.RenameSiteAuthorityDisplayName.applyInternal(RenameSiteAuthorityDisplayName.java:91)

      Both the connection pool and the content have been validated with the CASScript tool as valid. The output is listed below:

      CASScript>poolOpen 10.69.65.80,10.69.65.81?/sbaone/Centera_SDK/sbaone_preprod.pea 
      Attempting to connect to: 10.69.65.80,10.69.65.81?/sbaone/Centera_SDK/sbaone_preprod.pea 
      Connected to: 10.69.65.80,10.69.65.81?/sbaone/Centera_SDK/sbaone_preprod.pea 
      
      CASPool Properties: 
      Connection String: 10.69.65.80,10.69.65.81?/sbaone/Centera_SDK/sbaone_preprod.pea 
      Cluster Time: 2016.08.19 03:45:22 GMT 
      Buffer Size: 16384 
      Prefetch Buffer Size: 32768 
      Connection Timeout: 120000 
      Multi-Cluster Failover Enabled: True 
      Collision Avoidance Enabled: False 
      
      CASScript>clipopen EC9JA5D6OBC96eB87M5SJ09DSC8G419C6JC8TU0KA93UOREC394U0 
      
      Clip Properties: 
      Name: untitled 
      Creation Date: 2015.01.21 03:57:06 GMT 
      Size: 0 
      Number of Tags: 1 
      Number of Blobs: 0 
      Retention Class: 
      Retention Seconds: -1 
      Modified: False 
      EBR Enabled : False 
      

      Steps to reproduce:

      1. Install Alfresco 4.2.4.6 OOTB installer.
      2. Configure Alfresco to point to the 4.2.2 alf_data contentStore and the Alfresco Database
      3. Configure the Centera Connector according to documentation
      4. Start up Alfresco.

      Expected Results:
      Patching should complete and Alfresco should start up.

      Actual Results:

      Caused by: org.alfresco.service.cmr.repository.ContentIOException: 07170002 Failed to open centera channel: ContentAccessor[ contentUrl=centera://EC9JA5D6OBC96eB87M5SJ09DSC8G419C6JC8TU0KA93UOREC394U0, mimetype=application/octet-stream, size=0, encoding=UTF-8, locale=en_US]	
      at org.alfresco.enterprise.repo.content.centera.CenteraContentReader.getDirectReadableChannel(CenteraContentReader.java:105)
      at org.alfresco.repo.content.AbstractContentReader.getReadableChannel(AbstractContentReader.java:271)
      at org.alfresco.repo.content.AbstractContentReader.getContentInputStream(AbstractContentReader.java:375)
      	... 76 more
      
      *Caused by: com.filepool.fplibrary.FPLibraryException: tag should have a blob
      at com.filepool.fplibrary.FPTag.BlobReadPartial(Unknown Source)
      at com.filepool.fplibrary.FPTag.BlobRead(Unknown Source)
      at com.filepool.fplibrary.FPTag.BlobRead(Unknown Source)
      at org.alfresco.enterprise.repo.content.centera.CenteraContentReader.getDirectReadableChannel(CenteraContentReader.java:96)*
      ... 78 more
      (String), patch.renameSiteAuthorityDilayName(String)
      

      Additional Notes:

      Customer ran database validation from JConsole before upgrade attempt and it appears to be okay. When the attempted update fails the customer can roll back to Alfresco 4.2.2 and everything is fine including "EC9JA5D6OBC96eB87M5SJ09DSC8G419C6JC8TU0KA93UOREC394U0"

      It looks like the 'contentService' bean never gets created and the Centera client is not fully bootstrapped before the patch tries to read the content for patching with RenameSiteAuthorityDisplayName.java

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  closedbugs Closed Bugs (Inactive)
                  Reporter:
                  rpierce Ron Pierce
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 3 days, 5 hours, 5 minutes
                    3d 5h 5m

                      Structure Helper Panel