innovatecpm
IS-IT--Management
I have an application that uses MSMQ to pass messages to an application which takes these messages and writes data to a SQL Server 7.0 database running on NT 4.0. The process that pulls the messages from MSMQ then connects to and opens one database where it looks up some information (this process is a Java program that connects to the database via JDataConnect, a type 3 JDBC driver). It then determines which other database to connect to and open. Finally, it writes out data to this second database, including some logging information. In all, anywhere from 2-6 database connections are performed for each transaction (I know, I know, but I'm not the one who designed this...
) ). The system processes about 3,000 transactions per day, so there are probably a total of about 10,000 database connections made per day.
When the system is first started up and each time after rebooting, everything works well. After running for a day or so, an occasional exception is thrown ("Couldn't get connection to the 'DBNAME' database"
. Eventually within another day or so, the connection failures begin occurring with a lot more frequency. Rebooting the system will temporarily resolve the problem.
The number of user connections is set to 32,767 so I don't think it's a matter of running out of available connections. There is no other process running on this server. Anyone have any ideas on what might be causing this problem? Are there some other settings I should look at? X-)
) ). The system processes about 3,000 transactions per day, so there are probably a total of about 10,000 database connections made per day. When the system is first started up and each time after rebooting, everything works well. After running for a day or so, an occasional exception is thrown ("Couldn't get connection to the 'DBNAME' database"
. Eventually within another day or so, the connection failures begin occurring with a lot more frequency. Rebooting the system will temporarily resolve the problem. The number of user connections is set to 32,767 so I don't think it's a matter of running out of available connections. There is no other process running on this server. Anyone have any ideas on what might be causing this problem? Are there some other settings I should look at? X-)