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

Tasks are only updated when the site is manually reindexed

Bernd Kruse

Hello everyone,
I'm having an issue with Confluence. We're using version 10.2.7 of the Datacenter edition.
We recently updated from 9.2.9 to 10.2.7. Since the update, tasks are no longer syncing. When a task is created on a page, it no longer appears on the Tasks page in the personal area.
The task only reappears after a site reindex. After that, tasks show up for a few hours (approximately), and then synchronization stops working again until the next site reindex.
I’ve already tried clearing the cache, but that didn’t fix the problem.
Does anyone know if this is a known bug?
I couldn’t find any mention of this issue in the release notes.
Best regards, Bernd

Accepted answers

All comments

Christos Markoulatos -Relational-

Hi @Bernd Kruse

Hi Bernd! I did some digging and found a potentially related bug. Confluence introduced a Task Report Index in version 8.7, a separate index specifically for tasks used to power the personal Tasks view. There's a known issue ([CONFSERVER-99388] Task Report Macro not showing all tasks in Confluence when connected to MySQL database - Create and track feature requests for Atlassian products.) where this index fails to rebuild correctly after the first iteration, which would explain your symptoms: a full site reindex temporarily restores things by rebuilding the Task Report Index from scratch, but it then degrades again as new tasks come in. Quick question though, what database are you running Confluence on? The specific bug report is tied to MySQL, so knowing your DB type will help confirm whether this is the same root cause or something slightly different. Either way, it's worth checking General Configuration → Content Indexing → Queue Contents after a reindex to see if the queue stops being processed after a few hours, and looking in atlassian-confluence-index.log for any LuceneIndexFlusher ABORTED warnings, that would help narrow it down further!

Arkadiusz Wroblewski

Hello @Bernd Kruse

post-upgrade indexing jobs or queue processing Problem probably.

What saying indexing logs ? Can you paste them here ?

Bernd Kruse

Hello @Arkadiusz Wroblewski @Christos Markoulatos -Relational-

I have a few indexing logs for you here:

2026-04-07 03:00:00,098 WARN [Caesium-1-4] [index.lucene.snapshot.DefaultLuceneIndexSnapshotManager] findForJournal Error iterating snapshot directory: C:\\Program Files\\Atlassian\\Application Data\\Confluence\\shared-home\\index-snapshots
2026-04-07 07:53:04,795 WARN [Caesium-1-4] [confluence.impl.journal.DefaultJournalManager] handleFailedEntry Entry in journal [task_report_index] with ID [6836011] has reached the maximum try times (3), skipping it

2026-04-16 03:00:00,027 WARN [Caesium-1-2] [index.lucene.snapshot.DefaultLuceneIndexSnapshotManager] findForJournal Error iterating snapshot directory: C:\\Program Files\\Atlassian\\Application Data\\Confluence\\shared-home\\index-snapshots
2026-04-16 03:00:00,028 WARN [Caesium-1-2] [index.lucene.snapshot.DefaultLuceneIndexSnapshotManager] findForJournal Error iterating snapshot directory: C:\\Program Files\\Atlassian\\Application Data\\Confluence\\shared-home\\index-snapshots

2026-04-16 11:34:52,884 WARN [Caesium-1-3] [confluence.impl.journal.DefaultJournalManager] handleFailedEntry Entry in journal [task_report_index] with ID [7590301] has reached the maximum try times (3), skipping it
2026-04-16 11:43:13,047 WARN [Caesium-1-4] [confluence.impl.journal.DefaultJournalManager] handleFailedEntry Entry in journal [task_report_index] with ID [7590440] has reached the maximum try times (3), skipping it
2026-04-16 11:45:53,072 WARN [Caesium-1-1] [confluence.impl.journal.DefaultJournalManager] handleFailedEntry Entry in journal [task_report_index] with ID [7590456] has reached the maximum try times (3), skipping it
2026-04-16 11:47:13,092 WARN [Caesium-1-2] [confluence.impl.journal.DefaultJournalManager] handleFailedEntry Entry in journal [task_report_index] with ID [7590482] has reached the maximum try times (3), skipping it
2026-04-16 11:48:53,181 WARN [Caesium-1-3] [confluence.impl.journal.DefaultJournalManager] handleFailedEntry Entry in journal [task_report_index] with ID [7590494] has reached the maximum try times (3), skipping it
2026-04-16 11:49:28,293 WARN [Caesium-1-1] [confluence.impl.journal.DefaultJournalManager] handleFailedEntry Entry in journal [task_report_index] with ID [7590503] has reached the maximum try times (3), skipping it
2026-04-16 11:53:18,286 WARN [Caesium-1-4] [confluence.impl.journal.DefaultJournalManager] handleFailedEntry Entry in journal [task_report_index] with ID [7590515] has reached the maximum try times (3), skipping it
2026-04-16 11:53:43,292 WARN [Caesium-1-4] [confluence.impl.journal.DefaultJournalManager] handleFailedEntry Entry in journal [task_report_index] with ID [7590526] has reached the maximum try times (3), skipping it
2026-04-16 12:00:23,510 WARN [Caesium-1-3] [confluence.impl.journal.DefaultJournalManager] handleFailedEntry Entry in journal [task_report_index] with ID [7590565] has reached the maximum try times (3), skipping it
2026-04-16 12:01:33,534 WARN [Caesium-1-3] [confluence.impl.journal.DefaultJournalManager] handleFailedEntry Entry in journal [task_report_index] with ID [7590608] has reached the maximum try times (3), skipping it
2026-04-16 12:02:03,543 WARN [Caesium-1-1] [confluence.impl.journal.DefaultJournalManager] handleFailedEntry Entry in journal [task_report_index] with ID [7590622] has reached the maximum try times (3), skipping it

The warning message keeps repeating.

We use Microsoft SQL Server as our SQL server.

I hope this helps.
Best regards, Bernd

Christos Markoulatos -Relational-

Hi @Bernd Kruse

With a quick look

The task_report_index journal is repeatedly failing to process new task entries, hitting the 3-retry limit and skipping them entirely. That's exactly why tasks disappear over time every new task that gets skipped is simply never indexed. The separate findForJournal error on the snapshot directory is also worth noting, as it suggests Confluence is having trouble reading the index snapshot directory on that node, which may be contributing to the journal failures.

The key question now is why those journal entries are failing. The logs tell us they're being skipped, but not the underlying cause. To get to the root of it, could you check the atlassian-confluence-index.log (or atlassian-confluence.log) around the same timestamps specifically around 03:00 on April 7th and April 16th for any ERROR lines that appear just before or alongside those handleFailedEntry warnings? There's likely a stack trace or exception hiding nearby that will tell us exactly what's going wrong when Confluence tries to process those task journal entries.

In the meantime, the snapshot directory error (C:\Program Files\Atlassian\Application Data\Confluence\shared-home\index-snapshots) is worth checking too confirm that the Confluence service account has full read/write permissions to that path, as a permission or file lock issue there could cascade into the journal processing failures you're seeing.

Arkadiusz Wroblewski

@Bernd Kruse

It will be more helpful when you answer under a posts from us directly.

I know dumb question but did you done snapshot prior to update and can Fall back and try Update again ?

Bernd Kruse

Ich habe vor dem Update einen Snapshot gemacht. Allerdings ist dieser Fehler erst später aufgetaucht und daher ist der Snapshot schon wieder gelöscht worden. Wir können daher das Update nicht noch einmal durchführen.

Arkadiusz Wroblewski

@Bernd Kruse

Die entscheidende Meldung ist für mich nicht die Snapshot-Warnung, sondern das hier:

task_report_index ... has reached the maximum try times (3), skipping it

Das heißt, Confluence versucht die Task-Index-Updates im Hintergrund zu verarbeiten, scheitert dabei drei Mal und überspringt den Eintrag dann. Genau das passt auch zu deinem Verhalten: ein manueller Reindex baut den Index neu auf, danach funktioniert es kurz, und später fehlen neue Änderungen wieder.

Da ihr SQL Server nutzt, ist das auch nicht der MySQL-Bug, der vorher genannt wurde.

Der nächste Schritt ist deshalb, die eigentliche Exception vor dieser WARN-Meldung zu finden. Die von dir gepostete Zeile ist nur das Endergebnis nach drei Fehlversuchen, nicht die eigentliche Ursache.

Ich würde das Logging für com.atlassian.confluence.plugins.tasklist.report.searchindex auf TRACE stellen und dann noch einmal prüfen, welcher ERROR oder Stacktrace direkt davor auftaucht.

So wie es aussieht, ist das also kein allgemeines Reindex-Problem, sondern ein Fehler in der laufenden Verarbeitung des Task-Indexes.

Bernd Kruse

I reviewed the logs in the atlassian-confluence-index.log. There are no errors on the 7th, aside from the messages I’ve already sent you. I also can’t find any additional entries on the 16th. The other entries worth noting are the reindexes I performed. These completed 100%.

In the atlassian-confluence.log, I can find the following logs around 3 a.m.:

2026-04-16 02:59:16,199 INFO [Caesium-1-3] [agent.service.analytics.AnalyticsEventConsumer] info Configured migration analytics batch size: 200

2026-04-16 02:59:45,748 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:00:15,751 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:00:45,755 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:01:15,931 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:01:16,198 INFO [Caesium-1-4] [agent.service.analytics.AnalyticsEventConsumer] info Starting AnalyticsEventConsumer jobId=migration-plugin:analytics-events-consumer-job-id, isCancellationRequested=false

2026-04-16 03:01:16,199 INFO [Caesium-1-4] [agent.service.analytics.AnalyticsEventConsumer] info Configured migration analytics batch size: 200

2026-04-16 03:01:45,935 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:02:15,939 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:02:45,999 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:03:16,086 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:03:17,236 INFO [Caesium-1-4] [agent.service.analytics.AnalyticsEventConsumer] info Starting AnalyticsEventConsumer jobId=migration-plugin:analytics-events-consumer-job-id, isCancellationRequested=false

2026-04-16 03:03:17,237 INFO [Caesium-1-4] [agent.service.analytics.AnalyticsEventConsumer] info Configured migration analytics batch size: 200

2026-04-16 03:03:37,407 INFO [pool-34-thread-1] [agent.service.featureflag.Fx3OkhttpAdapter] post Fx3Client couldn't fetch feature flags from LD. Message : Connection reset

2026-04-16 03:03:46,091 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:03:56,316 INFO [pool-34-thread-1] [agent.service.featureflag.Fx3OkhttpAdapter] post Fx3Client couldn't fetch feature flags from LD. Message : Connection reset

2026-04-16 03:04:16,094 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:04:46,098 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:05:00,007 ERROR [analyticsEventProcessor:thread-1] [analytics.client.pipeline.DefaultAnalyticsPipeline] lambda$createTask$0 Failed to send analytics event com.atlassian.analytics.api.events.MauEvent@e05b1c09

io.atlassian.util.concurrent.LazyReference$InitializationException: software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: Connect to btf-analytics.s3.dualstack.us-east-1.amazonaws.com:443 [btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.191.109, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.252.76, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.199.246, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.228.197, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/52.216.63.18, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.207.208, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.182.71.42, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/54.231.197.242] failed: Read timed out

at io.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:156)

at io.atlassian.util.concurrent.LazyReference.get(LazyReference.java:116)

at io.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:95)

at com.atlassian.analytics.client.hash.BcryptAnalyticsEmailHasher.hashInternal(BcryptAnalyticsEmailHasher.java:61)

at com.atlassian.analytics.client.hash.BcryptAnalyticsEmailHasher.hash(BcryptAnalyticsEmailHasher.java:52)

at java.base/java.util.Optional.map(Unknown Source)

at com.atlassian.analytics.client.pipeline.serialize.properties.extractors.mau.MauService.lambda$new$0(MauService.java:31)

at com.github.benmanes.caffeine.cache.LocalCache.lambda$statsAware$0(LocalCache.java:167)

at com.github.benmanes.caffeine.cache.BoundedLocalCache.lambda$doComputeIfAbsent$0(BoundedLocalCache.java:2707)

at java.base/java.util.concurrent.ConcurrentHashMap.compute(Unknown Source)

at com.github.benmanes.caffeine.cache.BoundedLocalCache.doComputeIfAbsent(BoundedLocalCache.java:2705)

at com.github.benmanes.caffeine.cache.BoundedLocalCache.computeIfAbsent(BoundedLocalCache.java:2686)

at com.github.benmanes.caffeine.cache.LocalCache.computeIfAbsent(LocalCache.java:112)

at com.github.benmanes.caffeine.cache.LocalManualCache.get(LocalManualCache.java:63)

at com.atlassian.confluence.impl.cache.caffeine.CaffeineCacheLoadingImpl.get(CaffeineCacheLoadingImpl.java:31)

at com.atlassian.cache.impl.metrics.InstrumentedCache.get(InstrumentedCache.java:65)

at com.atlassian.analytics.client.pipeline.serialize.properties.extractors.mau.MauService.hashEmailPropertyForMauEvent(MauService.java:48)

at com.atlassian.analytics.client.pipeline.serialize.properties.extractors.mau.MauAwarePropertyExtractor.getEventPropertiesWithHashedEmail(MauAwarePropertyExtractor.java:20)

at com.atlassian.analytics.client.pipeline.serialize.properties.MauAwareExtractorSupplier.oldDelayed(MauAwareExtractorSupplier.java:58)

at com.atlassian.analytics.client.pipeline.serialize.properties.ExtractionSupplier.lambda$createTimedSupplier$0(ExtractionSupplier.java:21)

at com.atlassian.analytics.client.pipeline.DefaultAnalyticsPipeline.lambda$createTask$0(DefaultAnalyticsPipeline.java:95)

at com.atlassian.sal.core.executor.ThreadLocalDelegateRunnable.run(ThreadLocalDelegateRunnable.java:34)

at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.base/java.util.concurrent.FutureTask.run(Unknown Source)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.base/java.lang.Thread.run(Unknown Source)

Caused by: software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: Connect to btf-analytics.s3.dualstack.us-east-1.amazonaws.com:443 [btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.191.109, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.252.76, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.199.246, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.228.197, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/52.216.63.18, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.207.208, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.182.71.42, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/54.231.197.242] failed: Read timed out

at software.amazon.awssdk.core.exception.SdkClientException$BuilderImpl.build(SdkClientException.java:111)

at software.amazon.awssdk.core.exception.SdkClientException.create(SdkClientException.java:47)

at software.amazon.awssdk.core.internal.http.pipeline.stages.utils.RetryableStageHelper2.setLastException(RetryableStageHelper2.java:226)

at software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage2.execute(RetryableStage2.java:65)

at software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage2.execute(RetryableStage2.java:36)

at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)

at software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:53)

at software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:35)

at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.executeWithTimer(ApiCallTimeoutTrackingStage.java:82)

at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:62)

at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:43)

at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallMetricCollectionStage.execute(ApiCallMetricCollectionStage.java:50)

at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallMetricCollectionStage.execute(ApiCallMetricCollectionStage.java:32)

at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)

at software.amazon.awssdk.core.internal.http.pipeline.stages.ExecutionFailureExceptionReportingStage.execute(ExecutionFailureExceptionReportingStage.java:37)

at software.amazon.awssdk.core.internal.http.pipeline.stages.ExecutionFailureExceptionReportingStage.execute(ExecutionFailureExceptionReportingStage.java:26)

at software.amazon.awssdk.core.internal.http.AmazonSyncHttpClient$RequestExecutionBuilderImpl.execute(AmazonSyncHttpClient.java:210)

at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.invoke(BaseSyncClientHandler.java:103)

at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.doExecute(BaseSyncClientHandler.java:173)

at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.lambda$execute$0(BaseSyncClientHandler.java:66)

at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.measureApiCallSuccess(BaseSyncClientHandler.java:182)

at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.execute(BaseSyncClientHandler.java:60)

at software.amazon.awssdk.core.client.handler.SdkSyncClientHandler.execute(SdkSyncClientHandler.java:52)

at software.amazon.awssdk.awscore.client.handler.AwsSyncClientHandler.execute(AwsSyncClientHandler.java:60)

at software.amazon.awssdk.services.s3.DefaultS3Client.getObject(DefaultS3Client.java:5245)

at com.atlassian.analytics.client.s3.AnalyticsS3Client.getS3ObjectInputStream(AnalyticsS3Client.java:122)

at com.atlassian.analytics.client.hash.reader.RemoteHashingInstructionsReader.getRemoteListObject(RemoteHashingInstructionsReader.java:53)

at com.atlassian.analytics.client.hash.reader.RemoteHashingInstructionsReader.readInstructions(RemoteHashingInstructionsReader.java:34)

at com.atlassian.analytics.client.hash.BcryptAnalyticsEmailHasher$HashingInstructionsResettableLazyReference.create(BcryptAnalyticsEmailHasher.java:185)

at com.atlassian.analytics.client.hash.BcryptAnalyticsEmailHasher$HashingInstructionsResettableLazyReference.create(BcryptAnalyticsEmailHasher.java:166)

at io.atlassian.util.concurrent.ResettableLazyReference$InternalReference.create(ResettableLazyReference.java:185)

at io.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:332)

at io.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:150)

at io.atlassian.util.concurrent.LazyReference.get(LazyReference.java:116)

at io.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:95)

at com.atlassian.analytics.client.hash.BcryptAnalyticsEmailHasher.readRemoteInstructions(BcryptAnalyticsEmailHasher.java:145)

at com.atlassian.analytics.client.upload.RemoteFilterReadRunner.runJob(RemoteFilterReadRunner.java:50)

at com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.doRunJob(JobRunnerWrapper.java:121)

at com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.runJob(JobRunnerWrapper.java:83)

at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$JobRunnerWithStats.runJob(CaesiumSchedulerService.java:787)

at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:145)

at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:117)

at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:99)

at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:578)

at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJobWithRetryOnFailure(CaesiumSchedulerService.java:533)

at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:461)

at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:66)

at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:60)

at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:35)

... 1 more

Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to btf-analytics.s3.dualstack.us-east-1.amazonaws.com:443 [btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.191.109, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.252.76, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.199.246, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.228.197, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/52.216.63.18, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.15.207.208, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/16.182.71.42, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/54.231.197.242] failed: Read timed out

at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)

at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376)

at software.amazon.awssdk.http.apache.internal.conn.ClientConnectionManagerFactory$DelegatingHttpClientConnectionManager.connect(ClientConnectionManagerFactory.java:86)

at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)

at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)

at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)

at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)

at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)

at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)

at software.amazon.awssdk.http.apache.internal.impl.ApacheSdkHttpClient.execute(ApacheSdkHttpClient.java:72)

at software.amazon.awssdk.http.apache.ApacheHttpClient.execute(ApacheHttpClient.java:254)

at software.amazon.awssdk.http.apache.ApacheHttpClient.access$500(ApacheHttpClient.java:104)

at software.amazon.awssdk.http.apache.ApacheHttpClient$1.call(ApacheHttpClient.java:231)

at software.amazon.awssdk.http.apache.ApacheHttpClient$1.call(ApacheHttpClient.java:228)

at software.amazon.awssdk.core.internal.util.MetricUtils.measureDurationUnsafe(MetricUtils.java:99)

at software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.executeHttpRequest(MakeHttpRequestStage.java:79)

at software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.execute(MakeHttpRequestStage.java:57)

at software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.execute(MakeHttpRequestStage.java:40)

at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)

at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:74)

at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:43)

at software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:79)

at software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:41)

at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:55)

at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:39)

at software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage2.executeRequest(RetryableStage2.java:93)

at software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage2.execute(RetryableStage2.java:56)

... 47 more

Caused by: java.net.SocketTimeoutException: Read timed out

at java.base/sun.nio.ch.NioSocketImpl.timedRead(Unknown Source)

at java.base/sun.nio.ch.NioSocketImpl.implRead(Unknown Source)

at java.base/sun.nio.ch.NioSocketImpl.read(Unknown Source)

at java.base/sun.nio.ch.NioSocketImpl$1.read(Unknown Source)

at java.base/java.net.Socket$SocketInputStream.read(Unknown Source)

at java.base/sun.security.ssl.SSLSocketInputRecord.read(Unknown Source)

at java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source)

at java.base/sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source)

at java.base/sun.security.ssl.SSLTransport.decode(Unknown Source)

at java.base/sun.security.ssl.SSLSocketImpl.decode(Unknown Source)

at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)

at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)

at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:436)

at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:384)

at software.amazon.awssdk.http.apache.internal.conn.SdkTlsSocketFactory.connectSocket(SdkTlsSocketFactory.java:63)

at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)

... 76 more

2026-04-16 03:05:16,183 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:05:17,348 INFO [Caesium-1-2] [agent.service.analytics.AnalyticsEventConsumer] info Starting AnalyticsEventConsumer jobId=migration-plugin:analytics-events-consumer-job-id, isCancellationRequested=false

2026-04-16 03:05:17,349 INFO [Caesium-1-2] [agent.service.analytics.AnalyticsEventConsumer] info Configured migration analytics batch size: 200

2026-04-16 03:05:46,186 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:06:16,191 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:06:46,194 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:07:16,198 WARN [synchrony-interop-scheduled-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [Replaced Names]

2026-04-16 03:07:17,243 INFO [Caesium-1-3] [agent.service.analytics.AnalyticsEventConsumer] info Starting AnalyticsEventConsumer jobId=migration-plugin:analytics-events-consumer-job-id, isCancellationRequested=false

2026-04-16 03:07:17,248 INFO [Caesium-1-3] [agent.service.analytics.AnalyticsEventConsumer] info Configured migration analytics batch size: 200

Welcome!

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

Quick Links

Find more posts tagged with

confluence

task

data-center

index

confluence-data-center