Update from 3.2r2 to 3.4 : imap failed

[altiva]

Hi,

after updating from 3.2r2 to 3.4 imap stopped working. All the folders gone unsubscribed and Thunderbird and Outlook only sync the first level of folder.

00:14:43,927 DEBUG [org.alfresco.repo.imap.ImapServiceImpl] [getFavouriteSites] There is no Favorite sites' list bound to transaction a19f55b5-9904-4cb9-bd74-59e07deb4801
00:14:43,938 DEBUG [org.alfresco.repo.imap.AlfrescoImapHostManager] 
java.lang.NullPointerException
        at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:881)
        at org.alfresco.repo.site.SiteServiceImpl.getSiteRoot(SiteServiceImpl.java:606)
        at org.alfresco.repo.site.SiteServiceImpl.listSitesImpl(SiteServiceImpl.java:769)
        at org.alfresco.repo.site.SiteServiceImpl.listSites(SiteServiceImpl.java:737)
‍‍‍‍‍‍‍‍‍

[root@ged alfresco-3.4.c]# cat /etc/redhat-release
CentOS release 5.5 (Final)
[root@ged alfresco-3.4.c]#

[root@ged alfresco-3.4.c]# java -version
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)
[root@ged alfresco-3.4.c]#


Please, HELP!

[cpotter]

Same problem for us (same error logs)

It happened during a migration from Alfresco 3.4a / Mandriva Linux 2010.0 / java version "1.6.0_18" (OpenJDK IcedTea6 1.8 ) to a Alfresco 3.4d / CentOS 5.5 / java version "1.6.0_17" (OpenJDK IcedTea6 1.7.5)

Any help/hint welcomed

Chris

[cpotter]

Same problem for us (same error logs)

It happened during a migration from Alfresco 3.4a / Mandriva Linux 2010.0 / java version "1.6.0_18" (OpenJDK IcedTea6 1.8 ) to a Alfresco 3.4d / CentOS 5.5 / java version "1.6.0_17" (OpenJDK IcedTea6 1.7.5)

Any help/hint welcomed

Chris

Issue has been submitted : https://issues.alfresco.com/jira/browse/ALF-8906

[mrogers]

That issue has already been resolved.   A work around may be to go into Share and create a single dummy site.

[cpotter]

That issue has already been resolved.   A work around may be to go into Share and create a single dummy site.

But we don't use share …. However we are using the Sites spaces for other purposes, therefore spaces exists under Sites/ and the problem is still there