was 線程掛起

[15-1-30 16:32:17:797 CST] 00000003 ThreadMonitor W   WSVR0605W: 線程“WebContainer : 26”(0000029f)已保持活動狀態 685090 毫秒,此線程可能已掛起。在服務器中共有 25 個線程可能處於掛起狀態。

at sun.misc.Unsafe.park(Native Method)

at java.util.concurrent.locks.LockSupport.park(LockSupport.java:184)

at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:822)

at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:853)

at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1189)

at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:197)

at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:273)

at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:66)

at org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)

at org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1275)

at org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1269)

at org.apache.activemq.ActiveMQSession.(ActiveMQSession.java:252)

at org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:317)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

at java.lang.reflect.Method.invoke(Method.java:611)



at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)

at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179)

at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3935)

at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)

at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)

at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)

at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)

at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)

at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)

at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)

at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)

at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)

at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)

at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)

at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)



at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)

從日誌看,線程掛起在獲取數據源連接的地方。問題可能是由於集羣環境下獲取數據源出現死鎖,從而導致資源無法釋放,最終線程池被耗盡,線程掛起。 最後只能重啓WAS服務。

這個問題的解決辦法是:在數據源裏面增加一個參數 useRRASetEquals 設置爲 true

添加路徑:

       資源 -> JDBC -> XXX數據源->定製屬性 -> 新建

增加參數: useRRASetEquals ,值爲 true , 類型爲 java.lang.Boolean

這個參數應該是WAS7新加的,因爲加這個參數有版本要求,必須是 7.0.0.13 之後的版本,否則會報錯。

發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章