Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-1051

Confluence error: Illegal configuration. No default cache is configured

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 1.4.1
    • 1.4
    • Integration - Confluence
    • None

    • Sol10, Oracle10, Tomcat5.5.25, Confluence 2.8

      Confluence 2.8 was working fine with Crowd1.2.2. Having copied across the new crowd-ehcache.xml & replaced the old crowd jars with the single new one from the crowd 1.4 client distribution, confluence starts up fine but when trying to login I get the attached error ultimately complaining about the lack of default cache.

      Adding in the defaultCache from the old crowd-ehcache.xml to the end of the new file appears to resolve the stack traces - whether or not it's bypasses the new 'enhanced'? caches or not I've no idea...

        1. dashboard.action.htm
          25 kB
        2. crowd-ehcache.xml
          6 kB

            [CWD-1051] Confluence error: Illegal configuration. No default cache is configured

            James Deuchar added a comment -

            Hi Donna

            Nothing's appears to be broken at the moment with my 'copy/paste' hack - I'll take a look at 1.4.1 in due course

            Thanks

            James

            James Deuchar added a comment - Hi Donna Nothing's appears to be broken at the moment with my 'copy/paste' hack - I'll take a look at 1.4.1 in due course Thanks James

            DonnaA added a comment -

            Hi James,

            If you are still having cache issues with Crowd-integrated applications, please open a new support issue at http://support.atlassian.com. The crowd-ehcache.xml default cache issue has been resolved in Crowd 1.4.1.

            Cheers,
            Donna

            DonnaA added a comment - Hi James, If you are still having cache issues with Crowd-integrated applications, please open a new support issue at http://support.atlassian.com . The crowd-ehcache.xml default cache issue has been resolved in Crowd 1.4.1. Cheers, Donna

            DonnaA added a comment -

            Actually, sorry about that, please use the attached crowd-ehcache.xml file. CWD-937 is not related to this problem.

            Cheers,
            D.

            DonnaA added a comment - Actually, sorry about that, please use the attached crowd-ehcache.xml file. CWD-937 is not related to this problem. Cheers, D.

            DonnaA added a comment -

            Please try using the crowd-ehcache.xml file attached to CWD-937. This should resolve the issue.

            Thanks,
            Donna

            DonnaA added a comment - Please try using the crowd-ehcache.xml file attached to CWD-937 . This should resolve the issue. Thanks, Donna

            dahankzter added a comment -

            We performed the same upgrade today and we noticed the exact same error both in Confluence and Jira.

            As you say, adding an arbitrary default cache in the ehcache config makes the systems come up but whether the new cache features works as said i cannot say.

            We experience a nice speed increase in Confluence but Jira is still slow due to a veritable flood of permission queries.
            There is already an issue regarding this scheduled for another release i believe, CWD-772 if im not mistaken.

            dahankzter added a comment - We performed the same upgrade today and we noticed the exact same error both in Confluence and Jira. As you say, adding an arbitrary default cache in the ehcache config makes the systems come up but whether the new cache features works as said i cannot say. We experience a nice speed increase in Confluence but Jira is still slow due to a veritable flood of permission queries. There is already an issue regarding this scheduled for another release i believe, CWD-772 if im not mistaken.

              doflynn David O'Flynn [Atlassian]
              2ced05048fcf James Deuchar
              Affected customers:
              2 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: