我在这个网站上读过这样的另一个问题,但我不知道如何解决这个问题。
Spring Integration: Application leaking SimpleAsyncTaskExecutor threads?
我的错误类似于以前的链接
SimpleAsyncTaskExecutor-2327" - Thread t@2405
java.lang.Thread.State: WAITING
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <7a224c1> (a java.util.concurrent.CountDownLatch$Sync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
at org.springframework.messaging.core.GenericMessagingTemplate$TemporaryReplyChannel.receive(GenericMessagingTemplate.java:199)
at org.springframework.messaging.core.GenericMessagingTemplate$TemporaryReplyChannel.receive(GenericMessagingTemplate.java:192)
at org.springframework.messaging.core.GenericMessagingTemplate.doReceive(GenericMessagingTemplate.java:130)
at org.springframework.messaging.core.GenericMessagingTemplate.doSendAndReceive(GenericMessagingTemplate.java:157)
at org.springframework.messaging.core.GenericMessagingTemplate.doSendAndReceive(GenericMessagingTemplate.java:45)
at org.springframework.messaging.core.AbstractMessagingTemplate.sendAndReceive(AbstractMessagingTemplate.java:42)
at org.springframework.integration.core.MessagingTemplate.sendAndReceive(MessagingTemplate.java:97)
at org.springframework.integration.core.MessagingTemplate.sendAndReceive(MessagingTemplate.java:38)
at org.springframework.messaging.core.AbstractMessagingTemplate.convertSendAndReceive(AbstractMessagingTemplate.java:79)
at org.springframework.messaging.core.AbstractMessagingTemplate.convertSendAndReceive(AbstractMessagingTemplate.java:70)
at org.springframework.integration.gateway.MessagingGatewaySupport.doSendAndReceive(MessagingGatewaySupport.java:449)
我正在使用
我的场景是下一个:我通过Api控制器收到一条消息,这条消息被发送到一个非TCP套接字。
我已经定义了MessageGateway接口
@MessagingGateway(defaultRequestChannel = "toTcp.input")
public interface MessageTcpGateway {
@Gateway
public ListenableFuture<Void> sendTcpChannel(byte[] data,
@Header("connectionId") String connectionId );
}
我在这样的服务类中使用此接口后:
public void sendMessageTcpGateway(final String bridgeId,final String connectionId, final byte[] message) {
LOGGER.debug("sendMessageTcpGateway connectionId:{} - message:{}", connectionId, message);
if (holder.existsConnection(connectionId)!=null) {
gatewayTcp.sendTcpChannel(message,connectionId);
} else {
LOGGER.error("Not send message connectionId:{} - message:{}", connectionId, message);
}
}
我想知道为什么不遵循那个SO线程的建议...... ListenableFuture<Void>
是你解决方案的瓶颈。正如您在堆栈跟踪中看到的那样,您有doSendAndReceive()
,但我猜您的目标解决方案实际上是单向的,并且不会为标头中的replyChannel
返回任何内容。
你应该考虑只有简单的void
返回类型和下游的ExecutorChannel
。
遗憾的是,我们无法从框架端检测到这种情况,因为网关方法的Future
返回类型表明您将执行请求 - 回复异步方式。在您的情况下,它只是一个异步请求,仅此而已。