Hi,
I got u right. Thanks for the quick answer.
On 05-Feb-2018 8:32 PM, "Shiva Kumar K R" wrote:
> Hi,
>
> Thanks for the response, u r right I'll do the cleanup. And is tomcat uses
> new thread for each request or reuse existing thread.
>
> Thank you,
> Shiva
>
> On 05-Feb-2018 8:28 PM, "Johan
Hi,
Thanks for the response, u r right I'll do the cleanup. And is tomcat uses
new thread for each request or reuse existing thread.
Thank you,
Shiva
On 05-Feb-2018 8:28 PM, "Johan Compagner" wrote:
> If that is the case then the problem is also that you don't clean up the
> threadlocals..
> T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shiva,
On 2/5/18 9:36 AM, Shiva Kumar K R wrote:
> Hi,
>
> Component details: Tomcat = 8.5.24 Java = 1.8 OS = Ubuntu 16.04
> LTS
>
> Is above tomcat uses thread pool to process requests out of the box
> without any explicit configuration of thread
If that is the case then the problem is also that you don't clean up the
threadlocals..
That is a problem by itself, you should always after a request have cleanup
all your threadlocals
On 5 February 2018 at 15:36, Shiva Kumar K R
wrote:
> Hi,
>
> Component details:
> Tomcat = 8.5.24
> Java = 1.
Hi,
Component details:
Tomcat = 8.5.24
Java = 1.8
OS = Ubuntu 16.04 LTS
Is above tomcat uses thread pool to process requests out of the box without
any explicit configuration of thread pool.
I faced an issue while using threadlocal which was returning data stored in
previous request instead of c
