Clarified Issue

[kushaank]

I had an issue about concurrency that Rami cleared. Just wanted to share it with everyone
My question was- "So far, I haven't come across a single concurrent modification error. Is there a way of testing a specific scenario where i have to get one if I'm not using synchronized lists ?"

Heres what he said-
You may not be getting these errors for multiple reasons:

You have a single-core machine that you are testing your code on
You have a multi-core processors, but only one thread is used for your application
You have too many print statements that are causing enough delay in your program making it avoid such errors
Either way, when we test your code on another computer, things may come-up. I advise you to completely run all the scenarios on your program on one of the lab machines and make sure you comment out all the print statements.

[smoran02]

So if we run the scenarios on a lab machine and we have no concurrent modification errors, we aren't required to use synchronized lists?

[choiRyan]

You should absolutely still use synchronized lists. Not having errors in a
trial run could basically come down to luck. (Concurrency problem tend to
occur "sometimes") No need to take risks here...
On Nov 3, 2013 3:35 AM, "Spencer Moran" [email protected] wrote:

So if we run the scenarios on a lab machine and we have no concurrent
modification errors, we aren't required to use synchronized lists?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/97#issuecomment-27642148
.

[alghanmi]

@smoran02 your assumption is incorrect. You are required to use synchronized lists. My point is if you don't see them, that does not mean they don't exist.