Upgrade to JIRA 4.3.1+ Fails with 'Unprocessed Continuation Reference' Error

Symptoms

  1. The following appears in the atlassian-jira.log:

    2011-04-04 15:13:41,361 main INFO      [jira.upgrade.tasks.UpgradeTask_Build601] Migrating a valid User Directory configuration found in osuser.xml
    2011-04-04 15:13:41,432 main WARN      [jira.upgrade.tasks.UpgradeTask_Build601] Added migrated directory to JIRA: 'JIRA delegating internal directory'.
    2011-04-04 15:13:43,156 main ERROR      [atlassian.jira.upgrade.UpgradeManagerImpl] Errors during Upgrade Task: Migrate User Directory configuration
    2011-04-04 15:13:43,156 main ERROR      [atlassian.jira.upgrade.UpgradeManagerImpl] Errors occurred during upgrade:
    2011-04-04 15:13:43,156 main ERROR      [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Error: JIRA failed to connect to the LDAP server using 
    the configuration in the osuser.xml file. LDAP error: <br /> org.springframework.ldap.PartialResultException: Unprocessed Continuation Reference(s); 
    nested exception is javax.naming.PartialResultException: Unprocessed Continuation Reference(s); remaining name 'dc=mycompany,dc=com'
    
  2. Upgrading to the affected JIRA releases: 4.3.1 - 4.3.3

Cause

JIRA 4.3.1 - 4.3.3 are affected by a bug found in JRA-23969the upgrade task.

The below outlined workaround has been create to address this particular upgrade problem and shouldn't be used unless the bug from JRA-23969 is experienced

Workaround

  1. Generate valid backup of JIRA data.
  2. Perform normal in-place upgrade as outlined in our Upgrade Guide,
  3. Shutdown JIRA when similar error is recoded in the atlassian-jira.log:

    2011-04-04 15:13:43,156 main ERROR      [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Error: JIRA failed to connect to the LDAP server using 
    the configuration in the osuser.xml file. LDAP error: <br /> org.springframework.ldap.PartialResultException: Unprocessed Continuation Reference(s); 
    nested exception is javax.naming.PartialResultException: Unprocessed Continuation Reference(s); remaining name 'dc=mycompany,dc=com'
    
  4. Perform the SQL workaround:
    1. First check the Directory ID for your LDAP Auth directory:

      select * from cwd_directory where directory_type = 'DELEGATING'
      

      We expect the Delegated Directory to have an ID of 3, but best to confirm first.

    2. Now add the "Follow Referral" attribute:

      insert into cwd_directory_attribute 
        values (3, 'ldap.referral', 'true')
      

      Alter the "3" to your Directory ID if different.

    3. Additionally tag the 601 task as completed in the following way. Find id of the last record upgrade task:

      mysql> select max(id) from upgradehistory;
      +---------+
      | max(id) |
      +---------+
      |   10045 |
      +---------+
      1 row in set (0.00 sec)
      
    4. Increase the id by one and use it in the below insert statement:

      mysql> insert into upgradehistory (id, upgradeclass, targetbuild) values (10046, 'com.atlassian.jira.upgrade.tasks.UpgradeTask_Build601', 617);
      Query OK, 1 row affected (0.00 sec)
      
    5. Find record of the JIRA build number:

      SELECT
          propertystring.id, propertyvalue
      FROM
          propertystring
      INNER JOIN propertyentry
      ON
          (
              propertystring.ID = propertyentry.ID
          )
      WHERE
          propertyentry.PROPERTY_KEY = 'jira.version.patched' ;
      
      +-------+---------------+
      | id    | propertyvalue |
      +-------+---------------+
      | 10034 | 590           |
      +-------+---------------+
      1 row in set (0.00 sec)
      
    6. Update it to the 601 build:

      mysql> update propertystring set propertyvalue=601 where id=10034;
      Query OK, 1 row affected (0.00 sec)
      Rows matched: 1  Changed: 1  Warnings: 0
      
  5. Restart JIRA and let it continue with the upgrade process.

(info) Please see our Troubleshooting LDAP User Management documentation for further assistance with diagnosing LDAP problems.

Resolution

Upgrade to JIRA 4.3.4 release (when available).

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport