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

CLONE - Alfresco goes into read-only mode after changing "Share Hostname" in admin-settings and then restarting Alfresco.

    Details

    • Type: Service Pack Request
    • Status: Closed (View Workflow)
    • Resolution: Fixed
    • Affects Version/s: 4.2.5.1
    • Fix Version/s: 5.0.4
    • Component/s: Admin Console (Share)
    • Labels:
      None
    • Environment:
      Oracle, Postgres, Mysql.

      Description

      [Problem Description]
      admin-systemsettings page goes into read-only mode after changing "Share Hostname" and then restarting Alfresco.

      [Steps to reproduce]
      1. Install and start up Alfresco.
      2. Go to the admin-systemsettings page

      http://{host}:{port}/alfresco/service/enterprise/admin/admin-systemsettings

      3. Change the value of "Share Hostname", and Save it.
      4. Restart Alfresco
      5. Go to the admin-systemsettings page

      http://{host}:{port}/alfresco/service/enterprise/admin/admin-systemsettings

      6. Change the value of "Share Hostname" again, and try to save it.

      • Actual Behaviour
        We cannot save it with this error message. Please find the screenshot named error.png for further assistance.
        ERROR [org.springframework.extensions.webscripts.AbstractRuntime] [http-bio-8080-exec-1] Exception from executeScript - redirecting to status template error: 01020003 Access Denied. The system is currently in read-only mode.
        org.alfresco.repo.security.permissions.AccessDeniedException: 01020003 Access Denied. The system is currently in read-only mode. 
         
      • Expected Behaviour.
        We should be able to save with the changed value.

      [Additional Information]
      Once we get the error, we cannot fix the error until we change the value through JMX console (Alfresco > Configuration > sysAdmin > Attributes > share.host ), because it is a persistent JMX bean, otherwise these values are stored in
      database of alf_prop_string_value table as follows,

      id string_value                 string_end_lower string_crc
      27 share.host      share.host 3058882331
      28 127.0.0.1           127.0.0.1 3938641544

      These values does not exist until we start changing values through System Summary as that is a persistent JMX beans, otherwise these will be created only when we change the value. Also, when we change the value again through Jconsole, it will create an additional line at a time, rather than updating the existing value as follows,

      id string_value                 string_end_lower string_crc
      27 share.host      share.host 3058882331
      28 127.0.0.1           127.0.0.1 3938641544
      43 share.hostname02      share.hostname02 2196421571
      44 share.hostname03           share.hostname03 2473847950

      We can clean them up by one of the ootb schedule jobs named propTableCleanup job. Once we run it, only the latest one will remain as follows,

      id string_value                 string_end_lower string_crc
      27 share.host      share.host 3058882331
      44 share.hostname03           share.hostname03 2473847950

      But, the whole repository will be in read-only mode after restarting Alfresco after we clean them up by the job and update the latest one like this query. This could also be happened when we initialise database. Some of customers at implementation stage tends to initialise database, otherwise it is possible to get the read-only problem for the whole repository like the customer who requested this Jira.

      update alf_prop_string_value set string_value = '127.0.0.1' and string_end_lower = '127.0.0.1' where id = 44; 
      

      So, the only way we can recover is to change the value through JMX console as a work around.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                closedbugs Closed Bugs
                Reporter:
                kkono Kazuyuki Kono
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: