Re: Recommended Lock Mode for heavy JDBC usage?

"David Williams" <djw@smooth1.fsnet.co.uk> wrote in message news:<bbe0jk$c4q$1@news6.svr.pol.co.uk>... > "Anthony Presley" <anthony@zoraptera.com> wrote in message > news:a55ad738.0305312214.2e29b393@posting.google.com... > > So, it's REALLY bad to reply to ones own messages.... > > > > I've tried dropping and reloading the table, to no avail. > > > > Today, I went through and created some new routines to grab the rows > > at less than 50 at a time (in testing, I actually used values around > > 30). I also wrote a routine that grabs all 65K rows at one time. > > > > Both of them read and load into memory 8175 rows before crashing, > > always with the same error. I then redid the routines to start with > > the id of 8170, and start from there. It loads another 8175, then > > dies. Always, 8175 rows are read. > > > > Is this a performance issue? Is Informix doing some juggling and > > "closing" the db file? Any other ideas? I'm about at my wits end. > > > > - Try the query using dbacess on the server. > > - Go to http://www.iiug.org/software/index_JAVA.html and get jselect. > Try the query using that. > > - Log a support call with Informix. I think I'm down to having to log a support call with Informix. dbaccess runs just fine, as does jselect. Neither of them cause an issue. However, it MAY be the structure of my code, because while futzing with it this weekend I got it to pull out 16349 rows, of the 87,000. Very strange.