Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9924

[atlassian.plugin.webresource.DefaultResourceDependencyResolver] Cannot find web resource module for: com.atlassian.auiplugin:aui-experimental-expander

XMLWordPrintable

      The log is full of messages like this making quite hard to spot other important messages. 

       [atlassian.plugin.webresource.DefaultResourceDependencyResolver] Cannot find web resource module for: com.atlassian.auiplugin:aui-experimental-expander
2013-10-09 13:24:59,279 http-bio-8080-exec-71 WARN anonymous 804x433165x2 1t6sy38 10.80.118.156,10.80.16.78 /s/en_USgypgs5-418945332/854/21/b5d3e2fc3b0cdb86d9fbfe271217b034/_/download/contextbatch/js/gh-rapid-config,greenhopper-rapid-non-gadget,atl.general/batch.js [atlassian.plugin.webresource.DefaultResourceDependencyResolver] Cannot find web resource module for: com.atlassian.auiplugin:aui-experimental-expander
2013-10-09 13:24:59,279 http-bio-8080-exec-71 WARN anonymous 804x433165x2 1t6sy38 10.80.118.156,10.80.16.78 /s/en_USgypgs5-418945332/854/21/b5d3e2fc3b0cdb86d9fbfe271217b034/_/download/contextbatch/js/gh-rapid-config,greenhopper-rapid-non-gadget,atl.general/batch.js [atlassian.plugin.webresource.DefaultResourceDependencyResolver] Cannot find web resource module for: com.atlassian.auiplugin:aui-experimental-expander

      Work-around

      Using JIRA's logging configuration in the Administration screens, set the level of the package com.atlassian.plugin.webresource to ERROR. Because the package does not appear in the list by default, you'll have to add it manually.

            [JSWSERVER-9924] [atlassian.plugin.webresource.DefaultResourceDependencyResolver] Cannot find web resource module for: com.atlassian.auiplugin:aui-experimental-expander

            Pete Jaffe added a comment -

            Keep in mind that changing the logging levels through the Admin page only lasts until your JIRA server restarts. I also updated the log4
            j.properties file (referenced on that Logging page) to make the change stable across restarts until a permanent fix is available. Below is what I added to my file. I don't think location matters, but I put it at line 245 of my vanilla file (at the top of the "# CLASS-SPECIFIC LOGGING LEVELS" section):

            # Due to GHS-9924, elevate this logger's minimal logging level to ERROR
log4j.logger.com.atlassian.plugin.webresource = ERROR

            Pete Jaffe added a comment - Keep in mind that changing the logging levels through the Admin page only lasts until your JIRA server restarts. I also updated the log4 j.properties file (referenced on that Logging page) to make the change stable across restarts until a permanent fix is available. Below is what I added to my file. I don't think location matters, but I put it at line 245 of my vanilla file (at the top of the "# CLASS-SPECIFIC LOGGING LEVELS" section): # Due to GHS-9924, elevate this logger's minimal logging level to ERROR log4j.logger.com.atlassian.plugin.webresource = ERROR

            pascal lavoie added a comment -

            the work-around work. you just have to add the package, like it said in the description.

            thanks

            pascal lavoie added a comment - the work-around work. you just have to add the package, like it said in the description. thanks

            cflores1 added a comment -

            The work-around does not work. The com.atlassian.plugin.webresource does not appear in the logging configuration.

            cflores1 added a comment - The work-around does not work. The com.atlassian.plugin.webresource does not appear in the logging configuration.

            Michael Tokar added a comment -

            Apologies to everyone for the long delay. We will endeavour to fix this issue soon. In the mean time, I will update the description with a work-around.

            Thanks,
            JIRA Agile Team

            Michael Tokar added a comment - Apologies to everyone for the long delay. We will endeavour to fix this issue soon. In the mean time, I will update the description with a work-around. Thanks, JIRA Agile Team

            Bernhard Cygan added a comment -

            That is called "legendary service", get used to it.

            Bernhard Cygan added a comment - That is called "legendary service", get used to it.

            Peter Callies added a comment -

            Open, unassigned, 49 votes in a month, not even a comment from Atlassian! At a minimum, this logfile garbage makes it extremely, extremely, extremely difficult to troubleshoot real issues. C'mon Atlassian!

            Peter Callies added a comment - Open, unassigned, 49 votes in a month, not even a comment from Atlassian! At a minimum, this logfile garbage makes it extremely, extremely, extremely difficult to troubleshoot real issues. C'mon Atlassian!

            Bedub58 added a comment -

            I'm seeing this 5.2.11 belong with an error dialog box as documented in GHS-10021.

            Bedub58 added a comment - I'm seeing this 5.2.11 belong with an error dialog box as documented in GHS-10021 .

            Trevor Horsfall added a comment -

            Over a month old and still "Unassigned". That's pretty poor.

            Trevor Horsfall added a comment - Over a month old and still "Unassigned". That's pretty poor.

            Some User added a comment -

            I get this too bug with postgresql as the DB.

            Some User added a comment - I get this too bug with postgresql as the DB.

            Laszlo Kremer added a comment -

            Our log is also full with these. 6.3.2.2

            Laszlo Kremer added a comment - Our log is also full with these. 6.3.2.2

              mtokar Michael Tokar
              73f0b2e75f82 Sorin Sbarnea (Citrix)
              Affected customers:
              58 This affects my team
              Watchers:
              50 Start watching this issue

                Created:
                Updated:
                Resolved: