jboss+mysql安装在windows 2008上的怪问题

[aljoin79]

操作系统是windows 2008 ，jboss4.0.2 mysql5.0.54
运行一段时间后jboss就报错，报错后服务器的ie就不能打开baidu，sina等，就连qq也不能用，搞的向有安全控制一样，但是客户还是能访问到服务器上，哪位有遇到这样的问题吗
请大家看看是怎么回事怎么解决，对了在windows 2003上是没有这个问题的
下面是jboss报错的信息

1：
com.mchange.v2.log.log4j.Log4jMLog$Log4jMLogger.log(Log4jMLog.ja
va:161)
com.mchange.v2.log.log4j.Log4jMLog$Log4jMLogger.log(Log4jMLog.ja
va:173)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(Ba
sicResourcePool.java:1841)
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run
(ThreadPoolAsynchronousRunner.java:547)
19:59:57,894 INFO [STDOUT] 2013-05-09 19:59:57,894 WARN [Timer-5] (ThreadPoolA
synchronousRunner.java:60 - com.mchange.v2.async.ThreadPoolAsynchronousRunner$
DeadlockDetector@1424afd -- APPARENT DEADLOCK!!! Creating emergency threads for
unassigned pending tasks!
19:59:57,894 INFO [STDOUT] 2013-05-09 19:59:57,894 WARN [Timer-5] (ThreadPoolA
synchronousRunner.java:624) - com.mchange.v2.async.ThreadPoolAsynchronousRunner$
DeadlockDetector@1424afd -- APPARENT DEADLOCK!!! Complete Status:
Managed Threads: 3
Active Threads: 3
Active Tasks:
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@10e08e
1 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@68ed58
(com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@b633cc
(com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1)
Pending Tasks:
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@29b92
Pool thread stack traces:
Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2,5
,jboss]
java.lang.Thread.sleep(Native Method)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(Ba
sicResourcePool.java:1805)
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run
(ThreadPoolAsynchronousRunner.java:547)
Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0,5
,jboss]
java.lang.Thread.sleep(Native Method)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(Ba
sicResourcePool.java:1805)
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run
(ThreadPoolAsynchronousRunner.java:547)
Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1,5
,jboss]
java.lang.Thread.sleep(Native Method)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(Ba
sicResourcePool.java:1805)
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run
(ThreadPoolAsynchronousRunner.java:547)

由于滚动的太快只复制了这些信息

[zoeg]

这种问题，光看你这么一小角的信息是解决不了的勒！ 不过就你描述的影响到服务器的网络应用程序的话，你可以用命令netstat -an看看端口占用情况，我估计是临时端口用完了！默认的临时端口是1024-5000 你所谓2003没问题可能是那台2003的机器有人改过临时端口范围！

[zoeg]

临时端口是作为客户端往外连接的时候用的，不是说你监听的端口 偶尔出现就更能说明可能是临时端口耗尽，4000个不到的临时端口范围，如果都是连向同一个目标地址，还要加上两分钟的重用限制！

[aljoin79]

因为出现这个问题是随机的，没有固定的时间 我用过的端口8080、8090、8089、58等，结果都是一样 2003的机器是也是新安装的，部署后一直运行，没动过

[aljoin79]

那怎么修改临时端口的范围，谢谢指教

[aljoin79]

这是windows 2008正常情况下的端口信息，如果要不正常的大概要2-3天才会出现 C:\Users\Administrator>netstat -an 活动连接 协议 本地地址 外部地址 状态 TCP 0.0.0.0:80 0.0.0.0:0 LISTENING TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:445 0.0.0.0:0 LISTENING TCP 0.0.0.0:1039 0.0.0.0:0 LISTENING TCP 0.0.0.0:1947 0.0.0.0:0 LISTENING TCP 0.0.0.0:2383 0.0.0.0:0 LISTENING TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING TCP 0.0.0.0:49160 0.0.0.0:0 LISTENING TCP 127.0.0.1:1434 0.0.0.0:0 LISTENING TCP 192.168.0.114:139 0.0.0.0:0 LISTENING TCP 192.168.0.114:3389 192.168.0.55:50931 ESTABLISHED TCP [::]:80 [::]:0 LISTENING TCP [::]:135 [::]:0 LISTENING TCP [::]:445 [::]:0 LISTENING TCP [::]:1039 [::]:0 LISTENING TCP [::]:1947 [::]:0 LISTENING TCP [::]:2383 [::]:0 LISTENING TCP [::]:3389 [::]:0 LISTENING TCP [::]:49152 [::]:0 LISTENING TCP [::]:49153 [::]:0 LISTENING TCP [::]:49154 [::]:0 LISTENING TCP [::]:49155 [::]:0 LISTENING TCP [::]:49160 [::]:0 LISTENING TCP [::1]:1434 [::]:0 LISTENING UDP 0.0.0.0:123 *:* UDP 0.0.0.0:500 *:* UDP 0.0.0.0:1947 *:* UDP 0.0.0.0:3600 *:* UDP 0.0.0.0:4500 *:* UDP 0.0.0.0:5355 *:* UDP 0.0.0.0:54465 *:* UDP 0.0.0.0:54986 *:* UDP 0.0.0.0:59112 *:* UDP 127.0.0.1:54146 *:* UDP 127.0.0.1:60226 *:* UDP 192.168.0.114:137 *:* UDP 192.168.0.114:138 *:* UDP [::]:123 *:* UDP [::]:500 *:* UDP [::]:1947 *:* UDP [::]:5355 *:*