http://forums.hotjoe.com/posts/list/9.page JForum - http://www.jforum.net [BEA][SQLServer JDBC Driver]No more data available to read. is the latest and greatest JDBC error I’ve gotten. I've posted some other threads on database related question in the past and I'm kind of at a junction where having a mentor at work would come in handy because i have a knack for finding connection handling (or lack there of) issues.

For the most part on the handful of apps I’ve built I use the following pattern to handle connections. As i progress through my apps and I mature as a developer it gets slightly more sophisticated, but here goes.
This code won't compile and obviously isn't complete (I’ll try and come up with a working example here in the next day or so)

[code]
public class DatabaseConnections
{
public static Connection getConnection(String JNDIName)
{
//get connection don't remember how this is done, I'll have to check it out
//when I'm at work if it's relevant, which i don't think it is.
}

public static void closeConnections(String debugging, Connection conn, Statement statement, ResultSet resultSet)
{
//use "debugging" for my logging.
try{
if(conn!=null)
conn.close()
}
catch (SQLException e){
//report exception
}
conn=null;
try{
if(statement!=null)
statement.close();
}
catch (SQLException e) {
//report exception
}
statement=null;
try{
if(resultSet!=null)
resultSet.close();
}
catch (SQLException e) {
//report exception
}
resultSet=null;
}
}
[/code]

Then in where ever i actually need a connection i do the following:

[code]
public class SomeQuery
{

public void pingDB()
{
Connection connPing=null;
PreparedStatement pStatementPing=null;
ResultSet resultSetPing =null;
try
{
connPing= DatabaseConnections.getConnection("MY_POOL");
pStatementPing = connPing.prepareStatement("SELECT * FROM DATA");
//bind variables if needed
resultSetPing = pStatementPing.executeQuery();

//do what you gotta do with resultSet
}
catch (SQLException e)
{
//do whatever
}
catch(Exception e)
{
//do whatever
}
finally
{
DatabaseConnections.closeConnections("pingDB", connPing, pStatementPing, resultSetPing);
}
}
}
[/code]

I'm in a j2ee environment so threading could be/is an issue here. Am I closing all my connections here?
Here's my understanding of what's going on.
connPing, pStatementPing & resultSetPing are created and stuff is done with them. Then a pass a copy of their reference to closeConnections().
Close closes the 3 objects, but the null assignment only affects conn, pStatement, & resultSet. When closeConnections() finishes running we go back to the of the finally and ultimatly out of pingDB()
I don't need to assign null to connPing pStatementPing, and resultSetPing since they drop out of scope (after being closed in closeConnections()) after the finally anyways.

So that's my understanding of what's going on. Assuming that the above is true and that I haven't confused myself (or anyone reading this ;) ) I'm fairly confident that I'm handling my connections properly.

So now for this [url=http://www.weblogic.com/docs45/techsupport/faq/jdbckona_mssqlserver.html]SQLException[/url]...I'm kinda clueless. I did the ol google and read a bunch of them and it seems like one of those fun errors that a decent amount of folks get and no one really knows what to do about it. The most popular answer is that the [url=http://forum.java.sun.com/thread.jspa?threadID=510477&messageID=2464074]connections aren't being handled properly.[/url] I also saw a hit about weblogic being not being configured properly, and then finally someone [url=http://www.mcse.ms/archive90-2004-12-1285118.html]thought it was a threading issue.[/url]

So i guess all this confusing inner dialog boils down to 2 questions.
Is using static methods in a different class to get & close connections okay in terms of proper connection management?

The second question would be any thoughts or solutions on this SQLException I'm getting.
]]> http://forums.hotjoe.com/posts/preList/296/1252.page http://forums.hotjoe.com/posts/preList/296/1252.page GMT http://forums.hotjoe.com/posts/preList/296/1376.page http://forums.hotjoe.com/posts/preList/296/1376.page GMT

No worries, I don't remember writing this one!

restarting the server def fixes the problem (in the short term). There was a setting we had to enable/disable in weblogic to fix it for good. I'll see if i can't get more details on monday so we can update this for posterity. ]]> http://forums.hotjoe.com/posts/preList/296/1400.page http://forums.hotjoe.com/posts/preList/296/1400.page GMT