What exactly does it mean when they say that StringBuffer class is synchronized? Are all methods of that class declared synchronized?

Question

I know that StringBuffer class is synchronized(or thread-safe) while StringBuilder is not. Does this mean that all the methods within StringBuffer such as append are declared with the keyword synchronized ?

I checked the hava API: http://docs.oracle.com/javase/7/docs/api/java/lang/StringBuffer.html

As per the API, methods such as public StringBuffer append(String str)are not declared with the keyword synchronized.

Can anyone explain?

It means: thread-safe. And no, not a single method is `static` in that class. It should be somewhere in the documentation. `static` and thread-safe doesn't have any direct relationship though — x80486, Apr 19 '15 at 11:49
This simply means that you should use `StringBuilder` unless you need to access it from multiple threads simultaneously. — Bubletan, Apr 19 '15 at 11:52
You seem to be confused between `static` and `synchronized`, please proof read your question and work out what you want to ask. Also, be aware that thread safety does not require synchronization. — Boris the Spider, Apr 19 '15 at 11:56
Be also aware that synchronization does not automatically implies thread safety. — JB Nizet, Apr 19 '15 at 11:58
possible duplicate of [Meaning of " StringBuilders are not thread safe"](http://stackoverflow.com/questions/26860173/meaning-of-stringbuilders-are-not-thread-safe) — Joe, Apr 19 '15 at 12:15

Bohuslav Burghardt · Accepted Answer · 2015-04-19T12:02:40.863

The synchronized keyword doesn't show up in the generated JavaDoc, but if you open the source code of StringBuffer, you'll see that each public method which can change the state of the instance actually has synchronized keyword in its signature, eg.

public synchronized StringBuffer append(StringBuffer sb) {
    toStringCache = null;
    super.append(sb);
    return this;
}

As others mentioned in the comments static doesn't directly relate to thread safety. If you meant that the methods are not declared with synchronized keyword, then this should answer your question.

score 2 · Answer 2 · answered Apr 19 '15 at 17:57

"Thread safety" is a slippery idea.

When somebody says that a class such as StringBuffer is "thread safe" they usually mean that an instance of the class will not behave in weird, unexpected ways when it is accessed by more than one thread. For example, if thread A tries to append "yellow" to a StringBuffer at the same time as thread B appends "green", the final value might be "yellowgreen" or it might be "greenyellow", but it won't be "yegrelleown". No IllegalStateException will be thrown, and it won't crash the JVM.

Those guarantees make each individual instance of the class thread safe, but they won't make your program thread safe. If your program has some thread C that tries to read the StringBuffer at the same time, then it might get either of the two values above, or it might get just "yellow", or just "green", or even the empty string. If it's important for thread C to see both color names in the string, then you will need additional synchronization to guarantee that it happens that way.

Building a program entirely out of "thread-safe" classes does not automatically make the whole program "thread safe."

As other answers have already told you, the StringBuffer class achieves thread-safety by making all of its methods synchronized, but that is not the only way to achieve thread-safety, and in some cases, that may not be enough to achieve it. If you want to know what is thread-safe and what isn't, it's important to read the documentation.

Also, when you read it, pay attention to how the class was meant to be used. If somebody advertizes a class as "thread safe" in some particular use-case, that doesn't mean it will be "thread safe" in other use cases

What exactly does it mean when they say that StringBuffer class is synchronized? Are all methods of that class declared synchronized?

2 Answers2