1. Tempo Avatar Tempo
  2. Prime
  3. servertimesheet
  4. Issues

Getting NoViableAltException Exception in JIRA log when trying to eccess details of Project Pivot, Time Sheet and Worked Time Chart on Dashboard

Issue #585 resolved
Reetesh Kumar created an issue

Hi, We are using JIRA version 6.3.12 and "JIRA Timesheet Reports and Gadgets" Plugin version 2.8.2.6. (Screenshot TimesheetPlugin.png) We added Project Pivot, Time Sheet and Worked Time Chart on a dashboard. When we tried to access page Configure by clicking details > Configure (Screenshot Timesheet-Dashboard.png) then we are getting below error in the JIRA log file.

Please look into this issue

2015-01-08 15:16:05,553 http-bio-8080-exec-16 ERROR rkum66 915x6229x1 8izbjo 10.202.97.241,10.202.11.174 /secure/ConfigureReport!default.jspa [jira.issue.search.OfBizSearchRequestStore] A JQL query exception was thrown parsing, error loading search request with id '19011' and name 'ADR2 won't fix issues' owned by 'sroy' query 'issuetype = Defect AND resolution = "Won"t Fix" AND status = Closed AND reporter in (nesain, npal1, sroy14, hsin35, anmali, jtripa, anyada, skum56, ajindal3) AND created >= 2012-07-24 ORDER BY cf[10500] ASC, created ASC, key DESC'. 2015-01-08 15:16:05,553 http-bio-8080-exec-16 ERROR rkum66 915x6229x1 8izbjo 10.202.97.241,10.202.11.174 /secure/ConfigureReport!default.jspa [webwork.util.ValueStack] query="objectConfiguration/fieldValues(.)/empty" {[id="objectConfiguration" type="8" values=""]} {[id="fieldValues" type="10" values="query="." {[id="null" type="3" values=""]}"]} {[id="empty" type="8" values=""]} java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor635.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56) at webwork.util.ValueStack.findValue(ValueStack.java:417) at webwork.util.SimpleTest.test(SimpleTest.java:408) at webwork.util.SimpleTest.test(SimpleTest.java:518) at webwork.util.ValueStack.test(ValueStack.java:157) at webwork.view.taglib.ElseIfTag.doStartTag(ElseIfTag.java:45) at org.apache.jsp.secure.views.browser.configurereport_jsp._jspService(configurereport_jsp.java:354) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) <+2> (ApplicationFilterChain.java:303) (ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) <+11> (ApplicationFilterChain.java:241) (ApplicationFilterChain.java:208) (XContentTypeOptionsNoSniffFilter.java:22) (AbstractHttpFilter.java:31) (ApplicationFilterChain.java:241) (ApplicationFilterChain.java:208) (HeaderSanitisingFilter.java:32) (ApplicationFilterChain.java:241) (ApplicationFilterChain.java:208) (IteratingFilterChain.java:46) (DelegatingPluginFilter.java:70)

Comments (21)

  2. Andriy Zhdanov

    Hi Reetesh,

    Root cause seems to be: A JQL query exception was thrown parsing, error loading search request with id '19011' and name 'ADR2 won't fix issues' owned by 'sroy' query 'issuetype = Defect AND resolution = "Won"t Fix" AND status = Closed AND reporter in (nesain, npal1, sroy14, hsin35, anmali, jtripa, anyada, skum56, ajindal3) AND created >= 2012-07-24 ORDER BY cf[10500] ASC, created ASC, key DESC'.

    It's not clear though what's wrong with this query, but may be you can check within IssueNavigator.

    Note, I can add prevention of reports failing in this case, but problem really seems to be in the query.

    Thank you.

  4. Reetesh Kumar reporter

    Hi Andriy,

    We have corrected the JQL and this exception does not occur in log now. But we are facing one another issue

    When we tried to access page Configure by clicking details on Timesheet dashboard > Configure (Screenshot TimesheetDashboard.png) we are getting Proxy Error (Screenshot Proxy-Error.png). When we repeat the same again and again then we are getting "Proxy Error" maximum times and very few times it opens the correct configuration page (Screenshot TimesheetConfigurationPage.png). In order to resolve this issue we restarted Apache and JIRA server (After removing files .bundled-plugins and .osgi-plugins at /jira_install/jira_home/plugins) multiple times, but it did not get resolved. The Proxy Timeout is set 6000 seconds on Apache server. We have observed that we are not getting any error in JIRA log file related to this issue. Please find the screenshots and logs from attachment TimesheetLogs.

    Please suggest to the solution for this.

    Thanks, Reetesh

  7. Reetesh Kumar reporter

    Hi Andriy,

    The workaround solution is working for us. We applied this solution for only Filter option in both reports configuration screens. Can you please review the changes I did in the atlassian-plugin.xml file. Kindly, let us know, if there is any functional impact of this change (Except removal of drop down option of Filter field in Configure - Timesheet Report" page and in place of that input type text is there for field Filter). We did below changes in the atlassian-plugin.xml file.

    1. Searched for word filterid and this returned below set of text string in two places in this file: <property><key>filterid</key><name>report.timesheet.filterid.name</name><description>report.timesheet.filterid.description</description><type>select</type><values class="com.fdu.jira.util.OptionalSearchRequestValuesGenerator"/><default></default></property>

    AND

    <property><key>filterid</key><name>report.pivot.filterid.name</name><description>report.pivot.filterid.description</description><type>select</type><values class="com.fdu.jira.util.OptionalSearchRequestValuesGenerator"/><default></default></property>

    1. We did changes in the above set of text String. We removed <values class="com.fdu.jira.util.OptionalSearchRequestValuesGenerator"/><default></default> and replaced the <type>select</type> with <type>string</type>. After these change the text String is looking like below:

    <property><key>filterid</key><name>report.timesheet.filterid.name</name><description>report.timesheet.filterid.description</description><type>string</type></property>

    AND

    <property><key>filterid</key><name>report.pivot.filterid.name</name><description>report.pivot.filterid.description</description><type>string</type></property>

    Thanks, Reetesh

  8. Andriy Zhdanov

    Hi Reetesh,

    Looks good. Glad it works for you. Functional impact will be that for Filter option you will need to specify filter ID. This is very inconvenient, but hopefully rare case.

    Thank you.

  9. Reetesh Kumar reporter

    Hi Andriy,

    While testing the customized build of Timesheet plugin we found that the Filter field is accepting IDs in the “Configure Plugin” screen and returns the desired filter correctly. But providing Filter Name is Not working as we observe below NumberFormatException exception at the backend and the desired filter result is not shown in the configure screen as well.

    2015-01-12 12:45:39,581 http-bio-8080-exec-8 WARN rkum66 765x9045x1 1h55v4v 10.202.97.241,10.202.11.174 /secure/ConfigureReport.jspa [atlassian.jira.util.ParameterUtils] NumberFormatException looking for param: filterid

    Therefore kindly look into this issue to ascertain why Filter field is not accepting Filter Names properly and provide us a new build if required. I am attaching relevant logs/screenshots for reference (Timesheet_Support_Log.zip).

    Moreover we would also like to get the message appearing beneath the Filter field changed to the following sentence: “(Optional) Provide exact filter name to display report on.” Kindly include this change as well in the build you will provide after fixing this issue.

    Regards, Reetesh Kumar

  11. Reetesh Kumar reporter

    Hi Andriy,

    We have planned to roll out this plugin on our production environment this weekend and before that we need to test all required functionalities of this plugin. So, can you please suggest the solution as soon as possible?

  12. Andriy Zhdanov

    Hi Reetesh,

    Can you use patched 2.7.5 version as suggested in the workaround instead? Or you need latest version?

    Thank you.

  13. Former user Account Deleted

    Hello Andriy,

    Thanks for your help till now. Due to unavailability of Reetesh, I am doing follow-up on this today.

    As you have suggested that I can use patched 2.7.5 or latest version but thing is I am using 2.8.2.6 version of the plugin. I think 2.7.5 version will not going to help me.

    Please suggest if we have newer version of plugin available (having fix of above issues) than what I am using (2.8.2.6) now?

    Thanks, Kamal

  15. Former user Account Deleted

    Thanks Andriy, for your quick reply. Will the new version take care of the issues reported by Reetesh?

    Thanks, Kamal

  17. Former user Account Deleted

    OK, thanks.

    Due to this weekend release we are on critical path to this work. Meanwhile can you suggest any workaround to fix the issue reported which is "Providing Filter Name is Not working as we observe "NumberFormatException" exception in back-end logs" or I need to wait until new build?

    I need to communicate it to my higher management and users please suggest.

    Thanks, Kamal

  18. Andriy Zhdanov

    Sorry, this is an only workaround for the problem, solution is to update JIRA to 6.0.1 at least.

    I've made significant progress on patched version today, should be able to publish tomorrow.

    Thank you.

  21. Reetesh Kumar reporter

    Thanks Andriy. We will install and test this version and will let you know if we face any other issue.

  22. Log in to comment
Assignee
–
Type
bug
Priority
major
Status
resolved
Component
Configuration
Version
2.8
Votes
0
Watchers
1