This is a really bizzare problem. I have written a java consoloe program that transfers data from a Interbase server and puts it in a flat file. I am using JDBC to connect to the Interbase server. I open a connection to the database, run my query, get Recordset and start iterating through the recordset. For each row in the record set, I read all the data in the row, massage it and write it to a flat file. I close the recordset and the database connection after all the records have been written. Pretty standard stuff
This used to work perfectly before. However, recently, Interbase has started dropping the connection. At random times, I get an IO exception from Interbase that says the connection has been dropped. One thing I have noticed is that the CPU goes to 100%. It never used to because the process does a lot of database and file I/o's. I checked the ProcessManager and there is a process called CSRSS that is using up aout 50% of the CPU and rest of the CPU is divided up between java, interbase and interserver. I don't know whther the connect timeouts are somehow linked to CPU usage. Maybe the Interbase server is no able to communicate because it doesn't get enough CPU cycles and it times out
So, does anyone know how Interbase handles Connection timeouts and how I can increase the timeout
Also, does anyone know what CSRSS.exe is? Google says that it's either the MS-DOS console or a virus, and I'm pretty sure it's not a virus. Why should it take so much CPU?
Joined: Nov 05, 2004
Just bumping this to see if anyone has any idea about Interbase. Anyone? I figure out the CRSS. If I disable logging or make the logging go to a log file, then CRSS stops taking CPU