Gson is not threadsafe

[GoogleCodeExporter]

Gson throws ConcurrentModificationException when used concurrently. 
See the discussion in http://groups.google.com/group/google-
gson/browse_thread/thread/563bb51ee2495081

Original issue reported on code.google.com by inder123 on 20 Oct 2008 at 6:28

[GoogleCodeExporter]

I add a test for this in r274

Original comment by inder123 on 20 Oct 2008 at 7:49

[GoogleCodeExporter]

The culprit is ObjectNavigatorFactory which holds the memory stack reference. 
This 
stack must be held per call, not throughout the lifetime of Gson.

Original comment by inder123 on 20 Oct 2008 at 7:49

[GoogleCodeExporter]

Fixed in r276

Original comment by inder123 on 20 Oct 2008 at 8:11

• Changed state: Fixed

[aarengee]

The perfomance hit might be an issue for us so we resorted to using an overrride by using our own Serde for util.date and sql.date.

Uses FastDateFormat instead of SimpleDateFormat to ensure you dont take a performance hit due to serial usage (synchronize write and read)

Have added some sample code in github gist.