I will develop a similarly functional sample app this weekend and post it
to you as a zipped file.
BR,
Adnan
On Thu, Aug 2, 2012 at 3:29 PM, Marek Potociar <marek.potociar_at_oracle.com>wrote:
>
> On Jul 31, 2012, at 8:36 PM, Adnan <adnan.maks_at_gmail.com> wrote:
>
> > 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?
>
> It's hard to analyze your problem without additional data. It would be
> best if you could send us a heap dump, but that may be problematic from the
> security perspective of your product. So perhaps a better option would be
> to create a small example application that reproduces the same behavior
> when put under the load and send us the application for analysis.
>
> Thanks,
> Marek
> >
> >
> >
> > --
> > Thanks and Regards,
> > Adnan, Mohammed
> > Bangalore
> > cell:+91 9886529874
> >
>
>
--
Thanks and Regards,
Adnan, Mohammed
Bangalore
cell:+91 9886529874