Re: Unwanted SQL Developer inverse connection storming

From: Andrew Kerber <andrew.kerber_at_gmail.com>
Date: Mon, 8 Apr 2013 15:01:22 -0500
Message-ID: <CAJvnOJbPOiK5guDtDVz+G0ZxiD21Ym3miMUbRdyQr_c3UOfDhA_at_mail.gmail.com>

Even worse, in a consulting environment with multiple clients, it could be trying to ping client A from client B's network. Client B would then want to know what the heck is going on. It is also very bad programming practice, I dont want my programs doing network activity unless I tell them to.

On Mon, Apr 8, 2013 at 2:28 PM, Jeff Smith <jeff.d.smith_at_oracle.com> wrote:

> Flood is a subjective term - are you experiencing bandwidth issues?
>
> The behavior and feature should and will be documented going forward.
> Jeff
>
>
> On 4/8/2013 3:19 PM, breitliw_at_centrexcc.com wrote:
>
>> It floods the network with unnecessary traffic. At least
>> a) document this behaviour
>> b) give us the option to disable it
>>
>> On Mon, 08 Apr 2013 15:08:49 -0400, Jeff Smith <jeff.d.smith_at_oracle.com>
>> wrote:
>> 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?
>>>
>>>
>> --
>> Wolfgang Breitling
>> Centrex Consulting Corporation
>>
>>
>>
>

-- 
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'


--
http://www.freelists.org/webpage/oracle-l

Received on Mon Apr 08 2013 - 22:01:22 CEST