Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: High
Fix Version/s: 3.1
Affects Version/s: 2.10.4, 3.0.1, 3.0.2
Component/s: None
Labels:

Bug Fix Policy:
View Atlassian Server bug fix policy

The implementation of ClusterManager for non clustered licenses does not implement any kind of locking at all.

This means oncePerCluster (such as the ClusterSafetyJob) jobs can run concurrently, amongst other problems, which can lead to errors.

Update: see the comment below for patch instructions.

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List

NonClusterManager$SimpleClusteredLock.class
1 kB
08/Oct/2009 12:17 AM
NonClusterManager.java
4 kB
26/May/2010 11:55 PM
NonClusterManager.class
5 kB
08/Oct/2009 12:17 AM
nonclustered.zip
3 kB
30/Oct/2009 4:41 AM

causes

CONFSERVER-16989 Address frequency of cluster panic errors

Closed

CONFSERVER-17434 run Job DEFAULT.ClusterSafetyJob threw an unhandled Exception: java.lang.RuntimeException: More than one cluster safety number in database.

Closed

CONFSERVER-17158 installPlugin remote API causes Confluence to crash

Closed

is duplicated by

CONFSERVER-17201 Unclustered instance stopps with cluster panic during db backup since Confluence V3

Closed

CONFSERVER-16963 Cluster safety job throws an exception on system setup

Closed

relates to

CONFSERVER-17495 Cluster panics immediatley on startup with PATCHED confluence 3.0.2

Closed

(1 relates to)

Assignee:: Andrew Lynch (Inactive)

Reporter:: Andrew Lynch (Inactive)

Votes:: 1 Vote for this issue

Watchers:: 11 Start watching this issue

Created:: 07/Oct/2009 7:15 AM

Updated:: 11/Oct/2018 8:42 AM

Resolved:: 09/Oct/2009 6:38 AM

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates