Hey all who wonder how this issue was resolved back in the day. Following is the my final response to support specialist Joe Wai Tye:
Yea, it was as you guessed: resources.
I added timeout settings to JIRA startup and server started without problems [here I mean I increased max startup timeout duration]. All working 100%. Til now, I have always installed and maintained Atlassian tools on dedicated physical servers with 8G Ram. I never realized that these tools are so heavy that they don't startup on Paravirtual Machine with 4G Ram. Had to start each application (JIRA, Confluence and Stash) in succession for it to work.
Thanks Joe for support, you been of great help.
So, long story short: its about RAM mainly. Either increase it, or increase max timeout for Java app.
When you restart the server, is all the Atlassian Tools also all restarted and startup at the same time? Because, it will take a quite of resource when starting JIRA with its plugin and it have to share with other software.
About the plugin error itself, is there an error where it told you that it is not yet enabled so JIRA is locked, or there is a connection timeout? I would like to suggest you to increase the memory that could be use for your JIRA instance, you may follow this documentation on how to do it:
I might jump to quickly on my suggestion, but hope this could help you.
Best Regards, Julian.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG