Bamboo had a job that was stuck in the "Queued" state, but did not show up in the list of Builds. So we restarted Bamboo. Upon restart, the catalina log file was stuck on a line that said "Initializing C3P0 pool". After a while, an exception was thrown that said "The database is in use by another process". There were no processes running on the machine owned by me, other than my login and tomcat. Could the default database be corrupted or locked?
I found an article that said to delete the KahaDB and caches directories from the bamboo home directory to solve this problem
I tried renaming them to caches_old and KahaDB_old and restarting the tomcat server
The same thing happened again with the hang on Initializing C3P0 and subsequent crash
It is. I thought that might be a problem as well, but I checked and do not see other instances of bamboo running off of that directory on other machines. The only person that starts and stops bamboo is me, and I definitely did not start it up on another machine. It was working and I simply restarted it.
NFS v3, probably? Lock support is handled by an external process (not NFS core) and it still thinks that the files are locked. I can't recommend that setup. At the very least, upgrade to NFS v4.
I'd also recommend symlinking the database dir and the JMS dir to local dirs if you absolutely must run on NFS.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot