com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalStateException: Spring Application context has not been set
at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)
caused by: java.lang.IllegalStateException: Spring Application context has not been set
at com.atlassian.spring.container.SpringContainerContext.getComponent(SpringContainerContext.java:48)
com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalStateException: Spring Application context has not been set at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149) at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112) ...
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalStateException: Spring Application context has not been set at com.atlassian.spring.container.SpringContainerContext.getComponent(SpringContainerContext.java:48) at com.atlassian.spring.container.ContainerManager.getComponent(ContainerManager.java:33) at com.atlassian.confluence.util.LazyComponentReference$Accessor.get(LazyComponentReference.java:42) at com.atlassian.util.concurrent.Lazy$Strong.create(Lazy.java:85) at com.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:325) at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:143) ... 207 more
Hi Volker,
Unfortunately there isn't enough information to figure out the exact issue you're running into with Confluence. However, a common issue that users face is Confluence not having write access to the Confluence Home folder.
Have a look at this KB article that explains common problems and resolutions you might face when starting up Confluence - https://confluence.atlassian.com/confkb/confluence-does-not-start-due-to-spring-application-context-has-not-been-set-218278311.html
Hi Daniel, It is ok.
It turned out that my background postgres DB was not properly configured. After cleanup and reinstall with correct postgres DB everything worked fine.
Thanks for your effort!
Volker
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.