JIRA Version 4.0 - Issues with IE 10

Nithin K February 26, 2014

Hi , I am a end user using JIRA and the version used is Atlassian JIRA (v4.0#466). Currently upgraded my IE to IE 10 and facing below issues.

I ma facing below two issue when using JIRA with IE 10. Request you to please let us know is there any IE 10 specific settings to be used s that below issues are resolved by the same.

1> When entering a ticket in JIRA using Subcategory down arrow, it collapses and does not allow for selecting one. However it allows to select one when editing the ticket.

Also you have to do a lot of F5 screen refresh to get from screen to screen in JIRA. It gets hung while doing attachments, logging a ticket, etc. Then you end up with duplicates because it really did it but would not refresh to show you.

2> When doing a search or when viewing search results using IE10 , getting below error(part of the error message):

System Error
A system error has occurred.
Please try submitting this problem via the Support Request Page
Otherwise, please create a support issue on our support system at http://support.atlassian.comwith the following information:
1. a description of your problem
2. cut & paste the error and system information found below
3. attach the application server log file ( C:\WINDOWS\system32\atlassian-jira.log )
Cause:
javax.servlet.ServletException: Including component failed:org.apache.jasper.JasperException: GC overhead limit exceeded at org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:433) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:355) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:679) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:584) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:497) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:965) at org.apache.jsp.template.standard.filter_002dlist_jsp._jspx_meth_webwork_005fiterator_005f0(filter_002dlist_jsp.java:277) at org.apache.jsp.template.standard.filter_002dlist_jsp._jspx_meth_webwork_005fif_005f0(filter_002dlist_jsp.java:229) at org.apache.jsp.template.standard.filter_002dlist_jsp._jspx_meth_webwork_005fproperty_005f1(filter_002dlist_jsp.java:189) at org.apache.jsp.template.standard.filter_002dlist_jsp._jspService(filter_002dlist_jsp.java:115) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at

Thanks & Regards,

Nithin Kumar

3 answers

0 votes
Nithin K March 10, 2014

Team,

Was looking at the steps for database migration from HSQL. However the steps states that attachments will be lost. Please let me know if there is any way we can migrate to different database by retaining the existing attachments.

  1. Create an export of your data as an XML backup. See Backing Up Data for details.
    (warning) Please note that JIRA's XML backup utility does not back up attachments (if you have attachments enabled).

Thanks

0 votes
Radu Dumitriu
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 5, 2014

Nic is right, but the second error is 'GC overhead limit exceeded', which really means the JVM is doing too much GC and little usable work - it has nothing to do with IE. I think you should revise the JVM params, too.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 5, 2014

So. Much. To. Fix. :-)

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 26, 2014

I'm sorry, but this isn't going to get you very far. IE10 is not supported because Jira 4 is too old to be worth bodging IE10 specific workarounds in.

Your options are

  • Use a proper browser
  • Use an older version of IE
  • Upgrade Jira

Nithin K March 5, 2014

Team,

Thanks a lot. We are working on the options of upgrading JIRA.

Request you to please let us know if there is any support contact whom we can contact for suggestions.

In current version of JIRA, we are using HSQL as our database and our plan is to use SQL server with latest version of JIRA. Hence wanted to know how to migrate the tickets from older version to newer version.

Also please share any documents are availaible related to upgrading JIRA from older to newer version.

Thanks & Regards,

Nithin Kumar

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 5, 2014

Well, you can try raising a support call, but the advice you get will be along the lines of:

1. Get off HSQL now. It is completely unsuitable for production systems and you should never have used it for production. Forget upgrading until you are on a supportable database server.

2. Upgrade (it's not a case of migrating - Jira can do most of the upgrading for you by simply taking your existing data and reprocessing it. So most upgrades are "copy database, point new Jira at old data". But you could lose it all if you try it with HSQL)

See https://confluence.atlassian.com/display/JIRA/Switching+Databasesfor your more urgent task, then move on to https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA

Suggest an answer

Log in or Sign up to answer