Interesting question... see comments below
for each post there should be a response = that's the http specification.
There is no limit in the java servlet spec to the number of simultaneous
requests. A server is normally expected to queue requests or reject them
("temporarily unavailable") but for each request there is still a
response - otherwise you'd get a timeout ("server not responding")
The servlet spec does provide alternative mechanisms for scheduling. A
good design will always assume that many requests can be concurrently
occurring and handle that accordingly - for example by using stateless
objects and transactional data stores. Avoid synchronous servlets like
the plague.
Either you are somehow *not* generating more than one post or you are
getting more than one response and overwriting the results.
Try:
1. watching the request/response with firebug or similar and do some
console logging of state in your client
2. Add some debugging output to the servlet to see whats happening there.
Then study the results and determine the causality! At least, that's
what I'd do.
HTH
Alan