Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Confluence 6.15 server

Edited

Hello everyone,

Since upgrading to confluence 6.15.7, i started to have crashs several time (more then 5 crashs) per day.

After checking out the logs i found a timeout error caused by one of the workbox plugins, so i disabled all the workbox plugins and in-app notifications, with that the number of crash got to one crash per day.When i run the health check i have no error, and the JVM have always a 30% free memory, in the logs i can't found any errors ...

I also disabled the synchrony collaborative edit, after the upgrade since it require some change in the reverse proxy  fedloan

The instance have 5K users, 260 spaces and runs with 1024Mo JVM min and 2048 JVM max (the bdd runs in a different box)

(I had set the 200 maxthreads property in the reverse proxy connector) irs.gov 

If anyone have any advice/tips/ideas for me or experienced the same behaviour ?
Anything will be helpful since i can't found out the cause of this crasheseasybib

Thanks

0 comments

Comment

Log in or Sign up to comment