You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
My Jira is v9.4.2, after adding the following line to the {{Jira_installed_directory}}/bin/setenv.sh
#JVM_SUPPORT_RECOMMENDED_ARGS="-XX:+UseG1GC -XX:+ExplicitGCInvokesConcurrent -Duser.language=en -Duser.country=US -Dcom.atlassian.jira.st rict.transport.security.include.subdomains.enabled=true"
And executed {{Jira_installed_directory}}/bin/stop-jira.sh, Jira seemed to not stop correctly.
And the I executed {{Jira_installed_directory}}/bin/start-jira.sh, it shows as follows:
Using CATALINA_PID: /opt/atlassian/jira/work/catalina.pid
Existing PID file found during start.
Removing/clearing stale PID file.
Tomcat started.
And I check the {{Jira_home_directory}}/log/atlassian-jira.log, the tail keeps showing the following message:
2023-03-29 10:34:07,467+0000 FelixShutdown DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] ungetService bundle [com.microsoft.teams.microsoft-teams]
2023-03-29 10:34:08,684+0000 FelixShutdown DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] ungetService bundle [com.porzelt.jira.simpletemplates.CannedIssues]
2023-03-29 10:34:09,442+0000 FelixShutdown INFO [c.a.c.e.c.b.jira.cmj.IssueSecuritySchemeCachingServiceImplCache] Cache com.botronsoft.jira.cmj.IssueSecuritySchemeCachingServiceImplCache was flushed
2023-03-29 10:34:10,434+0000 FelixShutdown INFO [c.a.c.e.c.b.jira.cmj.NotificationSchemeCachingServiceImplCache] Cache com.botronsoft.jira.cmj.NotificationSchemeCachingServiceImplCache was flushed
2023-03-29 10:34:10,434+0000 FelixShutdown INFO [c.a.c.e.c.b.jira.cmj.PermissionSchemeCachingServiceImplCache] Cache com.botronsoft.jira.cmj.PermissionSchemeCachingServiceImplCache was flushed
2023-03-29 10:34:10,434+0000 FelixShutdown INFO [c.a.c.e.c.b.jira.cmj.WorkflowsCache] Cache com.botronsoft.jira.cmj.WorkflowsCache was flushed
2023-03-29 10:34:10,435+0000 FelixShutdown INFO [c.a.c.e.c.b.jira.cmj.WorkflowSchemeCachingServiceImplCache] Cache com.botronsoft.jira.cmj.WorkflowSchemeCachingServiceImplCache was flushed
2023-03-29 10:34:12,132+0000 FelixShutdown DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] ungetService bundle [com.atsistemas.jira.addons.convalpos.workflow-magic-box]
And Jira cannot be accessed, how should I do to resolve this question?
Thanks
Finally, I refer to the Server startup logs which are located in "/opt/atlassian/jira/logs/catalina.out" and found out the root cause.
This issue is due to there is one line "XXXXX ADD-->" to be the end of the block comment.
After changing the "XXXXX ADD-->" to "-->", and then Jira can start normally.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.