Hi All,
We are facing an issue with DNS server caching on RHEL-based distros: after
the update of resolv.conf java application cannot resolve the hosts any more.
Reproducer is very simple:
1. Clean /etc/resolv.conf or connect to vpn and use vpn-only nameserver.
2. Launch the minimal java app [1]
Hi all,
I want to contribute this issue.
If there are a problem about this patch or a better way for openjdk
community, please advise me.
Thanks for
2015-04-22 0:31 GMT+09:00 KUBOTA Yuji :
> Hi all,
>
> I found an infinite waiting at TCPChannel#createConnection.
> This method flushes the DataOut
Hi Kubota,
I think that perhaps the AdoptOpenJDK project
(https://java.net/projects/adoptopenjdk) can help here.
I've copied in their mailing list, in case one of the developers there
can help you.
Thanks,
Ben
On Mon, May 4, 2015 at 5:19 PM, KUBOTA Yuji wrote:
> Hi all,
>
> I want to contribu
Hi all,
My apologies for the re-post and wrong link, the link [1] of the
initial post is not correctly.
The correct link is below.
[1]:
http://hg.openjdk.java.net/jdk9/jdk9/jdk/file/c5b5d9045728/src/java.rmi/share/classes/sun/rmi/transport/tcp/TCPChannel.java#l227
The users cant specify the tim
Hello,
not sure how I feel about the res_init(). Depending on the backends
used this might be expensive. Especially since it wont be rate
limited. The negative-ttl of 10s is for single records I thing. So at a
minimum you should rate-limit res_init to the same negative-ttl time).
But another aspe
On May 4, 5:38pm, sbaid...@redhat.com (Stanislav Baiduzhyi) wrote:
-- Subject: DNS resolution fails after resolv.conf update
| Hi All,
|
| We are facing an issue with DNS server caching on RHEL-based distros: after
| the update of resolv.conf java application cannot resolve the hosts any more.
