nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why do plugin installs take about 30 minutes each in Confluence 4.2.2?

BroadcomS

Installing or upgrading any plugin in Confluence 4.2.2 takes at least 30 minutes. What's the deal? At this rate, we will have to have a 48 hour downtime to do our production upgrade, just to sit around and wait! Is this a known issue? Anyone else experiencing this? We are going from 3.5.13 to 4.2.2.

Accepted answers

BroadcomS

The root cause was the SharePoint Connector Plugin. Thankfully, Joseph Clark solved the problem and released the SharePoint Connector 1.6.1, which resolved the issue for us.

All comments

Nic Brough -Adaptavist-

Nope, ours upload in a few seconds. What does your log file say? Can you try downloading a plugin and loading it manually (via upload a jar, rather than asking the UPM to go to the marketplace)?

BroadcomS

Looks like a lot of garbage collection going on. We have nearly 100,000 pages, which may have something to do with it.

I should probably just open a support ticket. :-)

Ellen Feaheny [

Yep - something tweaky going on in that there Confluence system - dig deeper.. 4.2.2. is faster..

Nic Brough -Adaptavist-

Hmm, loads of GC is probably the cause of the slowness, but you should be seeing slow responses all over the place, and I can't pin down 100k pages as a direct cause.

I take it a manual upload of a plugin also runs really slowly?

I would indeed be thinking about a support call, but after looking at the memory/JVM settings to make sure they are sensible (and my usual trick is to use the wrong letter in a memory setting, so if you're anything like me, check your spelling/typing)

RianA

Hi, have you check Server Base URL? Does it match with the address that you use to access Confluence? Is your Confluence exposed to internet? If it doesn't, please refer to this documentation and this one. Cheers!

BroadcomS

The root cause was the SharePoint Connector Plugin. Thankfully, Joseph Clark solved the problem and released the SharePoint Connector 1.6.1, which resolved the issue for us.