您好，服务器使用了1个月时间，今天突然发现页面打不开，然后登陆服务器发现16G的内从都用满了，服务器只启动了mysql nginx tomcat 请问咱们的程序发生过类似的情况吗？求知道

我们自己演示站部署的服务器内存没你那么大都不会出现内存占满的事，你服务器被入侵了吧

您好，服务器使用了1个月时间，今天突然发现页面打不开，然后登陆服务器发现16G的内从都用满了，服务器只启动了mysql nginx tomcat

请问咱们的程序发生过类似的情况吗？求知道

没有呢，服务器内存用满了肯定是您内存不够用了，你是不是同时启动了多个项目

好吧。我再看一段时间 谢谢

我也出现类似的情况，放在阿里云上，隔一段时间CPU达到160%多，内存占满，还不会回落，然后重启又好了，日志也不报错，这样子怎么用啊，目前这个系统还只有我一个人用，后面商业咋办啊，总不能出现问题就重启吧

我也出现类似的情况，放在阿里云上，隔一段时间CPU达到160%多，内存占满，还不会回落，然后重启又好了，日志也不报错，这样子怎么用啊，目前这个系统还只有我一个人用，后面商业咋办啊，总不能出现问题就重启吧

我也出现类似的情况，放在阿里云上，隔一段时间CPU达到160%多，内存占满，还不会回落，然后重启又好了，日志也不报错，这样子怎么用啊，目前这个系统还只有我一个人用，后面商业咋办啊，总不能出现问题就重启吧

 您是不是服务器内存不够，可以加大下你服务器的内存试试

管理好，我最近看了看，还是内存一直增长，直到用满，
我看日志，有个异常，我复制出来了，这个是在运行中报的，还没满的时候，能帮忙看一样，这个异常正常吗


10:53:45.371 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - Checking for expired resources - Wed Jul 29 10:53:45 CST 2015 [com.mchange.v2.resourcepool.BasicResourcePool@65e73498]
10:53:45.371 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool@65e73498]
10:53:45.371 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - EXPIRED idle resource: com.mchange.v2.c3p0.impl.NewPooledConnection@6358f7f6 ---> idle_time: 7649992; max_idle_time: 7200000 [com.mchange.v2.resourcepool.BasicResourcePool@65e73498]
10:53:45.371 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - Removing expired resource: com.mchange.v2.c3p0.impl.NewPooledConnection@6358f7f6 [com.mchange.v2.resourcepool.BasicResourcePool@65e73498]
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - trace com.mchange.v2.resourcepool.BasicResourcePool@65e73498 [managed: 19, unused: 19, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@41692a49)
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - trace com.mchange.v2.resourcepool.BasicResourcePool@65e73498 [managed: 19, unused: 19, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@41692a49)
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - Preparing to destroy resource: com.mchange.v2.c3p0.impl.NewPooledConnection@6358f7f6
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - EXPIRED idle resource: com.mchange.v2.c3p0.impl.NewPooledConnection@518a9d3c ---> idle_time: 7649993; max_idle_time: 7200000 [com.mchange.v2.resourcepool.BasicResourcePool@65e73498]
10:53:45.372 DEBUG com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool - Preparing to destroy PooledConnection: com.mchange.v2.c3p0.impl.NewPooledConnection@6358f7f6
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - Removing expired resource: com.mchange.v2.c3p0.impl.NewPooledConnection@518a9d3c [com.mchange.v2.resourcepool.BasicResourcePool@65e73498]
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - trace com.mchange.v2.resourcepool.BasicResourcePool@65e73498 [managed: 18, unused: 18, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@41692a49)
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - trace com.mchange.v2.resourcepool.BasicResourcePool@65e73498 [managed: 18, unused: 18, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@41692a49)
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - Preparing to destroy resource: com.mchange.v2.c3p0.impl.NewPooledConnection@518a9d3c
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - EXPIRED idle resource: com.mchange.v2.c3p0.impl.NewPooledConnection@a166591 ---> idle_time: 7649993; max_idle_time: 7200000 [com.mchange.v2.resourcepool.BasicResourcePool@65e73498]
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - Removing expired resource: com.mchange.v2.c3p0.impl.NewPooledConnection@a166591 [com.mchange.v2.resourcepool.BasicResourcePool@65e73498]
10:53:45.372 DEBUG com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool - Preparing to destroy PooledConnection: com.mchange.v2.c3p0.impl.NewPooledConnection@518a9d3c
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - Preparing to destroy resource: com.mchange.v2.c3p0.impl.NewPooledConnection@a166591
10:53:45.372 DEBUG com.mchange.v2.c3p0.impl.NewPooledConnection - com.mchange.v2.c3p0.impl.NewPooledConnection@6358f7f6 closed by a client.
java.lang.Exception: DEBUG -- CLOSE BY CLIENT STACK TRACE
        at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:566) [c3p0-0.9.1.2.jar:0.9.1.2]
        at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:234) [c3p0-0.9.1.2.jar:0.9.1.2]
        at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.destroyResource(C3P0PooledConnectionPool.java:470) [c3p0-0.9.1.2.jar:0.9.1.2]
        at com.mchange.v2.resourcepool.BasicResourcePool$1DestroyResourceTask.run(BasicResourcePool.java:964) [c3p0-0.9.1.2.jar:0.9.1.2]
        at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) [c3p0-0.9.1.2.jar:0.9.1.2]
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - trace com.mchange.v2.resourcepool.BasicResourcePool@65e73498 [managed: 17, unused: 17, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@41692a49)
10:53:45.372 DEBUG com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool - Successfully destroyed PooledConnection: com.mchange.v2.c3p0.impl.NewPooledConnection@6358f7f6
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - Successfully destroyed resource: com.mchange.v2.c3p0.impl.NewPooledConnection@6358f7f6
10:53:45.372 DEBUG com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool - Preparing to destroy PooledConnection: com.mchange.v2.c3p0.impl.NewPooledConnection@a166591
10:53:45.372 DEBUG com.mchange.v2.resourcepool.BasicResourcePool - trace com.mchange.v2.resourcepool.BasicResourcePool@65e73498 [managed: 17, unused: 17, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@41692a49)
10:53:45.373 DEBUG com.mchange.v2.c3p0.impl.NewPooledConnection - com.mchange.v2.c3p0.impl.NewPooledConnection@518a9d3c closed by a client.
java.lang.Exception: DEBUG -- CLOSE BY CLIENT STACK TRACE

你服务器上有别的项目吗，我们服务器上部署了几个我们自己的产品都没出现过这种问题，建议优化下服务器