https://bz.apache.org/bugzilla/show_bug.cgi?id=63110
Philippe Mouawad <p.moua...@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|JMETER_5.1 |---
--- Comment #7 from Philippe Mouawad <p.moua...@ubik-ingenierie.com> ---
(In reply to miccah.castorina from comment #6)
> Philippe,
>
> After much experimentation I've found this issue only happens in a very
> specific environment.
>
> I have JMeter deployed in a Kubernetes cluster. The issue only happens right
> after I deploy a JMeter version 5.0 image to the pods. If I reboot the pods,
> the issue goes away.
>
> This does not happen with JMeter version 4.0, but I can't say for certain
> where the bug is: Kubernetes or JMeter?
>
> I would like to revisit this in JMeter 5.1 to see if the problem persists,
> but as of now this issue should not block its release due to the specificity
> of the bug.
Could you try setting this:
-Dsun.net.inetaddr.ttl=30
And in java.security :
networkaddress.cache.ttl=30
And try again ?
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
