Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

JVM error during jira tomcat server startup

Unrecognized VM option 'PrintGCDateStamps'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0

3 answers

Hi @Preethi Lakshmanan ,

It seems that you have configured the startup options in a way that is not supported by the java you are using.

Please check

For more information. 

This solution didn't resolve the issue. 


on which version did you start your jira? 8 or 11 ? 

Please, be aware the parameters was changed for the Java 9



So please share the ps aux | grep java 

or startup parameters 

preethi@Preethis-MacBook-Pro bin % ps

  PID TTY           TIME CMD

60102 ttys000    0:00.19 -zsh

62936 ttys000    0:00.03 /bin/bash ./okrapp up

63153 ttys000    0:41.13 docker-compose up

62371 ttys001    0:00.17 -zsh

65890 ttys001    1:55.45 ./ngrok start --all

63366 ttys002    0:00.16 -zsh

65167 ttys003    0:00.22 -zsh

66329 ttys004    0:00.16 -zsh

preethi@Preethis-MacBook-Pro bin % grep

usage: grep [-abcDEFGHhIiJLlmnOoqRSsUVvwxZ] [-A num] [-B num] [-C[num]]

[-e pattern] [-f file] [--binary-files=value] [--color=when]

[--context[=num]] [--directories=action] [--label] [--line-buffered]

[--null] [pattern] [file ...]

preethi@Preethis-MacBook-Pro bin % 

0 votes
Daniel Ebers Community Leader Jan 06, 2021

Hi @Preethi Lakshmanan

while you state you are still using Java 8 we see no evidence as from your posting nowhere a version number can be seen.

The following knowledge base article, indeed, states clearly this is happening when applying the parameter "PrintGCDateStamps" on Java 11.

Without deeper knowledge of your system I don't believe further analysis will be possible except from stating the above.

Best guess: check your file for occurrence of the "PrintGCDateStamps" flag and remove it accordingly - at least for a test.


Suggest an answer

Log in or Sign up to answer

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