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,
I am getting the following issue when tried to start the Bamboo server.
2018-05-14 09:36:14,559 WARN [localhost-startStop-1] [DefaultListableBeanFactory] Bean creation exception on non-lazy FactoryBean type check: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'immutablePlanManager' defined in class path resource [applicationContextManagers.xml]: Cannot create inner bean 'com.atlassian.bamboo.plan.cache.ImmutablePlanManagerImpl#2b3ab7ac' of type [com.atlassian.bamboo.plan.cache.ImmutablePlanManagerImpl] while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.atlassian.bamboo.plan.cache.ImmutablePlanManagerImpl#2b3ab7ac' defined in class path resource [applicationContextManagers.xml]: Cannot resolve reference to bean 'labelManager' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'labelManager' defined in class path resource [applicationContextManagers.xml]: Cannot create inner bean 'com.atlassian.bamboo.labels.LabelManagerImpl#a94eb50' of type [com.atlassian.bamboo.labels.LabelManagerImpl] while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.atlassian.bamboo.labels.LabelManagerImpl#a94eb50' defined in class path resource [applicationContextManagers.xml]: Cannot resolve reference to bean 'buildResultsIndexer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'buildResultsIndexer' defined in class path resource [applicationContextManagers.xml]: Cannot create inner bean 'com.atlassian.bamboo.index.buildresult.DefaultBuildResultsIndexer#14a437ac' of type [com.atlassian.bamboo.index.buildresult.DefaultBuildResultsIndexer] while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.atlassian.bamboo.index.buildresult.DefaultBuildResultsIndexer#14a437ac' defined in class path resource [applicationContextManagers.xml]: Cannot resolve reference to bean 'buildResultLuceneConnection' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'buildResultLuceneConnection' defined in class path resource [applicationContextManagers.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.bamboo.index.LuceneConnectionImpl]: Constructor threw exception; nested exception is com.atlassian.bonnie.LuceneException: org.apache.lucene.store.LockReleaseFailedException: Cannot forcefully unlock a NativeFSLock which is held by another indexer component: /media/atlassian-data/data/bamboo/current/index/results/write.lock
Please let me know what is causing it?
Warm regards,
Javed Gardezi
Hi Javed,
We most often see this error when an incorrect or incompatible version of Java is installed on the system. What version of the JAVA jdk do you have installed?
Hi @Robert W,
Thank you for your reply. Below are the details of the JAVA jdk version installed on Bamboo server.
JDK 1.8
atlassian-bamboo-6.4.0
However, I have resolved the problem. Still time to time I get issue on the Bamboo server when I restart the server.
The way I have resolved the issue is, first in the installation directory search for all the `write.lock`
find . -name "write.lock"
After that I have delete the lock file
> rm -r ./data/bamboo/current/index/search/write.lock
> rm -r ./data/bamboo/current/index/version/write.lock
> rm -r ./data/bamboo/current/index/results/write.lock
Warm regards,
Javed Gardezi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.