IllegalArgumentException when closing PreparedStatement

[Joe Kidd]

The following method is from a User bean. The method is used to verify login information by comparing information entered by a user against a MySQL database.

public String processLogin() throws SQLException
{
	String redirect = "login";

	Connection con = null;
	PreparedStatement stmt = null;
	String query = null;
	ResultSet qRes = null;
	try
	{
		con = General.dataSource.getConnection();

		//validate the user
		query = "select username from User where username=? and password=?";
		stmt = con.prepareStatement(query);
		stmt.setString(1, username);
		stmt.setString(2, password);
		qRes = stmt.executeQuery();

		if(qRes.first()) //valid
		{
			redirect = "home";
		}
	}
	catch(Exception e)
	{
		e.printStackTrace();
	}
	finally
	{
		qRes.close();
		stmt.close(); //line 90, exception here
		con.close();

		return redirect;
	}
}

Why would closing a PreparedStatement cause an exception to be thrown? The program runs fine if stmt.close(); is commented out... So, closing the ResultSet is fine, as is closing the Connection, but not the PreparedStatement

Here's the exception:

Caused by: java.lang.IllegalArgumentException: null source
	at java.util.EventObject.<init>(EventObject.java:38)
	at javax.sql.StatementEvent.<init>(StatementEvent.java:39)
	at com.mysql.jdbc.jdbc2.optional.JDBC4PreparedStatementWrapper.close(JDBC4PreparedStatementWrapper.java:70)
	at socNet.beans.User.processLogin(User.java:90)
	...

[Jeanne Boyarsky]

Driver bug? I don't know what else could cause that - it's very odd.

[Bauke Scholtz]

Google the stacktrace. You'll land at a MySQL bug page.

[Joe Kidd]

Bauke Scholtz wrote:Google the stacktrace. You'll land at a MySQL bug page.

I have, I searched for a while before I posted. The reason I ended up posting the question is because the MySQL bug you mentioned (http://bugs.mysql.com/bug.php?id=37645) was submitted back in 2008 (I just installed Netbeans 6.5.1 with Glassfish 2.1). There's another: http://bugs.mysql.com/bug.php?id=38699 that says there is a working fix. I just wanted to see if I was doing something wrong in my code, which I guess isn't the case.
Any idea how I could use the new version of MySQL Connector in Glassfish 2.1? Where should I put the .jar file and how do I make the server use it?

[Joe Kidd]

Ok, I figured out how to "fix" this problem. The idea is to setup the connection pool and the resource through NetBeans (I'm using 6.5.1) as opposed to through the Glassfish (2.1) admin console. There's a very nice tutorial that explains how to do this on the NetBeans website:

http://www.netbeans.org/kb/60/web/mysql-webapp.html#settingUpConnPool

I hope this helps anyone who ran into a similar problem.

[TestConfig testConfig]

Hi All,

I know this is a old post,I was also getting the above exception while closing the PreparedStatement.
Inorder to fix that problem I updated latest Mysql jar in the Glassfish server.
As said by Jeanne Boyarsky.

Hope this helps