Re: Unwanted SQL Developer inverse connection storming
From: Andrew Kerber <andrew.kerber_at_gmail.com>
Date: Wed, 3 Apr 2013 12:02:53 -0500
Message-ID: <CAJvnOJYBXKpBV48tUEtzqDX9vNfMDRhBiN-0f2M2MQKJnYEBeQ_at_mail.gmail.com>
And it is still a terrible idea. For one thing, most security standards require that ping response to be turned off for internal servers anyway, so no response means nothing If it is doing tnsping, you are also talking to the listenrs.
Date: Wed, 3 Apr 2013 12:02:53 -0500
Message-ID: <CAJvnOJYBXKpBV48tUEtzqDX9vNfMDRhBiN-0f2M2MQKJnYEBeQ_at_mail.gmail.com>
And it is still a terrible idea. For one thing, most security standards require that ping response to be turned off for internal servers anyway, so no response means nothing If it is doing tnsping, you are also talking to the listenrs.
On Wed, Apr 3, 2013 at 11:32 AM, Jeff Smith <jeff.d.smith_at_oracle.com> wrote:
> Sorry, horrible wording.
>
> To clarify, we're only pinging the server defined in the connection.
> We're not actually connecting or measuring connection times.
>
> Jeff
>
> On 4/3/2013 12:10 PM, Jeff Smith wrote:
> > y thought is that we should collect that on CONNECT time, not for all
> > connections defined in the tool at startup time, as you have noticed.
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
-- Andrew W. Kerber 'If at first you dont succeed, dont take up skydiving.' -- http://www.freelists.org/webpage/oracle-lReceived on Wed Apr 03 2013 - 19:02:53 CEST