• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Devaka Cooray
  • Tim Cooke
Sheriffs:
  • Rob Spoor
  • Liutauras Vilda
  • paul wheaton
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Mikalai Zaikin
  • Carey Brown
  • Piet Souris
Bartenders:
  • Stephan van Hulst

vetor thread safe?

 
Ranch Hand
Posts: 63
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

If I use a vector to store some objects much I synchronize access or is it thread safe?

Thanks
 
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It is thread-safe.
 
Master Rancher
Posts: 5045
80
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It is, technically, in the sense that each method individually is thread-safe. However it's difficult to accomplish anything useful with this class without some additional synchronization. For example when iterating, you need to synchronize, as shown here. Yes, that discussion is for Collections.synchronizedList(), but Vector works the same way. The basic problem is that while each individual method call is synchronized, nothing prevents other threads from inserting other method calls in between two calls that really need to go together. If you've just made a call to iterator.hasNext() and it returned true, can you safely call iterator.next()? Not without extra synchronization - because how do you know that some other thread didn't remove() or clear() the next item, immediately after you called hasNext()? In general, you don't. There are other examples where Vector and synchronizedList() usage require additional synchronization, but iteration is the most common.

My own opinion is that the synchronization in Vector and Collections.synchronizedList() is close to useless, and dangerously misleading. You're usually better off synchronizing on the list externally, using synchronized blocks. Or writing the code in a way that no synchronization is required at all.
 
Robert Kennedy
Ranch Hand
Posts: 63
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thank you very much for your detailed explanation. I will use locks.
 
A magnificient life is loaded with tough challenges. En garde tiny ad:
Gift giving made easy with the permaculture playing cards
https://coderanch.com/t/777758/Gift-giving-easy-permaculture-playing
reply
    Bookmark Topic Watch Topic
  • New Topic