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.
I'm tring to upgrade Confluence Server 6.15.9 to 7.4.3, but Confluence stills down after the migration.
What i've tried:
- Upgrade Confluence 6.15.9 to 7.4.3: KO
- Upgrade Confluence 6.15.9 to 7.0.5: It works perfectly
- Upgrade Confluence 7.0.5 to 7.4.3: KO
- Upgrade Confluence 6.15.9 to 7.4.3 with Docker: KO
I have that error on the landing page:
Database: Database connection failed
The database (MSSQL) is up and the configuration is correct.
This error appears in my catalina.out:
20-Aug-2020 09:27:36.244 WARNING [Catalina-utility-3] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8090-exec-1] (id=) has been active for [66,708] milliseconds (since [8/20/20 9:26 AM]) to serve the same request for [http://confluence.mydomain:8080/confluence/] and may be stuck (configured threshold for this StuckThreadDetectionValve is  seconds). There is/are  thread(s) in total that are monitored by this Valve and may be stuck.
at email@example.com/java.lang.Object.wait(Native Method)
at jdk.internal.reflect.GeneratedMethodAccessor78.invoke(Unknown Source)
20-Aug-2020 09:28:16.252 WARNING [Catalina-utility-1] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread [http-nio-8090-exec-1] (id=) was previously reported to be stuck but has completed. It was active for approximately [98,144] milliseconds.
OS: RHEL 7.8
JAVA: OpenJDK 1.8.0_262-b10
Confluence Server: 6.15.9
Do you have any suggestions?
Thanks in advance.
I recommend you open a ticket with atlassian support if you are still experiencing this issue: https://support.atlassian.com/contact/#/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.