After Java Update Bitbucket ran fine on 1st startup, but on 2. startup appears like new installation

[robinhp82]

After updating from an older Java version 1.8.0_xx to the latest x64 bit version of 1.8.0_281, Bitbucket startet firstly completely normal and fully functional. Everything seemed normal.

A new instance of the latest Bamboo 7.2.2 (running on another PC) was then re-connected to the Bitbucket instance (it was already connected a few days ago with the old Java version, but then disconnected before the Java update again).

However, during the usual automatic shutdown and backup procedure over night, the next restart did not go through successfully anymore. The startup screen is stuck for 1-2 minutes at "Starting plugin framework", and apparently a Timeout happens.
Afterwards the "Bitbucket Setup Screen" is shown, as if we had a fresh and empty installation of Bitbucket, asking if we want to use an "internal" or "external" database....

Researching for a few hours revealed a few "solution candidates" for the problem, which were all followed up and attempted, but nothing helped:

• delete Bitbucket cache : <Bitbucket_AppData>\plugins\.osgi-cache\felix
• increase the previously fine and working Java memory from 1 GB to 2 GB (the server still has another 10 GB of free memory and plenty of processing power)
  --> see Entry #3 of https://confluence.atlassian.com/bitbucketserverkb/bitbucket-server-failed-to-start-due-to-required-plugin-failed-to-start-779171543.html
• temporarily switching off Antivirus scanner, which suddenly "could block something"
• going back to the original/old/previous Java version also does not help anymore

These errors are thrown within the first 2 minutes of the startup:

2021-03-12 21:32:28,384 WARN [FelixStartLevel] o.e.g.b.e.i.s.ExtenderConfiguration Gemini Blueprint extensions bundle not present, annotation processing disabled.
2021-03-12 21:33:33,829 WARN [Spring DM Context Creation Timer] o.e.g.b.e.i.d.s.DependencyWaiterApplicationContextExecutor Timeout occurred before finding service dependencies for [NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.applinks.diagnostics-plugin, config=osgibundle:/META-INF/spring/*.xml)]
2021-03-12 21:33:33,834 ERROR [Spring DM Context Creation Timer] c.a.plugin.osgi.factory.OsgiPlugin Plugin 'com.atlassian.applinks.applinks-diagnostics-plugin' never resolved service '&typeAccessor' with filter '(&(objectClass=com.atlassian.applinks.spi.util.TypeAccessor)(objectClass=com.atlassian.applinks.core.InternalTypeAccessor))'
2021-03-12 21:33:33,834 ERROR [Spring DM Context Creation Timer] c.a.plugin.osgi.factory.OsgiPlugin Plugin 'com.atlassian.applinks.applinks-diagnostics-plugin' never resolved service '&applicationLinkService' with filter '(objectClass=com.atlassian.applinks.spi.link.MutatingApplicationLinkService)'
2021-03-12 21:33:33,844 ERROR [Spring DM Context Creation Timer] c.a.plugin.osgi.factory.OsgiPlugin Unable to start the plugin container for plugin 'com.atlassian.applinks.applinks-diagnostics-plugin'
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.applinks.diagnostics-plugin' has timed out waiting for (|(objectClass=com.atlassian.applinks.spi.link.MutatingApplicationLinkService)(&(objectClass=com.atlassian.applinks.spi.util.TypeAccessor)(objectClass=com.atlassian.applinks.core.InternalTypeAccessor)))
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2021-03-12 21:33:33,866 ERROR [Spring DM Context Creation Timer] o.e.g.b.e.i.s.ExtenderConfiguration Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.applinks.diagnostics-plugin, config=osgibundle:/META-INF/spring/*.xml))
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.applinks.diagnostics-plugin' has timed out waiting for (|(objectClass=com.atlassian.applinks.spi.link.MutatingApplicationLinkService)(&(objectClass=com.atlassian.applinks.spi.util.TypeAccessor)(objectClass=com.atlassian.applinks.core.InternalTypeAccessor)))
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2021-03-12 21:33:33,868 ERROR [Spring DM Context Creation Timer] o.e.g.b.e.i.d.s.DependencyWaiterApplicationContextExecutor Unable to create application context for [com.atlassian.applinks.diagnostics-plugin], unsatisfied dependencies: Dependency on [(objectClass=com.atlassian.applinks.spi.link.MutatingApplicationLinkService)] (from bean [&applicationLinkService]), Dependency on [(&(objectClass=com.atlassian.applinks.spi.util.TypeAccessor)(objectClass=com.atlassian.applinks.core.InternalTypeAccessor))] (from bean [&typeAccessor])
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.applinks.diagnostics-plugin' has timed out waiting for (|(objectClass=com.atlassian.applinks.spi.link.MutatingApplicationLinkService)(&(objectClass=com.atlassian.applinks.spi.util.TypeAccessor)(objectClass=com.atlassian.applinks.core.InternalTypeAccessor)))
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)

This is particularly frustrating, since after the new Java update we DID ALREADY do a restart of Bitbucket, and all was working. There was no significant interaction afterwards anymore, only reconnecting the new Bamboo. And now Bitbucket wont work with the Homedir anymore, no matter what we do....