Re: socketRead0 time out problem

2014-04-17 Thread Bernd Eckenfels
Hm, hard to say. Did you use tcpdump to check if data is transfered or did you straced the java process? And you can check more socket stats with /sbin/ss -eomipt Bernd Am Fri, 18 Apr 2014 09:23:21 +0800 schrieb Li Li : > hi all > sorry to post a not-dev problem here. because I can't find

socketRead0 time out problem

2014-04-17 Thread Li Li
hi all sorry to post a not-dev problem here. because I can't find any active forum(few people use oracle's Networking now). I am using http client 4.3. I use PoolingHttpClientConnectionManager with many threads. but I found one thread hangs on socketRead0(other thread is correct) netstat

Re: RFR [9] 8040837: Avoid provoking NFEs when initializing InetAddrCachePolicy

2014-04-17 Thread Bernd Eckenfels
Am Thu, 17 Apr 2014 21:50:23 +0200 schrieb Bernd Eckenfels : > Hello, > > I would propose to use Integer.valueOf(tmp) instead, but looking at > the context I think it is even better to skip this and the following > null check with Integer.parseInt(). This is even shorter and it reduces the privi

Re: RFR [9] 8040837: Avoid provoking NFEs when initializing InetAddrCachePolicy

2014-04-17 Thread Bernd Eckenfels
Hello, I would propose to use Integer.valueOf(tmp) instead, but looking at the context I think it is even better to skip this and the following null check with Integer.parseInt(). Gruss Bernd what about using Integer.valueOf(tmp) Am Thu, 17 Apr 2014 17:56:10 +0200 schrieb Claes Redestad : > Hi,

Re: RFR [9] 8040837: Avoid provoking NFEs when initializing InetAddrCachePolicy

2014-04-17 Thread Mike Duigou
Looks fine to me. Mike On Apr 17 2014, at 08:56 , Claes Redestad wrote: > Hi, > > could I get a review of the following small patch to address 8040837: > > http://cr.openjdk.java.net/~lagergren/8040837/ > https://bugs.openjdk.java.net/browse/JDK-8040837 > > A simple JMH microbenchmark shows

RFR [9] 8040837: Avoid provoking NFEs when initializing InetAddrCachePolicy

2014-04-17 Thread Claes Redestad
Hi, could I get a review of the following small patch to address 8040837: http://cr.openjdk.java.net/~lagergren/8040837/ https://bugs.openjdk.java.net/browse/JDK-8040837 A simple JMH microbenchmark shows this actually might have a small benefit to startup: @GenerateMicroBenchmark