was 线程挂起 已保持活…

[15-1-30 16:32:17:797 CST] 00000003ThreadMonitor W   WSVR0605W: 线程“WebContainer :26”（0000029f）已保持活动状态 685090 毫秒，此线程可能已挂起。在服务器中共有 25个线程可能处于挂起状态。

at sun.misc.Unsafe.park(NativeMethod)

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

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

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

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

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

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

atorg.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:66)

atorg.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)

atorg.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1275)

atorg.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1269)

atorg.apache.activemq.ActiveMQSession.(ActiveMQSession.java:252)

atorg.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:317)

atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod)

atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)

atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

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

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

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

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

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

atcom.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)

atcom.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)

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

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

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

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

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

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

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

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

atcom.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)

atcom.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)

atcom.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)

atcom.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)

atcom.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)

 

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

从日志看，线程挂起在获取数据源连接的地方。问题可能是由于集群环境下获取数据源出现死锁，从而导致资源无法释放，最终线程池被耗尽，线程挂起。 最后只能重启WAS服务。

这个问题的解决办法是：在数据源里面增加一个参数 useRRASetEquals 设置为 true

添加路径：

       资源 ->JDBC -> XXX数据源->定制属性 -> 新建

增加参数： useRRASetEquals ，值为 true, 类型为 java.lang.Boolean

这个参数应该是WAS7新加的，因为加这个参数有版本要求，必须是 7.0.0.13 之后的版本，否则会报错。