Re: RMI server

> >We have had this RMI server in light production
> >use for a couple of months, but last week used it heavily to bring
> >the first 18,000 pairs of shoes into our new warehouse.  All went
> >well for about a day and a half, but then the server began to crash
> >repeatedly with a message like "SQLCURSOR000000007 already open",
> >received and displayed by the client.  (Could this be some kind of
> >resource issue on the '400?)

Luther Ananda Miller wrote:
> 
> Are you closing all the results when you are done with them? 

Ooops... Don't know how I got in that habit, I do know better :)

> Is lazy close enabled? 

How do I tell?  Is this an AS/400 thing or a Java thing?

> How many connection are you using?

I create one Connection object at startup of the RMI server like this:

  DriverManager.registerDriver (new com.ibm.db2.jdbc.app.DB2Driver());
  Connection c = DriverManager.getConnection ("jdbc:db2://WEYCO400");

and then use it to create a bunch of PreparedStatements.  A single
ResultSet variable is then reassigned each time I need one, with 
rs = ps.executeQuery().

Thanks for the response, I am closing all the ResultSets now as soon
as I exit the "while rs.next()" loops, and we will stress test this 
as soon as we can.

-- 
____________________________________________________________
Glenn Holmer                          gholmer@weycogroup.com
Programmer/Analyst                       phone: 414.908.1809
Weyco Group, Inc.                          fax: 414.908.1601
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---