I have successfully got Jersey advocated as the standard REST framework for
our company's API and have it live in production now. However, when we run
a continuous load of just 26 hits/sec, we observe that after 100 hrs of
running, the response times are too high for each event processing
resulting in decreased performance.
We are running a Jersey/OAuth/tomcat setup with the standard connector
configuration in tomcat's server.xml and facing this issue. Any idea of
that's because of any thread local variables created by Jersey which maybe
causing threads to not end and eating up the server's thread space?
If so, do we have a way to release these thread local variables when
committing a response back to the client?
--
Thanks and Regards,
Adnan, Mohammed
Bangalore
cell:+91 9886529874