Jira Data Center startup failed due to MalformedURIException
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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.
*Except Fisheye and Crucible
Summary
Jira Data Center startup failed with MalformedURIException causing problem starting listener for RMICachePeer:
1
2
3
4
5
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.taskMapDiagnosis
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:
Cause
Underscore is not recognise as a valid character in hostname, which can load to MalformedURLException.
Solution
Remove the underscore from server's local hostname and restart the Jira node.
Was this helpful?