https://bz.apache.org/bugzilla/show_bug.cgi?id=66476

Omkar <patkarom...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|DUPLICATE                   |---
     Ever confirmed|1                           |0
             Status|RESOLVED                    |UNCONFIRMED

--- Comment #2 from Omkar <patkarom...@gmail.com> ---
(In reply to Mark Thomas from comment #1)
> I suspect this is triggered by local port re-use. Possible scenarios for
> that are described in bug 65776.
> 
> I suspect what you really need is an update to Tomcat 9.0.59 or later.
> 
> It might be possible to reduce the frequency via configuration (e.g. disable
> HTTP keep-alive) but those changes may cone with performance impacts.
> 
> The users list is the place to discuss possible workarounds if a Tomcat
> upgrade is not possible.
> 
> *** This bug has been marked as a duplicate of bug 65776 ***

Hi Thomas,

Thank you for prompt response. I really appreciate that. But I am still marking
the status as "Unconfirmed" because, we have still not been able to find cause
of the weird behavior. I mean, we can "assume" reuse of local port,... but why
this happens "ONLY" for requests coming from outside network ? Why this does
not happen for requests sent from within the internal company network. I mean,
i would agree if the behaviour is same across different requests, but here the
distinction is clear. 
The issue occurs "ONLY" for external requests and not internal requests. Why is
it so ? What can we do to confirm that local port is re-used ONLY for external
requests ? 
In other words, if i upgrade to Tomcat above 9.0.59 or above and if it still
continues the wierd behavior for external requests then ? How can we be sure
that upgrade is the only solution ? The bug 65776 you have referred definetly
talks about similar issue, but it says nothing about external or internal
requests.

We need your help to understand this unusual behavior. Let us know what more
diagnostics we can perform to find the root cause. Together we can find the
cause. One more information i would like to provide you here: -

The machine on which the Tomcat is running has local IP and public IP (for
external network or world). When requests comes from within the company network
it is via local IP and when the request comes from external world, it comes via
public IP.

Thanks and Regards
Omkar Patkar

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to