Jira Data Center startup failed due to MalformedURIException
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
要約
Jira Data Center startup failed with MalformedURIException causing problem starting listener for RMICachePeer:
2021-01-01 22:22:01,271+0800 localhost-startStop-1 ERROR [c.a.jira.startup.ComponentContainerLauncher] A fatal error occurred during initialisation. JIRA has been locked.
net.sf.ehcache.CacheException: Problem starting listener for RMICachePeer //abc_jira01:40001/com.atlassian.jira.task.TaskManagerImpl.taskMap. Initial cause was invalid authority: //abc_jira01:40001/com.atlassian.jira.task.TaskManagerImpl.taskMap
...
Caused by: java.net.MalformedURLException: invalid authority: //abc_jira01:40001/com.atlassian.jira.task.TaskManagerImpl.taskMap診断
The server's local hostname is used for inter-node communication while port 40001 is the default Ehcache port for Jira Data Center.
In Jira Data Center setup, the startup failed as it attempted to start the listener for RMICachePeer with its local hostname that ended up with MalformedURLException.
Jira server startup doesn't get block with the same as it doesn't use Ehcache.
However, URL with underscore is rejected by Jira as base URL or linked issue. Here are some other issues triggered by URL with underscore:
- Cannot login to JIRA when URL Contains an Underscore in Internet Explorer
- Activity Stream Breaks due to InvalidCharacterException
原因
Underscore is not recognise as a valid character in hostname, which can load to MalformedURLException.
ソリューション
Remove the underscore from server's local hostname and restart the Jira node.