Problems wie Umlaute in the API

[Martin Schmalz]

Hello,

im running JIRA (8.20.25) on a local Server in a Docker-Container. Im trying to create an Issue with the API. The Statement with no Umlauts works fine. So User, token etc. is OK.

But if i add an Umlaut (like ä or ö), i get this Errormessage: "Invalid UTF-8 middle byte 0xf6\n at [Source: org.apache.catalina.connector.CoyoteInputStream@3cf15376;"

• i set the /etc/default/locale (for jira-user and root) to LANG="de_DE.UTF-8" and LC_ALL="de_DE.UTF-8" (packages langauge-pack-de + -de-base are installed)
• i exportet LANG an LC_ALL in the setenv.sh
• i set jvm-rec-args: ${JVM_SUPPORT_RECOMMENDED_ARGS:="-Dfile.encoding=utf-8 -Dsun.jnu.encoding=UTF-8 -Duser.language=de -Duser.country=DE"}
• i added 'URIEncoding="UTF-8"' to the connector in the server.xml(.j2)
• i set the contenttype in the api-json to  --header "Content-Type: application/json;charset=UTF-8"
• webwork.i18n.encoding in Database an webwork.properties is utf-8

I still get the Error and i have no idea what is causing it. 

Can anybody help?

*thx*

[Andy Heinzer · Accepted solution]

Hi @Martin Schmalz 

I understand you are seeing this error in a Jira server 8.20.x version.   The steps you have taken so far look good from what I recall of these settings.  The aspect I am still unclear about is, how is the database setup for this Jira?  Was this docker image created by Atlassian? or is this a custom docker?

Unfortunately, Atlassian has end-of-life all Jira Server editions (Jira Data Center is still supported).  But also the 8.20.x line has also been end-of-life'd several months ago.  Being this product is at the end of support, that may limit what we can do in this case.  That said, I'm interested to try to learn more to see if we can help.

My hunch is that if the database collation and/or encoding is setup to use some other value aside from UTF-8, it's possible that the data in the API request can't accurately be saved to the database when this happens.  But if that were the case, then perhaps the Jira application logs might be more helpful in providing a better error message, such as a SQL exception when this happens.  I'd try to check that log file when this API call is made.  Perhaps with some digging into the logs we can find a clue as to why the application is throwing this as an invalid byte error.

There are steps on how the database should be setup in Connecting Jira Applications to a database - however depending the database type there are correspond guides for each (mysql, postgres, oracle, MS SQL).  Using a docker might obscure this database creation aspect, as I don't know what database type this might be.  But before we go down this road, I would suggest checking the logs Jira creates when this error happens, I think it will tell us more.

Andy

[Dan Breyen]

Hi Martin, I'm going to include Atlassian Support for this issue.  I searched Atlassian's Jira Site and didn't find this specific issue, but I did find other issues using the umlaute.