【IT168技术文档】项目组反应数据库有问题，

　　检查发现sga还用的默认参数，缓冲区命中率很低。根据系统内存调整后，好像系统正常了。数据库调整就算是结束了

　　一天后，我再登这个数据库的时候，发现一个提示说线程已经超过限制，不允许再登录。然后我去修改了process到250，增加并发连接数。然后重启了数据库。当天没发生什么事情，第二天，发现250又被撑满了，这个时候，我就开始换衣中间件有问题，登入中间件那边看了下日志，一直报错，提示无法打开新的连接。一般来说，中间件连接数据库能开10个都算可以了。至少websphere是这样，weblogic应该差不多。然后修改了一下，调整了weblogic的连接池，修改最大连接到100.

　　1、 报错信息

　　<2008-4-22 上午04时33分18秒 CST>

　　hread: '1' for queue: 'weblogic.kernel.Default' has been busy for "102" seconds

　　working on the request "Http Request: /guestAction.jsp", which is more than the

　　configured time (StuckThreadMaxTime) of "60" seconds.>

　　<2008-4-22 上午04时33分18秒 CST>

　　hread: '7' for queue: 'weblogic.kernel.Default' has been busy for "178" seconds

　　working on the request "Http Request: /guestAction.jsp", which is more than the

　　configured time (StuckThreadMaxTime) of "60" seconds.>

　　<2008-4-22 上午04时34分18秒 CST>

　　hread: '0' for queue: 'weblogic.kernel.Default' has been busy for "111" seconds

　　working on the request "Http Request: /guestAction.jsp", which is more than the

　　configured time (StuckThreadMaxTime) of "60" seconds.>

　　<2008-4-22 上午04时34分18秒 CST>

　　hread: '1' for queue: 'weblogic.kernel.Default' has been busy for "162" seconds

　　working on the request "Http Request: /guestAction.jsp", which is more than the

　　configured time (StuckThreadMaxTime) of "60" seconds.>

　　<2008-4-22 上午04时35分18秒 CST>

　　hread: '0' for queue: 'weblogic.kernel.Default' has been busy for "171" seconds

　　working on the request "Http Request: /guestAction.jsp", which is more than the

　　configured time (StuckThreadMaxTime) of "60" seconds.>

　　<2008-4-22 上午04时35分18秒 CST>

　　hread: '12' for queue: 'weblogic.kernel.Default' has been busy for "111" seconds

　　working on the request "Http Request: /guestAction.jsp", which is more than the

　　configured time (StuckThreadMaxTime) of "60" seconds.>

　　<2008-4-22 上午04时36分18秒 CST>

　　hread: '12' for queue: 'weblogic.kernel.Default' has been busy for "171" seconds

　　working on the request "Http Request: /guestAction.jsp", which is more than the

　　configured time (StuckThreadMaxTime) of "60" seconds.>

　　2、判断　可能存在部分sql语句未优化，造成执行时间过长(request超时)造成挂死