Sorry for late reply. We have fixed the issue. Kubernetes ingress file was
causing multiple requests to be sent over and over again. Proxy timeout
along with read and send timeouts were not present in that file. We have
added them and now the process is working fine allowing it to complete with
onl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ripu,
On 6/9/20 08:03, Ripu Daman wrote:
> Hello everyone,
>
> I work in an IT firm as a software engineer. I don't know whether
> it's a right platform to ask questions based on personal projects
> but i believe i will get some help from here.
>
>
I assume a servlet request is kicking off this process? If this is correct
then are you 100% sure that something is not calling the servlet more than
once? Perhaps a retry after a timeout or something?
Turn your access log on and look at what requests are coming in to the
server
Paul
On Tue, Ju
Hello everyone,
I work in an IT firm as a software engineer. I don't know whether it's a
right platform to ask questions based on personal projects but i believe i
will get some help from here.
We are facing an issue regarding multiple threads being created for a
servlet execution running in tomc
