Jersey JAX-RS 1.0 request not completed with client timesout

Question

We are using Jersey 1.6 on a RESTful Server, when a request is started, but takes to long and the client timesout (can be replicated with postman and cancelling request) the request is only partially completed and some but not all database calls are done, leaving the database in a inconsistant state. I thought REST servers, always complete the calls no matter what happens to the client, but this does not seem to be true here. No exceptions are logged in our logging system, what does Jersey do to a request if the client timesout?

Answer 1

I thought REST servers, always complete the calls no matter what happens to the client, but this does not seem to be true here.

This is incorrect assumption. REST describes just the way of interaction, it is still under service developer's responsibility to make the database changes consistent(transactional) if needed.

No exceptions are logged in our logging system, what does Jersey do to a request if the client timesout?

It will still send the response, but the client will ignore it due to timeout.