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; } } }

Creating a new Page

Sebastian Bischoff

Hello Confluence Team,

if i want to creat a new page in confluence i get a massage that the page needs longer for the load as expected.
And then the page is loading and loading and loading.. Nothing happens.
Maybe you know this issue and can help me?

Best regards,

S. Bischoff

Accepted answers

All comments

Nic Brough -Adaptavist-

This usually means Synchrony is failing for some reason.

Try going to Admin -> Collaborative Editing and disabling Synchrony.

If my guess is right, then you'll find you can use the old-style editor to edit pages fine. We'll then have to go debug what is wrong with Synchrony.

If I'm wrong, then we'll need to start looking at logs to see what the problem is.

Sebastian Bischoff

Hello,

thank you for your response.

Yeah it works, if i disable Synchrony.
But i think i need it, or?
If i eneble it again, then its loading againg and nothing happens.

The "atlassian-confluence"Log says this:
2017-08-14 13:22:20,539 INFO [Caesium-1-3] [directory.ldap.cache.RemoteDirectoryCacheRefresher] findAllRemoteUsers found [ 3 ] remote users in [ 341 ms ]
2017-08-14 13:22:20,571 INFO [Caesium-1-3] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] deleteCachedUsersNotIn scanned and compared [ 3 ] users for delete in DB cache in [ 29ms ]
2017-08-14 13:22:20,571 INFO [Caesium-1-3] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] deleteCachedUsersNotIn scanned for deleted users in [ 30ms ]
2017-08-14 13:22:20,595 INFO [Caesium-1-3] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] getUsersToAddAndUpdate scanning [ 3 ] users to add or update
2017-08-14 13:22:20,610 INFO [Caesium-1-3] [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] addOrUpdateCachedUsers scanned and compared [ 3 ] users for update in DB cache in [ 38ms ]
2017-08-14 13:22:20,620 INFO [Caesium-1-3] [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] addOrUpdateCachedUsers synchronised [ 3 ] users in [ 48ms ]
2017-08-14 13:22:20,673 INFO [Caesium-1-3] [directory.ldap.cache.RemoteDirectoryCacheRefresher] findAllRemoteGroups found [ 2 ] remote groups in [ 53 ms ]
2017-08-14 13:22:20,684 INFO [Caesium-1-3] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] deleteCachedGroupsNotIn scanned and compared [ 2 ] groups for delete in DB cache in [ 10ms ]
2017-08-14 13:22:20,687 INFO [Caesium-1-3] [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] addOrUpdateCachedGroups scanning [ 2 ] groups to add or update
2017-08-14 13:22:20,718 INFO [Caesium-1-3] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] findGroupsToUpdate scanned and compared [ 2 ] groups for update in DB cache in [ 29ms ]
2017-08-14 13:22:20,726 INFO [Caesium-1-3] [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] addOrUpdateCachedGroups synchronized [ 2 ] groups in [ 39ms ]
2017-08-14 13:22:20,757 INFO [Caesium-1-3] [directory.ldap.cache.AbstractCacheRefresher] synchroniseAllGroupAttributes finished group attribute sync with 0 failures in [ 31ms ]
2017-08-14 13:22:20,881 INFO [Caesium-1-3] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache FULL synchronisation complete for directory [ 262145 ] in [ 688ms ]

Nic Brough -Adaptavist-

That log is all about LDAP, not a problem here.

The usual thing with Synchrony is a proxy that's not set up to let it work. We'll almost certainly want to take a look at the config of that if you have one.

Whether you have a proxy or not though, you should find there's a synchrony log in the same place you found the main confluence log.

Sebastian Bischoff

Hello Nic,

the atlassian-synchrony log (C:\Program Files\Atlassian\Application Data\Confluence\logs) has entrys with a date of 2015:

""synchrony":{"message":"synchrony.querydsl.jdbc [info] connection pool test-connection-on-checkin: true idle-connection-test-period: 100 max-idle-time-excess-connections: 100 max-idle-time: 3600","ns":"synchrony.querydsl.jdbc"}}
MLog initialization issue: slf4j found no binding or threatened to use its (dangerously silent) NOPLogger. We consider the slf4j library not found.
MLog clients using log4j logging.
Initializing c3p0-0.9.5.1 [built 16-June-2015 00:06:36 -0700; debug? true; trace: 10]
Running QueryDSL sytem...
{"synchrony":{"message":"synchrony.querydsl.jdbc [info] connection pool test-connection-on-checkin: true idle-connection-test-period: 100 max-idle-time-excess-connections: 100 max-idle-time: 3600","ns":"synchrony.querydsl.jdbc"}}
MLog initialization issue: slf4j found no binding or threatened to use its (dangerously silent) NOPLogger. We consider the slf4j library not found.
MLog clients using log4j logging.
Initializing c3p0-0.9.5.1 [built 16-June-2015 00:06:36 -0700; debug? true; trace: 10]
Running QueryDSL sytem...
{"synchrony":{"message":"synchrony.querydsl.jdbc [info] connection pool test-connection-on-checkin: true idle-connection-test-period: 100 max-idle-time-excess-connections: 100 max-idle-time: 3600","ns":"synchrony.querydsl.jdbc"}}
MLog initialization issue: slf4j found no binding or threatened to use its (dangerously silent) NOPLogger. We consider the slf4j library not found.
MLog clients using log4j logging.
Initializing c3p0-0.9.5.1 [built 16-June-2015 00:06:36 -0700; debug? true; trace: 10]
Running QueryDSL sytem...
{"synchrony":{"message":"synchrony.querydsl.jdbc [info] connection pool test-connection-on-checkin: true idle-connection-test-period: 100 max-idle-time-excess-connections: 100 max-idle-time: 3600","ns":"synchrony.querydsl.jdbc"}}
MLog initialization issue: slf4j found no binding or threatened to use its (dangerously silent) NOPLogger. We consider the slf4j library not found.
MLog clients using log4j logging.
Initializing c3p0-0.9.5.1 [built 16-June-2015 00:06:36 -0700; debug? true; trace: 10]
Running QueryDSL sytem...
{"synchrony":{"message":"synchrony.querydsl.jdbc [info] connection pool test-connection-on-checkin: true idle-connection-test-period: 100 max-idle-time-excess-connections: 100 max-idle-time: 3600","ns":"synchrony.querydsl.jdbc"}}
MLog initialization issue: slf4j found no binding or threatened to use its (dangerously silent) NOPLogger. We consider the slf4j library not found.
MLog clients using log4j logging.
Initializing c3p0-0.9.5.1 [built 16-June-2015 00:06:36 -0700; debug? true; trace: 10]
Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ acquireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionCustomizerClassName -> null, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, contextClassLoaderSource -> caller, dataSourceName -> 1bqonij9p1q9st7g7vyzbj|6d453e13, debugUnreturnedConnectionStackTraces -> false, description -> null, driverClass -> org.h2.Driver, extensions -> {}, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, forceSynchronousCheckins -> false, forceUseNamedDriverClass -> false, identityToken -> 1bqonij9p1q9st7g7vyzbj|6d453e13, idleConnectionTestPeriod -> 100, initialPoolSize -> 3, jdbcUrl -> jdbc:h2:tcp://localhost:9092/C:\Program Files\Atlassian\Application Data\Confluence\database\h2db;MVCC=TRUE, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 3600, maxIdleTimeExcessConnections -> 100, maxPoolSize -> 15, maxStatements -> 0, maxStatementsPerConnection -> 0, minPoolSize -> 3, numHelperThreads -> 3, preferr"

Does this help you?
Thx for your reply.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence