On Fri, Dec 29, 2017 at 11:15 AM, Chris Hegarty
wrote:
> On 29 Dec 2017, at 00:33, Steven Schlansker
> wrote:
>> Thanks for the discussion!
>>
>> So, it sounds like amending the message by default is going to be a
>> non-starter -- but at least adding the information otherwise might be
>> poss
, 2018 1:39:46 PM
To: Bernd Eckenfels
Cc: net-dev@openjdk.java.net
Subject: Re: Adding SocketChannel toString to connection exception messages
Hi Bernd,
Are you specifically talking about a SOCKS proxy, or something else?
-Chris.
On 3 Jan 2018, at 12:10, Bernd Eckenfels
mailto:e
Hi Bernd,
Are you specifically talking about a SOCKS proxy, or something else?
-Chris.
> On 3 Jan 2018, at 12:10, Bernd Eckenfels wrote:
>
> Hello,
>
> Just to add to the discussion, if proxies are used, the error should make
> clear if the problem is connecting the proxy or the endpoint. An
Hello,
Just to add to the discussion, if proxies are used, the error should make clear
if the problem is connecting the proxy or the endpoint. And for that case
(especially with multiple proxies) the actual failed address is also
interesting for trouble shooting (in that case higher level code
On 02/01/2018 21:25, Steven Schlansker wrote:
:
This would definitely be better than nothing! But it's still difficult, for
example a common allocation pattern for us would be to assign networks to
availability zones:
10.0.1.0/24 10.0.2.0/24 10.0.3.0/24
then if you pick the same last number
Hi Steven,
Steven Schlansker je 02. 01. 2018 ob 22:25 napisal:
On Jan 2, 2018, at 8:35 AM, Alan Bateman wrote:
On 29/12/2017 00:33, Steven Schlansker wrote:
Thanks for the discussion!
So, it sounds like amending the message by default is going to be a non-starter
-- but at least adding the
On 29/12/2017 00:33, Steven Schlansker wrote:
Thanks for the discussion!
So, it sounds like amending the message by default is going to be a non-starter
-- but at least adding the information otherwise might be possible.
There are examples in other area where exceptions include detail
informa
half of Chris Hegarty
>>
>> Sent: Friday, December 22, 2017 4:17:31 PM
>> To: Seán Coffey; David Holmes; Steven Schlansker
>> Cc: core-libs-dev; net-dev@openjdk.java.net
>> Subject: Re: Adding SocketChannel toString to connection exception messages
>>
>>
>>>
.
Gruss
Bernd
--
http://bernd.eckenfels.net
From: net-dev on behalf of Chris Hegarty
Sent: Friday, December 22, 2017 4:17:31 PM
To: Seán Coffey; David Holmes; Steven Schlansker
Cc: core-libs-dev; net-dev@openjdk.java.net
Subject: Re: Adding SocketChannel toString to
On 22/12/17 14:59, Seán Coffey wrote:
As someone who works with alot of log files, I'd like to chime in and
support Steven's end goal. Looking at a "Connection refused" error in
the middle of a log file that possibly extends to millions of lines is
near useless. In the era of cloud compute, di
As someone who works with alot of log files, I'd like to chime in and
support Steven's end goal. Looking at a "Connection refused" error in
the middle of a log file that possibly extends to millions of lines is
near useless. In the era of cloud compute, diagnosing network issues is
sure to beco
On 22/12/17 01:27, David Holmes wrote:
cc'ing net-dev as that might be the more appropriate list.
On 22/12/2017 10:59 AM, Steven Schlansker wrote:
On Dec 21, 2017, at 4:35 PM, David Holmes
wrote:
On 22/12/2017 10:29 AM, Steven Schlansker wrote:
On Dec 21, 2017, at 11:11 AM, Steven Schlansk
cc'ing net-dev as that might be the more appropriate list.
On 22/12/2017 10:59 AM, Steven Schlansker wrote:
On Dec 21, 2017, at 4:35 PM, David Holmes wrote:
On 22/12/2017 10:29 AM, Steven Schlansker wrote:
On Dec 21, 2017, at 11:11 AM, Steven Schlansker
wrote:
What if ConnectException in
13 matches
Mail list logo
