Comments on: Why synchronize? Go ATOMIC! http://www.javablogging.com/why-synchronize-go-atomic/ Tracking surprises, features and bugs Sun, 05 Feb 2012 15:43:49 -0500 http://wordpress.org/?v=2.8 hourly 1 By: Kiren http://www.javablogging.com/why-synchronize-go-atomic/comment-page-1/#comment-11116 Kiren Wed, 08 Jun 2011 08:16:03 +0000 http://www.javablogging.com/?p=303#comment-11116 I've used atomic integer, and interestingly, it does seem to be not totally threadsafe...I have an app using an AtomicInteger as an index over an array. Sometimes, it does not behave: int indexVal=index.getAndIncrement(); // Keep this in case its cause the side-effect (1 in 14400). logger.debug("Getting connection from " + indexVal); DataSource myDs = dataSources.get(indexVal); if (index.get() >= dataSources.size()) { index.set(0); } return myDs; For some reason, the index goes pass the length, as in the comment, maybe 1 every 14000 requests, 25 conncurrent requests. I’ve used atomic integer, and interestingly, it does seem to be not totally threadsafe…I have an app using an AtomicInteger as an index over an array.

Sometimes, it does not behave:
int indexVal=index.getAndIncrement(); // Keep this in case its cause the side-effect (1 in 14400).
logger.debug(”Getting connection from ” + indexVal);
DataSource myDs = dataSources.get(indexVal);

if (index.get() >= dataSources.size()) {
index.set(0);
}
return myDs;

For some reason, the index goes pass the length, as in the comment, maybe 1 every 14000 requests, 25 conncurrent requests.

]]>