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

Team Calendar CalDav Syncronizer

Katharina Wolkwitz

Hi Support,

recently we have installed confluence including the team calendar function. We'd like to syncronize them to Outlook via the CalDav Syncronizer, which causes internal server errors (code 500). Do you have a hint what it could be and how I can resolve it?

We have deactivated the collaborative editing feature as we don't need it. Does it influence the calendar synchronisation?

Is there a way to add the report xml.file to the support-request? The edit-field is limited to 20.000 chars and the report exeeds that by far.

Kate

Accepted answers

All comments

Shannon S

Katharina

Can you show me which CalDav Synchronizer this is? I'm not familiar with it.

If you were to create a test calendar and add a basic event or two, does the issue still occur?

Lastly, what is the report xml file you refer to? Is it generated by the synchronizer? What error messages do you see in the Confluence Server logs when it tries to synchronize?

Regards,

Shannon

Katharina Wolkwitz

Hi Shannon,

sorry for taking so long answering your post. I was off work on Friday.

The CalDav Synchronizer is the tool recommended by your own step-by-step guide "Subscribe to Team Calendars from Microsoft Outlook" ( https://community.atlassian.com/t5/Confluence-questions/Team-Calendar-CalDav-Syncronizer/qaq-p/879535?utm_campaign=&utm_content=post&utm_medium=email&utm_source=atlcomm#M118137 ) which I followed to connect our Team Calendars to our Outlook-Clients btw.

The report-file is indeed from this tool.

Could you give me a hint as to where I'd find the Confluence Server logs? I inherited the server and am not very familiar with its setup.

I'll create a test-calendar and subscribe to it only with my Outlook-Client and create a few test events. And then I'll have a look if that calendar will produce synchronization errors as well.

Kate

Katharina Wolkwitz

One more information:

All our other team-calendars are based on pre-existing calendars exported from a group-ware-server to .ics-files and imported into confluence team-calendars. They had between 5 and 480 events when they were generated/imported (some of them recurring).

Kate

Katharina Wolkwitz

Hi again,

in the /opt/atlassian/confluence/logs/catalina.2018-08-24.log and also in others from different dates I've found numerous errors like this:

24-Aug-2018 14:35:07.995 WARNUNG [ContainerBackgroundProcessor[StandardEngine[Standalone]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread [http-nio-8090-exec-134] (id=[3673]) was previously reported to be stuck but has completed. It was active for approximately [154,232] milliseconds. There is/are still [8] thread(s) that are monitored by this Valve and may be stuck.
24-Aug-2018 14:35:07.996 WARNUNG [ContainerBackgroundProcessor[StandardEngine[Standalone]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread [http-nio-8090-exec-122] (id=[3661]) was previously reported to be stuck but has completed. It was active for approximately [127,339] milliseconds. There is/are still [7] thread(s) that are monitored by this Valve and may be stuck.
24-Aug-2018 14:35:07.996 WARNUNG [ContainerBackgroundProcessor[StandardEngine[Standalone]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread [http-nio-8090-exec-135] (id=[3674]) was previously reported to be stuck but has completed. It was active for approximately [127,374] milliseconds. There is/are still [6] thread(s) that are monitored by this Valve and may be stuck.
24-Aug-2018 14:35:07.996 WARNUNG [ContainerBackgroundProcessor[StandardEngine[Standalone]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread [http-nio-8090-exec-123] (id=[3662]) was previously reported to be stuck but has completed. It was active for approximately [93,553] milliseconds. There is/are still [5] thread(s) that are monitored by this Valve and may be stuck.

Since until now I only kept the CalDav synchronization reports for one day, I'm afraid I'm not able to compare the date/time-stamps from the server-log-files with the CalDav-synchronizer-report-files at the moment. I've changed the time-frame the reports are kept to three days, so I'll be able to do some alignement tomorrow.

Kate

Welcome!

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

Quick Links

Find more posts tagged with

confluence

server

confluence-server

atl-adm

team-calendars-for-confluence

sync

caldav