pie154
pie154

Reputation: 613

JAVA: Concurrency control for access to list in java

I have a multi-threaded application that has a centrlaised list that is updated (written to) only by the main thread. I then have several other threads that need to periodically retrieve the list in its current state. Is there a method that can allow me to do this?

Upvotes: 5

Views: 4558

Answers (6)

gustafc
gustafc

Reputation: 28905

That depends on how you want to restrict the concurrency. The easiest way is probably using CopyOnWriteArrayList. When you grab an iterator from it, that iterator will mirror how the list looked at the point in time when the iterator was created - subsequent modifications will not be visible to the iterator. The upside is that it can cope with quite a lot of contention, the drawback is that adding new items is rather expensive.

The other way of doing is locking, the simplest way is probably wrapping the list with Collections.synchronizedList and synchronizing on the list when iterating.

A third way is using some kind of BlockingQueue and feed the new elements to the workers.

Edit: As the OP stated only a snapshot is needed, CopyOnWriteArrayList is probably the best out-of-the-box alternative. An alternative (for cheaper adding, but costlier reading) is just creating a copy of a synchronizedList when traversion is needed (copy-on-read rather than copy-on-write):

List<Foo> originalList = Collections.synchronizedList(new ArrayList());

public void mainThread() {
    while(true)
        originalList.add(getSomething());
}

public void workerThread() {
    while(true) {
        List<Foo> copiedList;
        synchronized (originalList) {
             copiedList = originalList.add(something);
        }
        for (Foo f : copiedList) process(f);
    }
}

Edit: Come to think of it, the copy-on-read version could simplified a bit to avoid all synchronized blocks:

List<Foo> originalList = Collections.synchronizedList(new ArrayList());

public void mainThread() {
    while(true)
        originalList.add(getSomething());
}

public void workerThread() {
    while(true) {
        for (Foo f : originalList.toArray(new Foo[0])) 
            process(f);
    }
}

Edit 2: Here's a simple wrapper for a copy-on-read list which doesn't use any helpers, and which tries to be as fine-grained in the locking as possible (I've deliberately made it somewhat excessive, bordering on suboptimal, to demonstrate where locking is needed):

class CopyOnReadList<T> {

    private final List<T> items = new ArrayList<T>();

    public void add(T item) {
        synchronized (items) {
            // Add item while holding the lock.
            items.add(item);
        }
    }

    public List<T> makeSnapshot() {
        List<T> copy = new ArrayList<T>();
        synchronized (items) {
            // Make a copy while holding the lock.
            for (T t : items) copy.add(t);
        }
        return copy;
    }

}

// Usage:
CopyOnReadList<String> stuff = new CopyOnReadList<String>();
stuff.add("hello");
for (String s : stuff.makeSnapshot())
    System.out.println(s);

Basically, when you to lock when you:

  1. ... add an item to the list.
  2. ... iterate over the list to make a copy of it.

Upvotes: 12

sjlee
sjlee

Reputation: 7896

If the write is not frequent and the data size is small, the CopyOnWriteArrayList is a great choice. Otherwise, your write performance may be an issue.

If you do not need a full List interface (mainly the random access via index), then you have more options. If your use case is satisfied with the Queue interface, then things like ConcurrentLinkedQueue would be an excellent choice. If you can live with the Queue interface, then something like this becomes possible:

Queue<Foo> originalList = new ConcurrentLinkedQueue<Foo>();

public void mainWrite() {
    // main thread
    originalList.add(getSomething()); // no locking needed
}

public void workerRead() {
    // executed by worker threads
    // iterate without holding the lock
    for (Foo f: originalList) {
        process(f);
    }
}

Upvotes: 0

tylermac
tylermac

Reputation: 489

Take a look at Java's Concurrency Package. There should be something there you can use.

Do the child threads need read only access? Do the just need an item of the top of the list? How is the list being used, might help us understand your problem better, and point you in a clearer direction.

To pass a snapshot of the list, just create a new List populated by the original list.

List<Object> newList;
synchronize (originalList)
{
    newList = new ArrayList<Object>(originalList);
}
return newList;

Synchronized may or may not be beneficial here. I'm not sure.

Upvotes: 2

hakan
hakan

Reputation: 1851

You can consider using a read - write lock mechanism. If your JDK version is 1.5 or newer, you can use ReentrantReadWriteLock.

Upvotes: 3

mkvcvc
mkvcvc

Reputation: 1563

If the threads are only "reading" the list you're safe with just using List. If the list is going to be "written to" (get changed in any way) use Vector instead of List.

Upvotes: 1

user268396
user268396

Reputation: 12006

If you simply want a read-only snapshot and the list is not too large:

private static List<TypeHere> getCurrentList() { 
  /* code to return the list as it currently is */
}
public static List<TypeHere> snapshot() {
  TypeHere[] objects = getCurrentList().toArray(new TypeHere[] {});
  return Collections.unmodifiableList(Arrays.asList(objects));
} 

Upvotes: 0

Related Questions