求助 Tomcat查询数据导致Mysql服务崩溃

求助 Tomcat查询数据导致Mysql服务崩溃,网站是tomcat服务,查询数据时导致数据库崩溃,求解。
崩溃日志:

14:24:44 UTC - mysqld got exception 0xc000001d ;
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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=72
max_threads=2000
thread_count=72
connection_count=72
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 800567 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x294987bbe40
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...
7ffc8c3a5c01    MSVCR120.dll!pow()
7ff6498049ea    mysqld.exe!get_sweep_read_cost()[handler.cc:7272]
7ff649dc0737    mysqld.exe!ror_intersect_add()[opt_range.cc:5473]
7ff649db6569    mysqld.exe!get_best_ror_intersect()[opt_range.cc:5654]
7ff649dc2a25    mysqld.exe!test_quick_select()[opt_range.cc:3120]
7ff64996ace3    mysqld.exe!get_quick_record_count()[sql_optimizer.cc:5963]
7ff6499696dd    mysqld.exe!JOIN::estimate_rowcount()[sql_optimizer.cc:5709]
7ff64996c439    mysqld.exe!JOIN::make_join_plan()[sql_optimizer.cc:5066]
7ff64996dfcb    mysqld.exe!JOIN::optimize()[sql_optimizer.cc:368]
7ff6499c15c9    mysqld.exe!st_select_lex::optimize()[sql_select.cc:1009]
7ff6499bf5dd    mysqld.exe!handle_query()[sql_select.cc:164]
7ff649826227    mysqld.exe!execute_sqlcom_select()[sql_parse.cc:5144]
7ff649828186    mysqld.exe!mysql_execute_command()[sql_parse.cc:2816]
7ff64982bb68    mysqld.exe!mysql_parse()[sql_parse.cc:5576]
7ff649824cf3    mysqld.exe!dispatch_command()[sql_parse.cc:1487]
7ff649825c9a    mysqld.exe!do_command()[sql_parse.cc:1027]
7ff6497e91cc    mysqld.exe!handle_connection()[connection_handler_per_thread.cc:306]
7ff64a232732    mysqld.exe!pfs_spawn_thread()[pfs.cc:2193]
7ff649f4326c    mysqld.exe!win_thread_start()[my_thread.c:38]
7ffc8c334f7f    MSVCR120.dll!_beginthreadex()
7ffc8c335126    MSVCR120.dll!_endthreadex()
7ffc9b1184d4    KERNEL32.DLL!BaseThreadInitThunk()
7ffc9d9ae851    ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (29498a921a0): select subsysuser0_.ID as ID1_47_, subsysuser0_.CTIME as CTIME2_47_, subsysuser0_.CUSER as CUSER3_47_, subsysuser0_.LOGINNAME as LOGINNAM4_47_, subsysuser0_.SYSID as SYSID5_47_, subsysuser0_.USERID as USERID6_47_ from wuc_subsys_user subsysuser0_ where subsysuser0_.SYSID='40288107900fa35e01900fa905d50002' and subsysuser0_.USERID='4028810790c482540190dd89b9980423'
Connection ID (thread ID): 71
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.

网站500报错:

HTTP Status 500 – Internal Server Error


Type 异常报告
消息 Could not open Hibernate Session for transaction; nested exception is org.hibernate.TransactionException: JDBC begin transaction failed:
描述 服务器遇到一个意外的情况,阻止它完成请求。

生产环境吗,还是自己玩的

嗯,生产环境

数据库现在是崩了吗?还是就这个SQL报错了

一些较大量的数据查询会导致crash

数据库给了多少内存

看报错要调大点

配置挺大的 比较奇怪,配置如下:

[client]
port		= 3306
socket		= MySQL
default-character-set = utf8
user=root
password=**********

[mysqld]
max_connections=1000
thread_cache_size=100
port		= 3399
socket		= MySQL
skip-external-locking
key_buffer_size = 64M
max_allowed_packet = 64M
table_open_cache = 1000
sort_buffer_size = 4M
net_buffer_length = 32K
read_buffer_size = 4M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 128M
log-bin=mysql-bin
binlog_format=mixed
server-id	= 1
character_set_server = utf8
query_cache_size = 128M
query_cache_type = 1

# InnoDB settings for high-performance and large memory usage
innodb_buffer_pool_size = 16G
innodb_log_file_size = 1G
innodb_flush_log_at_trx_commit = 2
innodb_io_capacity = 4000
innodb_io_capacity_max = 8000
# innodb_flush_method = O_DIRECT
innodb_buffer_pool_instances = 16

[mysqldump]
quick
max_allowed_packet = 64M

[mysql]
no-auto-rehash

[myisamchk]
key_buffer_size = 128M
sort_buffer_size = 128M
read_buffer = 8M
write_buffer = 8M

[mysqlhotcopy]
interactive-timeout

改不了語句要麼存儲過程,這種一般靠cpu,特別是單核性能

看看这个报错里面的

select subsysuser0_.ID as ID1_47_, subsysuser0_.CTIME as CTIME2_47_, subsysuser0_.CUSER as CUSER3_47_, subsysuser0_.LOGINNAME as LOGINNAM4_47_, subsysuser0_.SYSID as SYSID5_47_, subsysuser0_.USERID as USERID6_47_ from wuc_subsys_user subsysuser0_ where subsysuser0_.SYSID=‘40288107900fa35e01900fa905d50002’ and subsysuser0_.USERID=‘4028810790c482540190dd89b9980423’
这是那个报错的SQL吗

大佬 具体需要改哪个配置参数呢 还请解答
主机是16h32g的

是的 是这个查询语句

调整这个里面的现在你的配置是
64 + (4 + 4)*32
最好现在测试环境复测一下

我没咋用过MYSQL看这个报错是这样的,你要在测试环境测试一下,生产环境要备份数据

这个SQL会有多少条记录了

好的 我测试下 十分感谢 :pray:

不多 少于100条

那不应该啊是表的数据量很大吗

就这么一个单表的查询还会这样吗?连关联都没有