Re: EHOSTUNREACH should not be considered as an exception when send on a loopback network interface.

2011-12-12 Thread Charles Lee
On 12/12/2011 07:48 PM, Neil Richards wrote: On Thu, 2011-12-08 at 10:54 +, Chris Hegarty wrote: On 08/12/2011 03:16, Charles Lee wrote: Hi Alan, hi Chris, Thank you for reviewing this and creating a bug id for me. I have put a revised webrev at http://cr.openjdk.java.net/~littlee/711

Re: EHOSTUNREACH should not be considered as an exception when send on a loopback network interface.

2011-12-12 Thread Neil Richards
On Thu, 2011-12-08 at 10:54 +, Chris Hegarty wrote: > On 08/12/2011 03:16, Charles Lee wrote: > > > > Hi Alan, hi Chris, > > > > Thank you for reviewing this and creating a bug id for me. I have put a > > revised webrev at http://cr.openjdk.java.net/~littlee/7118907/webrev.00/ > >

Re: EHOSTUNREACH should not be considered as an exception when send on a loopback network interface.

2011-12-08 Thread Chris Hegarty
On 08/12/2011 03:16, Charles Lee wrote: Hi Alan, hi Chris, Thank you for reviewing this and creating a bug id for me. I have put a revised webrev at http://cr.openjdk.java.net/~littlee/7118907/webrev.00/ . Looks fine to me. Let

Re: EHOSTUNREACH should not be considered as an exception when send on a loopback network interface.

2011-12-07 Thread Charles Lee
On 12/07/2011 09:39 PM, Chris Hegarty wrote: On 07/12/2011 11:12, Alan Bateman wrote: On 07/12/2011 08:11, Charles Lee wrote: : I'd like to raise this issue again. The patch is on the [1]: When a loopback network interface is bound to sendto and connect, in some linuxes it will throw an EIN

Re: EHOSTUNREACH should not be considered as an exception when send on a loopback network interface.

2011-12-07 Thread Chris Hegarty
On 07/12/2011 11:12, Alan Bateman wrote: On 07/12/2011 08:11, Charles Lee wrote: : I'd like to raise this issue again. The patch is on the [1]: When a loopback network interface is bound to sendto and connect, in some linuxes it will throw an EINVAL errno, in other linuxes (AIX, iSeries) it

Re: EHOSTUNREACH should not be considered as an exception when send on a loopback network interface.

2011-12-07 Thread Alan Bateman
On 07/12/2011 08:11, Charles Lee wrote: : I'd like to raise this issue again. The patch is on the [1]: When a loopback network interface is bound to sendto and connect, in some linuxes it will throw an EINVAL errno, in other linuxes (AIX, iSeries) it will throw an EHOSTUNREACH errno. The man

Re: EHOSTUNREACH should not be considered as an exception when send on a loopback network interface.

2011-12-07 Thread Charles Lee
On 09/02/2011 12:58 PM, Charles Lee wrote: On 09/02/2011 12:50 PM, Charles Lee wrote: Hi guys, In some linuxes, when you bind on a loopback network interface, sendto will be fail and errono will be set to EHOSTUNREACH. In this situation, EHOSTUNREACH maybe need treat as INVAL: return false, n

Re: EHOSTUNREACH should not be considered as an exception when send on a loopback network interface.

2011-09-01 Thread Charles Lee
On 09/02/2011 12:50 PM, Charles Lee wrote: Hi guys, In some linuxes, when you bind on a loopback network interface, sendto will be fail and errono will be set to EHOSTUNREACH. In this situation, EHOSTUNREACH maybe need treat as INVAL: return false, not throw an exception. Patch is attached.

EHOSTUNREACH should not be considered as an exception when send on a loopback network interface.

2011-09-01 Thread Charles Lee
Hi guys, In some linuxes, when you bind on a loopback network interface, sendto will be fail and errono will be set to EHOSTUNREACH. In this situation, EHOSTUNREACH maybe need treat as INVAL: return false, not throw an exception. Patch is attached. Does anyone interested in this issue? --