after updating our Confluence instance from version 6.15.1 to version 7.0.3 on Wednesday, it has been unreachable 2 times.
We never had this case before the upgrade.
The Confluence instance is used on a Windows Server 2016 and a MySQL database 5.7
What information do you need to find the error.
nachdem ich am Mittwoch unsere Confluence Instanz von Version 6.15.1 auf Version 7.0.3 aktuallisiert habe, ist dieser schon 2 mal nicht erreichbar gewesen.
Diesen Fall hatten wir vor dem Upgrade noch nie.
Verwendet wird die Confluence Instanz auf einem Windows Server 2016 und einer MySQL Datenbank 5.7
Welche Informationen benötigen Sie um den Fehler finden zu können.
Thank you for raising this with us.
You mention you haven't been able to access your Confluence site twice since upgrading. I have a few follow-up questions for you.
Thank you for your help!
yesterday we had the third crash since the upgrade.
Access to the Confluence is generally possible.
We get the crash, the website does not answer anymore.
How do we perform the upgrades?
First of all, all plugins are patched.
Then we check via "Update Check" if all plug-ins are compatible.
Now we download the setup file: https://www.atlassian.com/software/confluence/download
This file is then started and followed by the wizard.
We have to stop the Windows service "Confluence080917081758" manually because the wizard does not finish it.
At the end of the update process we do not confirm the button "start Confluence".
We make adjustments to the following file:
<Installation directory> \ Atlassian \ Confluence \ conf \ server.xml
<Connector port = "8090" connectionTimeout = "20000" redirectPort = "8443"
maxThreads = "48" minSpareThreads = "10"
enableLookups = "false" acceptCount = "10" debug = "0" URIEncoding = "UTF-8"
protocol = "org.apache.coyote.http11.Http11NioProtocol"
proxyName = "<proxyurl>" proxyPort = "443" scheme = "https" />
Next we adapt the following file:
<Installation directory> \ Atlassian \ Confluence \ confluence \ WEB-INF \ web.xml
<Session-timeout> 180 </ session-timeout>
<Tracking mode> COOKIE </ tracking mode>
Now we finish the Wizzard and start if necessary the Windows service "Confluence080917081758" manually.
The Confluence itself worked right after the upgrade.
At some point we get but no answer in the browser and currently only helps restart the server.
But since our Confluence has to be reachable from the outside (that's why the upstream proxy), a crash is very bad.
I have created a support file, how can I send it to you?
Thank you for your reply! I wanted to let you know first that I moved your reply into the main thread, for ease of legibility.
I consulted the team, and it appears we have a known issue right now in 7.0.1, 7.0.2, and 7.0.3 that is causing UPM to hang and then bring down the rest of the instance.
We suspect that this could be what is bringing your instance down. Could you give the workaround a try and let me know if it improves anything?
In Confluence, disable connectivity to Marketplace:
Confluence Administration >> General Configuration >> Manage Apps >> Settings >> Uncheck the 'Connect to the Atlassian Marketplace' box, then click 'Apply'
Let me know how that goes.
It’s been great to hear from fellow users over the last few weeks about the best tips and fun moments you’ve had working on Confluence since the transition to working remote. I’d love to keep the c...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events