It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Migrated dev server data to production through xml back up and moved plugins and attachments

Hello ,

 

We have migrated Jira dev server data to production through xml back up and manually moved important files to productions . we doesn't move install directory files or we doesn't change any thing in both serves . After few hours our dev server is down and getting below error can any one help me out to resolve this issue and cause .

Jira Dev Down.PNG

1 answer

1 accepted

0 votes
Answer accepted

Hello Mahesh,

Thank you for reaching out.

After upgrading Apache Tomcat to version 8.5.32, we’ve added new properties to the server.xml file that allow Tomcat to accept requests with special characters. 

Depending on the version you exported your backup from, you might need to add these properties to your server.xml file, otherwise, I believe you might face the error you are describing.

We have a KB with more detailed information about this problem:

Changing server.xml to handle requests with special characters

Please, check the information provided in that KB to diagnose and confirm if this is the problem you are facing and try the suggested steps to fix it:

  1. Go to <Jira-installation-directory>/conf, and edit the server.xml file.
  2. Find all connectors your application is using. Just search for Connector in the file, or look at the example below. You're interested only in connectors whose protocol is set to HTTP and HTTPS (not AJP).
  3. Add relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;" to the connector properties in server.xml. 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.

P.S: Save a copy of your original XML file before uploading the changes to your JIRA application.

Let me know if this information helps.

@Petter Gonçalves yeah we noticed and same thing we have changed anyway thanks for your response stay in touch with for further queries , By the way you are able to support on confluence issues also .

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

The add-in you’ve been waiting for: Jira Cloud for Excel 🙌

Introducing Jira Cloud for Excel Here at the product integrations team at Atlassian, we are thrilled to announce the new Jira Cloud for Excel add-in! This add-in lets you export Jira data directly ...

954 views 8 25
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you