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

      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

            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.

            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

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

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

            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 .

            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.

            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

            I'm also seeing this issue, but I'm still running JIRA 5.2.2 so I'm guessing this is a greenhopper (JIRA Agile) bug since I'm up to date on that.

            Peter Callies added a comment - I'm also seeing this issue, but I'm still running JIRA 5.2.2 so I'm guessing this is a greenhopper (JIRA Agile) bug since I'm up to date on that.

            This log message is all over our log files too:

            $ grep "Cannot find web resource module for: com.atlassian.auiplugin:aui-experimental-expander" catalina.out | wc -l
            35774
            

            JIRA version: 6.0.5
            JIRA Agile version: 6.3.2.2

            Michael Richards added a comment - This log message is all over our log files too: $ grep "Cannot find web resource module for : com.atlassian.auiplugin:aui-experimental-expander" catalina.out | wc -l 35774 JIRA version: 6.0.5 JIRA Agile version: 6.3.2.2

            The REST error turned out to be unrelated, and ultimately caused by an Oracle driver issue. Since we are using Oracle 11.1.0.7.0, we used that version of ojdbc6.jar. I should note here that we are running Tomcat 7 and Java 7. When I saw an article indicating that JIRA recommends the 11.2.x drivers, I switched to 11.2.0.1 and the errors went away. The older driver has worked fine for our other Java web apps, so it might be good for JIRA Agile to document this somewhere in case anyone else has this issue.

            Michael Payne added a comment - The REST error turned out to be unrelated, and ultimately caused by an Oracle driver issue. Since we are using Oracle 11.1.0.7.0, we used that version of ojdbc6.jar. I should note here that we are running Tomcat 7 and Java 7. When I saw an article indicating that JIRA recommends the 11.2.x drivers, I switched to 11.2.0.1 and the errors went away. The older driver has worked fine for our other Java web apps, so it might be good for JIRA Agile to document this somewhere in case anyone else has this issue.

            Has anyone who is getting this WARN also gotten the following ERROR:
            "Unable to complete GreenHopper REST method java.lang.ArrayIndexOutOfBoundsException"? This usually displays in the interface as an Internal Server Error. At present this error is breaking most JIRA Agile functionality. I cannot find a reference to it in the bug database or answers, and am wondering if it could be linked to the "WARN". We are using JIRA v6.0.7, JIRA Agile v6.3.3.

            Michael Payne added a comment - Has anyone who is getting this WARN also gotten the following ERROR: "Unable to complete GreenHopper REST method java.lang.ArrayIndexOutOfBoundsException"? This usually displays in the interface as an Internal Server Error. At present this error is breaking most JIRA Agile functionality. I cannot find a reference to it in the bug database or answers, and am wondering if it could be linked to the "WARN". We are using JIRA v6.0.7, JIRA Agile v6.3.3.

            Any plan to fix this in near future

            Honeywell JIRA Admin added a comment - Any plan to fix this in near future

            I also get this error a lot, using Jira v6.0.8 and Jira Agile v6.3.3. The Hercules log scanner links to this ticket.

            Christian Grandsjö added a comment - I also get this error a lot, using Jira v6.0.8 and Jira Agile v6.3.3. The Hercules log scanner links to this ticket.

            A greenhopper issue? Version 6.0.3 of JIRA is exhibiting this behaviour.

            Stephen Welsh added a comment - A greenhopper issue? Version 6.0.3 of JIRA is exhibiting this behaviour.

            Carmen Nadeau added a comment - - edited

            We also are facing this, we just upgrade last night from 6.2 to 6.3.1 and the log is full of that warning everytime we click on a board.

            Carmen Nadeau added a comment - - edited We also are facing this, we just upgrade last night from 6.2 to 6.3.1 and the log is full of that warning everytime we click on a board.

            We are also facing this issue.Every time you access the board,this warning will come in the logs.

            Honeywell JIRA Admin added a comment - We are also facing this issue.Every time you access the board,this warning will come in the logs.

            This defect was introduced in JIRA Agile v6.3.1. The very first WARN event appeared in my log within 1 minute of the upgrade from v6.3.0.2

            At that time, I was running JIRA v5.2.2. I have since upgraded to JIRA v6.0.8 but the WARN events continue... 4800 so far.

            Mark Symons added a comment - This defect was introduced in JIRA Agile v6.3.1. The very first WARN event appeared in my log within 1 minute of the upgrade from v6.3.0.2 At that time, I was running JIRA v5.2.2. I have since upgraded to JIRA v6.0.8 but the WARN events continue... 4800 so far.

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

                Created:
                Updated:
                Resolved: