Bug #43096 Unknown prepared statement handler (1) given to mysql_stmt_execute
Submitted: 23 Feb 2009 5:50 Modified: 23 Mar 2009 16:58
Reporter: Satya Siripuram Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Prepared statements Severity:S2 (Serious)
Version:5.0.22 OS:Windows (Unknown prepared statement handler (1) given to mysql_stmt_execute)
Assigned to: CPU Architecture:Any
Tags: Unknown prepared statement handler (1) given to mysql_stmt_execute

[23 Feb 2009 5:50] Satya Siripuram 
Description:
java.sql.SQLException: Unknown prepared statement handler (1) given to mysql_stmt_execute
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:946)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2870)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1573)
        at com.mysql.jdbc.ServerPreparedStatement.serverExecute(ServerPreparedStatement.java:1169)
        at com.mysql.jdbc.ServerPreparedStatement.executeInternal(ServerPreparedStatement.java:693)
        at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1266)
        at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:93)

when we are using the external IP Address then we are not getting the above error, But, when we are using 127.0.0.1 in place of external IP for database we are getting the above error. Is it a mysql bug??.

Thanks & Regards,
Satya Siripuram

How to repeat:
when we are using the external IP Address then we are not getting the above error, But, when we are using 127.0.0.1 in place of external IP for database we are getting the above error. Is it a mysql bug??.
[23 Feb 2009 16:58] Valeriy Kravchuk 
Thank you for the problem report. Please, try to repeat with a newer version of server, 5.0.77, and inform about the results.
[24 Mar 2009 0:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".