Hello Kevin, if you have absolutely nothing changed but the Java Virtual Machine I can only suggest going a step back and reinstalling 1.4.2_04 (and never change a running system again :-). If you have a connection pool configured in Tomcat, there should be normally only these connects, and not much more, only possible reconnects if something had timed out or you plugged the network cable. Perhaps you may look at the knldiag of the MaxDB if there are that much SQL sessions established/destroyed, and tell us what is seen there ... perhaps this will shed more light on this issue.
Regards Alexander Schröder SAP DB, SAP Labs Berlin > -----Original Message----- > From: Kevin Wilson [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 19, 2005 6:57 PM > To: Jira-User (E-mail); Maxdb (E-mail); i-net Crystal-Clear > support (E-mail) > Subject: TCP/IP connections to database not being closed when > not in use. > > [app server] > Sun JVM 1.4.2_08 > Tomcat 5.0.27 > SuSE Linux 9.1-32bit > > [db server] > MaxDB 7.5.0.23 > SuSE Linux 9.2-64bit > > After updating the app server's jvm from 1.4.2_04 to 1.4.2_08 > I am noticing > that the jdbc connections from tomcat to the database are > stacking up. there > was normally only around 10-20 connections shown by the > "netstat -tunap" > command but now there are over 200 shown and have been > increasing over the > past 5 days. > > Any ideas? I am at a loss since none of the connection code > for the apps > have changed. > > Thanks, > > Kevin > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
