Re: [dba-dev] Where to find all open DB connections and closes them

2010-07-01 Thread Fernand Vanrie

Now answers so far,
so wath's the problem:

I opened a DB connection using first the  dispatcher to have a 
Datasourcebrowser and then i fill the grid with data from a registered 
database connected to a MySQL over the native connector.
loadComponentFromURL(.component:DB/DataSourceBrowser, _beamer, 0, 
aProps)
The resulting activeconnection can been disposed orclosed but the 
object is still there without any further use.(giving a disposed exeption)
even after kiling the object the connection is still open as a sleep 
connection on the Mysql server and stay there for ever


- disabling or enabling the pooling  make no differences
- the connection stay there until i close OO

so: How can i find this half alive connection and kill it without 
closing OO


Thanks again

Fernand


hallo all,

When opening a DatasourceBrowser with the dispatcher using 
loadComponentFromURL(.component:DB/DataSourceBrowser, _beamer, 0, 
aProps)

I have a connection opened with the database server.

How can i find this opened connection and close it with the API ?

I tried  and found a activeConnection on the derivided rowset

orowset.activeconnection.dispose
or
orowset.activeConnection.close
does nothing  the connection stays open on the server site, only 
closing OO closes  this connection


Thanks for any hint


-
To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org
For additional commands, e-mail: dev-h...@dba.openoffice.org



-
To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org
For additional commands, e-mail: dev-h...@dba.openoffice.org



Re: [dba-dev] Where to find all open DB connections and closes them

2010-07-01 Thread Frank Schoenheit, Sun Microsystems Germany
Hi Fernand,

 When opening a DatasourceBrowser with the dispatcher using 
 loadComponentFromURL(.component:DB/DataSourceBrowser, _beamer, 0, 
 aProps)
 I have a connection opened with the database server.
 
 How can i find this opened connection and close it with the API ?
 
 I tried  and found a activeConnection on the derivided rowset
 
  orowset.activeconnection.dispose
  or
 orowset.activeConnection.close
 does nothing  the connection stays open on the server site, only closing 
 OO closes  this connection

Since you say in your other mail that disabling connection pooling
doesn't change the behavior, I can't think of any legitimate reason for
keeping the connection open - so, it sounds like a bug.

And yet more, there's no chance to iterate over opened connections, and
forcefully close them (as this would ... irritate a lot of other
components). Sorry to say.

Interesting question would be whether this also happens with MySQL over
JDBC, for instance. (One reason why this is interesting is because the
JDBC driver has built-in logging capabilities, see
http://wiki.services.openoffice.org/wiki/Logging_JDBC_Activity.)

Ciao
Frank

-- 
ORACLE
Frank Schönheit | Software Engineer | frank.schoenh...@sun.com

-
To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org
For additional commands, e-mail: dev-h...@dba.openoffice.org



Re: [dba-dev] Where to find all open DB connections and closes them

2010-07-01 Thread Fernand Vanrie

Frank ,

Thanks a million:  the bandit is the native connector :-)

with jdbc works like a charm

i post a issue

as I am in love with the native (high volume + high speed) i  will 
create a Help-db-JDBC  to do this small durthy jobs


greetz
Frernand

BTW: noch immer keine  Base heimweh  ?



Hi Fernand,

  
When opening a DatasourceBrowser with the dispatcher using 
loadComponentFromURL(.component:DB/DataSourceBrowser, _beamer, 0, 
aProps)

I have a connection opened with the database server.

How can i find this opened connection and close it with the API ?

I tried  and found a activeConnection on the derivided rowset

 orowset.activeconnection.dispose
 or
orowset.activeConnection.close
does nothing  the connection stays open on the server site, only closing 
OO closes  this connection



Since you say in your other mail that disabling connection pooling
doesn't change the behavior, I can't think of any legitimate reason for
keeping the connection open - so, it sounds like a bug.

And yet more, there's no chance to iterate over opened connections, and
forcefully close them (as this would ... irritate a lot of other
components). Sorry to say.

Interesting question would be whether this also happens with MySQL over
JDBC, for instance. (One reason why this is interesting is because the
JDBC driver has built-in logging capabilities, see
http://wiki.services.openoffice.org/wiki/Logging_JDBC_Activity.)

Ciao
Frank

  



-
To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org
For additional commands, e-mail: dev-h...@dba.openoffice.org