Thanks for your help. On server side I've used single thread executor to send all UI messages sequentially, then also I’m getting same exception.
Actually we are using GWT event service to send asynchronous messages from server to client. So now all RemoteEventServiceServlet.addEvent() are executed sequentially, then also it gives ConcurrentModificationException. On Tuesday, December 10, 2013 6:36:32 PM UTC+5:30, Jens wrote: > > I don't think its a problem with GWT. > > It's more likely that your own server code has a multi-threading bug that > you are not yet aware of. While request A is done and a HashMap is > serialized by GWT to send it to the browser, a second request B modifies > the same HashMap instance which results in the exception you see. > > > -- J. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
