mysql的报错，请高手帮忙指出问题

[zcxill]

最近在测试程序的数据库时间运行的稳定性，发现经常出现mysql自动关闭。（因为顺带做压力测试，所以数据操作比较频繁，但是用得是tomcat mysql线程池）
报错1：
120801 23:29:01 - mysqld got exception 0xc0000005 ;
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=67108864
read_buffer_size=4194304
max_used_connections=1
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1303623 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x6c7faed8
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...
015D1F66

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (6C7DFE10): insert into CurrentFeatureUsage(featureID,updateTime,used,borrowed) values(742,'2012-08-01 23:25:07',0,0)
Connection ID (thread ID): 2
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.


报错2


120806 23:21:16 - mysqld got exception 0xc0000005 ;
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=67108864
read_buffer_size=4194304
max_used_connections=1
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1303623 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x9ebad20
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...
01321F66

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (6C86E788): update Feature set expireDate = '1970-01-01 00:00:00' , featureVersion = '3.0' where featureNameID = 188
Connection ID (thread ID): 2
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

[rucypli]

This could be because you hit a bug

[rczjp]

连接开启和关闭是正常的，操作太频繁所以会造成中断，处理不过来。
使用
1、back_log=500
2、使用持久连接mysql_pconnect（针对程序）

[zcxill]

肯定不是BUG，应该我查了相关资料，说5.1以上版本就不存在这个BUG了。而我的5.5版本
[Quote=引用 1 楼 的回复:]

This could be because you hit a bug
[/Quote]

[zcxill]

我已经用tomcat 的mysql连接池了，应该不存在数据库连接频繁处理不过来。所以你的猜测的方向应该是不对的。
[Quote=引用 2 楼 的回复:]

连接开启和关闭是正常的，操作太频繁所以会造成中断，处理不过来。
使用
1、back_log=500
2、使用持久连接mysql_pconnect（针对程序）
[/Quote]

[火雲邪神]

oh , 仆街了