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
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.
After spending weeks looking at options for a ticketing solution, YouTube videos on different products for my small 400 employee company, I messaged support with my silly questions in excitement and I was so excited to get Jira Service Desk installed and and use it. There is no ticketing system in place at this time.
Unfortunately my excitement turned into frustration after spending a whole day today trying to just get it installed on my server from scratch. The only thing I did differently was try to make it connect to my MySQL db hosted on a different server and I just could not get past the dreaded "Could not find driver with class name: com.mysql.jdbc.Driver" message while configuring database at first launch. First someone said that this might be due to re-distributables and then it might be due to java not pointing correctly and then maybe the MySQL connected (mentioned in the manual) needs to be downloaded and copied to the bin folder, and list goes on.
Why, I ask why is there even an install process when it doesn't go through some sort of check process before even installing itself into a folder? Whatever happened to pre-install requisites check? So here I am looking at config check java and all sorts of batch files now.. I am going to step away for a few hours and give it one last try tonight before going to sleep.
Call me dumb, point fingers or laugh; I am just burned out now. It was great and wish I could have really tried it but if this is the experience now then I am worried what will happen in future. Somethings are just meant to be.
I ended up installing MySQL locally on a different drive to alleviate some issues and am running into the next error now - MySQL is now configured properly.
Great that you were able to make the driver works.
Now about your MySQL, can you confirm if you are editing under the [mysqld] tag?
I've in the past an error when I tried to modify under [mysql] instead of [mysqld], and that was failing to restart my service.
If you are hosting JIRA with AWS I would recommend evaluate the usage of a RDS, this will make your database administrative task (such as backup and restore) much easier.
Let us posted with your progress!
I am in! Database is now being set up by the app.
"Please wait while the database is set up. This may take a minute..."
Basically you will be doing the trade in an inactive workflow after which setting it to energetic. That's what lets in you to do the changes you want