Hello GWTViju, I'm pretty sure you are running into a race condition. The 500 means that an error ocurred in the server side - there should be somewhere a detailed stacktrace, check your logging settings. Check for member variables in your controllers, servlets and services which could be modified by two parallel requests. A particularily uggly thing I've seen is if your controller references a single database connection which is then used by multiple requests in parallel.
On Sep 28, 10:54 pm, bijuv v <vvbiju2...@googlemail.com> wrote: > Able to reproduce the same without proxy setup as well. I directly hit > the Websphere server (bypassing the proxy) and still get the same > error. > > Though I say I can reproduce locally (tomcat ), the steps will vary each time. > > I have taken another step now - Im printing the payload in the Filters > itself (just to make sure that the filters did not eat up the payload > for whatever reason it is! I'm using Spring Security + 2 additional > filters) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.