In-place DB Upgrade fails for Delegated Directories to Crowd 2.0.4

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

症状

  • After an in-place DB upgrade, users have not been migrated over in your Delegated Directories.
  • You may see this error in the logs:
    
    2010-07-01 13:35:57,461 main FATAL [crowd.console.listener.UpgradeListener] Failed to initialise Crowd container
    java.lang.IllegalArgumentException: argument credential cannot be null
            at org.apache.commons.lang.Validate.notNull(Validate.java:203)
            at com.atlassian.crowd.integration.model.user.UserTemplateWithCredentialAndAttributes.<init>(UserTemplateWithCredentialAndAttributes.java:25)
            at com.atlassian.crowd.migration.legacy.database.UserMapper.importUsersFromDatabase(UserMapper.java:108)
            at com.atlassian.crowd.migration.legacy.database.UserMapper.importFromDatabase(UserMapper.java:44)
            at com.atlassian.crowd.migration.legacy.database.DatabaseMigrator.importDatabase(DatabaseMigrator.java:38)
            at com.atlassian.crowd.migration.legacy.database.DatabaseMigrator$$FastClassByCGLIB$$20c39eb4.invoke(<generated>)
            at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
    

原因

This is caused by a bug that's been fixed. See In-place DB Upgrade fails for Delegated Directories to Crowd 2.0.4.

ソリューション

  1. Roll-back to the original database before the upgrade attempt.
  2. Use Crowd 2.0.5 or higher in the next upgrade attempt.

最終更新日 2012 年 11 月 21 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.