Re: Unwanted SQL Developer inverse connection storming
- From: Jeff Smith <jeff.d.smith@xxxxxxxxxx>
- To: Andrew Kerber <andrew.kerber@xxxxxxxxx>
- Date: Mon, 08 Apr 2013 15:08:49 -0400
So, another clarification - we're doing doing a PING either. We're doing
a TNSPING.
And it is actually being used - not in a super secret way - if you mouse
over the connection label in the tree you'll see a 'Last Ping: XXX ms'
if the listener was able to respond, e.g. db is up.
So some help here - what is 'bad' about this behavior?
Thanks everyone,
Jeff Smith
Product Manager, Oracle SQL Developer
On 4/3/2013 1:02 PM, Andrew Kerber wrote:
> 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@xxxxxxxxxx
> <mailto:jeff.d.smith@xxxxxxxxxx>> 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.
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
>
>
> --
> Andrew W. Kerber
>
> 'If at first you dont succeed, dont take up skydiving.'
--
//www.freelists.org/webpage/oracle-l
Other related posts:
