-----Original Message----- From: Glenn Holmer <firstname.lastname@example.org> >> Is lazy close enabled? > >How do I tell? Is this an AS/400 thing or a Java thing? Oops- scratch that. I think lazy close is only an ODBC option (maybe it is in the JDBC drivers too, I am not sure). It means that whne you do issue a close, it won't get sent to the server until the next time you do some other request (in order to keep requests over the network to a minimum). >> 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(). I suppose you may also want to think about connection pooling so you are not just using one connection, and if the problem persists, maybe holding requests until they can get a connection all to themselves until the request is finished.. let us know how it works out! Luther +--- | 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: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.