急求關(guān)于mysql數(shù)據(jù)庫自動(dòng)停止的問題

數(shù)據(jù)庫：mysql5.6.17 os: 2008server 32位

業(yè)務(wù)正在運(yùn)行，突然數(shù)據(jù)庫就自動(dòng)停止服務(wù)了，日志如下：
2016-12-03 11:14:06 4860 [ERROR] Can’t create thread to handle request (errno= 12)
2016-12-03 11:15:25 4860 [ERROR] InnoDB: InnoDB: Unable to allocate memory of size 1065016.

2016-12-03 11:15:25 1398 InnoDB: Assertion failure in thread 5016 in file ha_innodb.cc line 17080
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/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2016-12-03 11:15:39 4860 [ERROR] Error log throttle: 7 ‘Can’t create thread to handle new connection’ error(s) suppressed
2016-12-03 11:15:39 4860 [ERROR] Can’t create thread to handle request (errno= 12)
2016-12-03 11:16:40 4860 [ERROR] Error log throttle: 963 ‘Can’t create thread to handle new connection’ error(s) suppressed
2016-12-03 11:16:40 4860 [ERROR] Can’t create thread to handle request (errno= 12)
2016-12-03 11:18:00 5108 [Note] Plugin ‘FEDERATED’ is disabled.
2016-12-03 11:18:00 171c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB’s internal memory allocator.
2016-12-03 11:18:00 5108 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-12-03 11:18:00 5108 [Note] InnoDB: The InnoDB memory heap is disabled
2016-12-03 11:18:00 5108 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-12-03 11:18:00 5108 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-12-03 11:18:00 5108 [Note] InnoDB: Not using CPU crc32 instructions
2016-12-03 11:18:00 5108 [Note] InnoDB: Initializing buffer pool, size = 823.0M
2016-12-03 11:18:00 5108 [Note] InnoDB: Completed initialization of buffer pool
2016-12-03 11:18:00 5108 [Note] InnoDB: Highest supported file format is Barracuda.
2016-12-03 11:18:00 5108 [Note] InnoDB: Log scan progressed past the checkpoint lsn 37892781681
2016-12-03 11:18:00 5108 [Note] InnoDB: Database was not shutdown normally!
2016-12-03 11:18:00 5108 [Note] InnoDB: Starting crash recovery.
2016-12-03 11:18:00 5108 [Note] InnoDB: Reading tablespace information from the .ibd files…
2016-12-03 11:18:04 5108 [Note] InnoDB: Restoring possible half-written data pages
2016-12-03 11:18:04 5108 [Note] InnoDB: from the doublewrite buffer…
InnoDB: Doing recovery: scanned up to log sequence number 37893927335
InnoDB: 6 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 63 row operations to undo
InnoDB: Trx id counter is 12591616
2016-12-03 11:18:05 5108 [Note] InnoDB: Starting an apply batch of log records to the database…
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 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
2016-12-03 11:18:06 5108 [Note] InnoDB: 128 rollback segment(s) are active.
InnoDB: Starting in background the rollback of uncommitted transactions

我掛了五個(gè)tomcat搭載了nginx 。大約有100個(gè)客戶端會(huì)頻繁訪問。想著應(yīng)該沒問題，但是連續(xù)兩天數(shù)據(jù)庫突然停止，急求大神幫忙解決，謝謝！