Description:
update SQL： insert into OPLOG (OPNAME,OPREALNAME,OPIP,OPTIME,OPDATA) values ('admin','admin','10.43.64.58',Now(),'0
502×÷0
90803ó0
5020
502×÷08±:admin07032006-11-300
70710.43.64.580
8050005)')
com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:
** BEGIN NESTED EXCEPTION **
java.io.EOFException
STACKTRACE:
java.io.EOFException
at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1902)
at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2348)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2858)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1570)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1665)
at com.mysql.jdbc.Connection.execSQL(Connection.java:2972)
at com.mysql.jdbc.Connection.execSQL(Connection.java:2902)
at com.mysql.jdbc.Statement.execute(Statement.java:529)
at server.database.DBAccess.exeUpdate(DBAccess.java:195)
at server.database.DBoperatorstat.insert(DBoperatorstat.java:72)
at server.implement.UserLoginImp.checkip(UserLoginImp.java:102)
at server.implement.UserLoginImp.load(UserLoginImp.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
** END NESTED EXCEPTION **
c30a7152000000e70000000000000000000000000028af1000020000000000000000000000000002147d14a1ffffffff0000ffffffff00000002144f00000000000000d31a7200000001000000e7002c000000e7002c ......... Z ( ;InnoDB: End of page dump
061130 16:43:08 InnoDB: Page checksum 3272241490, prior-to-4.0.14-form checksum 3220417626
InnoDB: stored checksum 3272241490, prior-to-4.0.14-form stored checksum 3220417626
InnoDB: Page lsn 0 2666256, low 4 bytes of lsn at page end 2666256
InnoDB: Page number (if stored to page already) 231,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
061130 16:43:08InnoDB: Assertion failure in thread 7084976 in file ../include/page0page.ic line 494
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=16777216
read_buffer_size=258048
max_used_connections=36
max_connections=100
threads_connected=35
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x8ff3e48
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x6bdc3c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8126bf0
0x68bdf8
0x82cabdd
0x8202df9
0x8202e99
0x81fb9c8
0x81acdb0
0x81a4489
0x815946f
0x8155306
Stack trace seems successful - bottom reached
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x9001d68 = insert into OPLOG (OPNAME,OPREALNAME,OPIP,OPTIME,OPDATA) values ('admin','admin','10.43.64.58',Now(),'操作对象：操作员:admin于2006-11-30从10.43.64.58登陆)')
thd->thread_id=46
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
Number of processes running now: 0
061130 16:43:08 mysqld restarted
061130 16:43:08 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
061130 16:43:08 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 2666256.
InnoDB: Doing recovery: scanned up to log sequence number 0 2666345
061130 16:43:08 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 10109, file name ./JSU-DCBI-bin.000004
061130 16:43:09 InnoDB: Flushing modified pages from the buffer pool...
061130 16:43:09 InnoDB: Started; log sequence number 0 2666345
/usr/sbin/mysqld: ready for connections.
Version: '4.1.14-standard-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
How to repeat:
when i executed update/insert sql,the problem appeared
Description: update SQL： insert into OPLOG (OPNAME,OPREALNAME,OPIP,OPTIME,OPDATA) values ('admin','admin','10.43.64.58',Now(),'0 502×÷0 90803ó0 5020 502×÷08±:admin07032006-11-300 70710.43.64.580 8050005)') com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.io.EOFException STACKTRACE: java.io.EOFException at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1902) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2348) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2858) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1570) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1665) at com.mysql.jdbc.Connection.execSQL(Connection.java:2972) at com.mysql.jdbc.Connection.execSQL(Connection.java:2902) at com.mysql.jdbc.Statement.execute(Statement.java:529) at server.database.DBAccess.exeUpdate(DBAccess.java:195) at server.database.DBoperatorstat.insert(DBoperatorstat.java:72) at server.implement.UserLoginImp.checkip(UserLoginImp.java:102) at server.implement.UserLoginImp.load(UserLoginImp.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.lang.Thread.run(Unknown Source) ** END NESTED EXCEPTION ** c30a7152000000e70000000000000000000000000028af1000020000000000000000000000000002147d14a1ffffffff0000ffffffff00000002144f00000000000000d31a7200000001000000e7002c000000e7002c ......... Z ( ;InnoDB: End of page dump 061130 16:43:08 InnoDB: Page checksum 3272241490, prior-to-4.0.14-form checksum 3220417626 InnoDB: stored checksum 3272241490, prior-to-4.0.14-form stored checksum 3220417626 InnoDB: Page lsn 0 2666256, low 4 bytes of lsn at page end 2666256 InnoDB: Page number (if stored to page already) 231, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be an update undo log page 061130 16:43:08InnoDB: Assertion failure in thread 7084976 in file ../include/page0page.ic line 494 InnoDB: Failing assertion: 0 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html InnoDB: about forcing recovery. mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=16777216 read_buffer_size=258048 max_used_connections=36 max_connections=100 threads_connected=35 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8ff3e48 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0x6bdc3c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8126bf0 0x68bdf8 0x82cabdd 0x8202df9 0x8202e99 0x81fb9c8 0x81acdb0 0x81a4489 0x815946f 0x8155306 Stack trace seems successful - bottom reached Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x9001d68 = insert into OPLOG (OPNAME,OPREALNAME,OPIP,OPTIME,OPDATA) values ('admin','admin','10.43.64.58',Now(),'操作对象：操作员:admin于2006-11-30从10.43.64.58登陆)') thd->thread_id=46 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 061130 16:43:08 mysqld restarted 061130 16:43:08 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 061130 16:43:08 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 2666256. InnoDB: Doing recovery: scanned up to log sequence number 0 2666345 061130 16:43:08 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 10109, file name ./JSU-DCBI-bin.000004 061130 16:43:09 InnoDB: Flushing modified pages from the buffer pool... 061130 16:43:09 InnoDB: Started; log sequence number 0 2666345 /usr/sbin/mysqld: ready for connections. Version: '4.1.14-standard-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) How to repeat: when i executed update/insert sql,the problem appeared