Re: Unwanted SQL Developer inverse connection storming
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: jeff.d.smith@xxxxxxxxxx
- Date: Wed, 3 Apr 2013 17:17:48 +0100
My 2c
Don't talk to databases/listeners unless specifically asked to. Especially
management/infrastructure information in what is primarily a development
tool (even though I love it). Then have as many documented options for
obtaining reliable useful data as you can. :)
On Wed, Apr 3, 2013 at 5:10 PM, Jeff Smith <jeff.d.smith@xxxxxxxxxx> wrote:
> So that was put in to collect ping times for connections, with the
> intent at some point of displaying that visually for users.
>
> So you could see what databases were 'far away.'
>
> Obviously that last bit was never implemented, but we could do it for
> the next release. Any thoughts on whether that would be of use to you or
> your users?
>
> My 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.
>
> And since we're getting ready with a new release, now is a good time to
> address this.
>
> Jeff
>
>
> On 4/3/2013 11:31 AM, Martin Klier wrote:
> > Dear listers,
> >
> > recently we noticed that the Oracle SQL Developer causes a kind of
> > unwanted "inverse" connection storm to all configured databases, when we
> > start the SQL Developer. It's not restoring aborted connections or
> > stuff like that, all was quit before stopping the SQL dev., and
> > nevertheless each and every configured connection is "tested" at startup.
> >
> > In my example, it's doing the following for all configured connections
> > (tested with version 3.2.20.09):
> >
> > TNS connect:
> >
> (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=ww.xx.yy.zz)(PORT=1521))(CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=xyz)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))))
> > and gets back:
> >
> (DESCRIPTION=(TMP=)(VSNNUM=186647296)(ERR=12514)(ERROR_STACK=(ERROR=(CODE=12514)(EMFI=4))))
> >
> > I'm having multiple problems with this behavior:
> > 1.) it's useless, since the SQL dev does not display any information
> > about reachable/non-reachable databases. I simply can't see any benefit.
> > 2.) it's waste of network resources
> > 2.) it's most unwanted since your network can see what you have
> > configured (for example in a public WLAN, and in worst case a IDS might
> > feel like you are doing something nasty in the (for example, customer's)
> > network)
> >
> > Does somebody know why they are doing this, and why are they doing it
> > THIS very way?
> >
> > Thanks a lot in advance and best regards
> > Martin Klier
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
--
//www.freelists.org/webpage/oracle-l
Other related posts:
