2009-02-11 08:27:41,798 ERROR [AWT-EventQueue-0] Catch.all - Uncaught exception on [Logger Daemon]: '1.2260857675E10' in column '1' is outside valid range for the datatype INTEGER. - query: SHOW PROCESSLIST /*jp 186110425*/ eE: '1.2260857675E10' in column '1' is outside valid range for the datatype INTEGER. - query: SHOW PROCESSLIST /*jp 186110425*/ at bY.a(SourceFile:331) at av.a(SourceFile:360) at av.a(SourceFile:351) at av.a(SourceFile:275) at aV.d(SourceFile:255) at aV.run(SourceFile:178) at java.lang.Thread.run(Unknown Source) Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLDataException: '1.2260857675E10' in column '1' is outside valid range for the datatype INTEGER. at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Sou rce) at java.lang.reflect.Constructor.newInstance(Unknown Source) at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at com.mysql.jdbc.Util.getInstance(Util.java:381) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:999) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926) at com.mysql.jdbc.ResultSetImpl.throwRangeException(ResultSetImpl.java:7 872) at com.mysql.jdbc.ResultSetImpl.parseIntAsDouble(ResultSetImpl.java:7114 ) at com.mysql.jdbc.ResultSetImpl.getInt(ResultSetImpl.java:2666) at com.mysql.jdbc.ResultSetImpl.getInt(ResultSetImpl.java:2777) at dT.a(SourceFile:34) at cb.a(SourceFile:254) at bY.a(SourceFile:329) ... 6 more
Jet Profiler for MySQL erroneously uses 32-bit signed integers for thread ids instead of longs. Your server has been up for so long and served so many connections that the counter has gone past an int! Uptime: 490 days 5 hours 58 min 16 sec - Impressive. You should be able to confirm this by issuing
SHOW PROCESSLIST;
and checking the highest Id, it will be greater than 2147483647.
Thanks for spotting this bug. It should be fixed and out in the next release, hopefully within the next couple of days. I'll notify you when it's out.