Forums

Articles
Create
cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
  • Community
  • Q&A
  • Jira
  • Questions
  • Error with module when starting jira after upgrading jira 6.4 to jira 7.0.11 to version 7.12.3

it is possible to have Jira data into excel automatically????

MURUGESH S
November 3, 2023

Requirement example

1) Need to better understand reporting or, ideally, integration with excel.

2 )If we need to provide cash flow forecasts, we don’t have monthly or quarterly spend projections here. Could solve this via an excel integration?

1 answer

1 accepted

0 votes
Answer accepted
Andy Heinzer
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 Champions.
November 5, 2018

In regards to the plugins, some of these are no longer supported in the latest version of Jira, while others might just require an update.   In the process of doing the upgrade, it might just be best to temporarily remove these from the $JIRAHOME/plugins/installed-plugins/ folder so that you can at least get Jira started and upgraded first.  After Jira itself is working I'd then recommend trying to use the UPM in Jira in order to update/reinstall compatible versions of any plugins you might need for Jira.

 

As for the other major problem with Tomcat, this is a known problem when upgrading any version such as 7.12.1 or earlier versions to a higher version.  This is mentioned in the upgrade notes at https://confluence.atlassian.com/jiracore/jira-core-7-12-x-upgrade-notes-955179470.html

as well as the bug ticket https://jira.atlassian.com/browse/JRASERVER-67974

Both documents indicate the steps needed in order to make this work.  They involve making changes to your server.xml file for all the connectors you have there:

 

Workaround

  1. Open configuration file server.xml (should be in conf directory)
  2. Find all connectors your application is using
  3. Add ** relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>" to properties for example: 
    <Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443" acceptCount="100" disableUploadTimeout="true" bindOnInit="false"/>
  4. Restart Jira
    See KB for full details: changing server.xml to handle requests with special characters

 

Note: If you have more than one connector in that server.xml file, you will need to repeat step #3 for each of them.

Jonatan Bouillon
November 5, 2018

Thanks for the answer, I have tried to remove the plugin from the folder but it didn't work, maybe I didn't remove correctly.

To fix my problem, I ended up installing a new Jira in another folder without any existing pluging and it worked.

I realize that is not a good idea to inplace-upgrade with unsupported plugin.

It would have been a better idea to review each plugin and remove or disable those plugin before upgrade like suggested in the installation documentation.

I didn't needed the SVN, Autowatcher plugin with the new jira version anyway.

The problem was not related to the server.xml config and relaxed chars.

Like • eldar_guseinov likes this

Suggest an answer

Log in or Sign up to answer