2005/9/29, Kevin Wilson <[EMAIL PROTECTED]>:
> [System Info]
>
> App server:
> SuSE 9.1-x32 SMP (AMD)
> JSDK 1.4.2_08
> Tomcat 5.0.27
>
> DB server:
> SuSE 9.2-x64 SMP (AMD)
> MaxDB 7.5.0.23
>
> JDBC Driver:
> sapdbc-7_5_01_00.jar
>
> I named it this to let me know which version of the db server I downloaded
> the jdbc driver from.
>
>
> I connect to the db using the following properties:
>
> props.setProperty("defaultRowPrefetch", "100");
> props.setProperty("defaultBatchValue", "25");
> props.setProperty("isolation", "TRANSACTION_READ_UNCOMMITTED");
> props.setProperty("reconnect", "on");
> props.setProperty("timeout", "120"); //in seconds
>
>
> Does the reconnect = on prevent connections from dying? A restart of tomcat
> kills all the connections and resets back to 5 on restart but then they
> slowly begin to grow in number. A look in the dbgui shows very few
> connections, usually only 2 to 14 active at any given time but netstat shows
> the same number of connections on both the app and db servers and they all
> have a status of established.
>
> Any ideas that could help me figure out why these connections are persisting
> without any usage over a long period of time would be appreciated.
This pretty much looks like std connection pool behavior: connections
are allocated and kept open to make DB accesses faster. Pool
implementations vary but you will generally observe a certain number
of connections open. This # is configurable btw. Also, idle
connections don't really take up much resources (mostly a bit of mem
but no CPU).
Kind regards
robert
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
