linux - Spring CachingConnectionFactory 在 Linux 主机上的 Tomcat 关闭期间不关闭共享的 MQQueueConnection

Question

我有一个基于 spring-integration 4.0.x 的应用程序，它连接到 Websphere MQ 管理器以生成/使用 JMS 消息。该应用程序当前部署在 Tomcat 7.0.x 容器上，当在 Windows 主机上运行时，应用程序会在容器关闭时按预期停止，但在 RH6 Linux 主机上运行时，应用程序容器关闭时未能按预期停止。

查看基于 Linux 的关闭期间的跟踪级别日志记录，我可以看到应用程序在尝试关闭与 Websphere MQ 队列的 JMS 连接时卡住了:

15:24:30.628 [localhost-startStop-2] DEBUG org.springframework.beans.factory.support.DisposableBeanAdapter - Invoking destroy() on bean with name 'cachingConnectionFactory'
15:24:30.628 [localhost-startStop-2] DEBUG org.springframework.jms.connection.CachingConnectionFactory - Closing shared JMS Connection: com.ibm.mq.jms.MQQueueConnection@13909638

然后应用程序会在此时保持大约 15 分钟，直到记录以下内容:

15:40:24.247 [task-scheduler-1] TRACE org.springframework.jms.connection.CachingConnectionFactory - Logical close of cached JMS Session failed - discarding it
javax.jms.IllegalStateException: MQJMS1024: session closed
    at com.ibm.mq.jms.MQSession.checkSessionOpen(MQSession.java:2629) ~[com.ibm.mqjms-6.0.2.3.jar:6.0.2.3 - j600-203-080121  ]
    at com.ibm.mq.jms.MQSession.getTransacted(MQSession.java:1385) ~[com.ibm.mqjms-6.0.2.3.jar:6.0.2.3 - j600-203-080121  ]
    at org.springframework.jms.connection.CachingConnectionFactory$CachedSessionInvocationHandler.logicalClose(CachingConnectionFactory.java:457) ~[spring-jms-4.0.7.RELEASE.jar:4.0.7.RELEASE]
    at org.springframework.jms.connection.CachingConnectionFactory$CachedSessionInvocationHandler.invoke(CachingConnectionFactory.java:309) [spring-jms-4.0.7.RELEASE.jar:4.0.7.RELEASE]
    at com.sun.proxy.$Proxy92.close(Unknown Source) [?:?]
    at org.springframework.jms.support.JmsUtils.closeSession(JmsUtils.java:108) [spring-jms-4.0.7.RELEASE.jar:4.0.7.RELEASE]
    at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:497) [spring-jms-4.0.7.RELEASE.jar:4.0.7.RELEASE]
    at org.springframework.jms.core.JmsTemplate.receiveSelected(JmsTemplate.java:761) [spring-jms-4.0.7.RELEASE.jar:4.0.7.RELEASE]
    at org.springframework.integration.jms.JmsDestinationPollingSource.doReceiveJmsMessage(JmsDestinationPollingSource.java:122) [spring-integration-jms-4.0.4.RELEASE.jar:?]
    at org.springframework.integration.jms.JmsDestinationPollingSource.receive(JmsDestinationPollingSource.java:96) [spring-integration-jms-4.0.4.RELEASE.jar:?]
    at org.springframework.integration.endpoint.SourcePollingChannelAdapter.receiveMessage(SourcePollingChannelAdapter.java:144) [spring-integration-core-4.0.6.RELEASE.jar:?]
    at org.springframework.integration.endpoint.AbstractPollingEndpoint.doPoll(AbstractPollingEndpoint.java:192) [spring-integration-core-4.0.6.RELEASE.jar:?]
    at org.springframework.integration.endpoint.AbstractPollingEndpoint.access$000(AbstractPollingEndpoint.java:55) [spring-integration-core-4.0.6.RELEASE.jar:?]
    at org.springframework.integration.endpoint.AbstractPollingEndpoint$1.call(AbstractPollingEndpoint.java:149) [spring-integration-core-4.0.6.RELEASE.jar:?]
    at org.springframework.integration.endpoint.AbstractPollingEndpoint$1.call(AbstractPollingEndpoint.java:146) [spring-integration-core-4.0.6.RELEASE.jar:?]
    at org.springframework.integration.endpoint.AbstractPollingEndpoint$Poller$1.run(AbstractPollingEndpoint.java:298) [spring-integration-core-4.0.6.RELEASE.jar:?]
    at org.springframework.integration.util.ErrorHandlingTaskExecutor$1.run(ErrorHandlingTaskExecutor.java:52) [spring-integration-core-4.0.6.RELEASE.jar:?]
    at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:50) [spring-core-4.0.8.RELEASE.jar:4.0.8.RELEASE]
    at org.springframework.integration.util.ErrorHandlingTaskExecutor.execute(ErrorHandlingTaskExecutor.java:49) [spring-integration-core-4.0.6.RELEASE.jar:?]
    at org.springframework.integration.endpoint.AbstractPollingEndpoint$Poller.run(AbstractPollingEndpoint.java:292) [spring-integration-core-4.0.6.RELEASE.jar:?]
    at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) [spring-context-4.0.8.RELEASE.jar:4.0.8.RELEASE]
    at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81) [spring-context-4.0.8.RELEASE.jar:4.0.8.RELEASE]
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:1.8.0_25]
    at java.util.concurrent.FutureTask.run(Unknown Source) [?:1.8.0_25]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) [?:1.8.0_25]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [?:1.8.0_25]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_25]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_25]
    at java.lang.Thread.run(Unknown Source) [?:1.8.0_25]
15:40:24.257 [task-scheduler-1] DEBUG org.springframework.jms.connection.CachingConnectionFactory - Closing cached Session: com.ibm.mq.jms.MQQueueSession@6d33d604
15:40:24.258 [task-scheduler-1] DEBUG org.springframework.integration.endpoint.SourcePollingChannelAdapter - Poll interrupted - during stop()? : MQJMS1024: session closed; nested exception is javax.jms.IllegalStateException: MQJMS1024: session closed

我的应用程序使用以下堆栈运行:

java 8

com.ibm:com.ibm.mq:6.0.2.3
com.ibm:com.ibm.mqjms:6.0.2.3
javax.jms:jms:1.1
org.springframework.integration:spring-integration-core:4.0.6.RELEASE
org.springframework.integration:spring-integration-java-dsl:1.0.1.RELEASE
org.springframework.integration:spring-integration-jms:4.0.4.RELEASE

我的应用程序的 JMS 配置显示在这里:

@Configuration
@ComponentScan
public class JmsConfig {

    @Autowired
    private Properties jndiProperties;
    
    private ConnectionFactory mqConnectionFactory() throws NamingException {
        
        Context ctx = new InitialContext(jndiProperties);
        
        try {
            MQQueueConnectionFactory connectionFactory = (MQQueueConnectionFactory)
                ctx.lookup("jms/service/SERVICE_QCF");
        
            return connectionFactory;
            
        } finally {
            ctx.close();
        }   
    }
    
    @Bean
    public CachingConnectionFactory cachingConnectionFactory() throws NamingException {
        CachingConnectionFactory connectionFactory = new CachingConnectionFactory();
        connectionFactory.setTargetConnectionFactory(mqConnectionFactory());
        connectionFactory.setCacheConsumers(false);
        return connectionFactory;
    }
}

此处部分显示了我的应用程序的集成配置:

@Configuration
@EnableIntegration
public class IntegrationConfig {

    ...

    @Autowired
    private CachingConnectionFactory cachingConnectionFactory;

    @Bean
    public IntegrationFlow requestFlow() {
    
        return IntegrationFlows
            .from("request.ch")
            .handle(Jms.outboundAdapter(cachingConnectionFactory)
                    .destination("REQUEST_QUEUE")).get();
    }

    @Bean
    public IntegrationFlow responseFlow() {

        return IntegrationFlows
                   .from(Jms.inboundAdapter(cachingConnectionFactory).destination(
                        "RESPONSE_QUEUE"),
                        c -> c.poller(Pollers.fixedRate(1000).maxMessagesPerPoll(10)))
                  .channel("response.ch")
                .get();
    }

    ...
}

如何确保在应用程序停止/关闭时正确关闭与 MQ 管理器队列的连接？

提前致谢，下午

Answer 1

重新发布我的评论作为答案...

您使用的是非常旧的 MQ Java 客户端版本 6.0.2.3 - IBM 甚至不再支持它。您是否考虑过使用更新的软件，例如 7.5.0.5 客户端？更新很多，其中有许多修复和增强功能。另外值得注意的是，Java 8 不受任何版本的 MQ Java 客户端支持，支持的最新版本是 Java 7。

IBM 在此处免费提供其 7.5 个客户端:http://www-01.ibm.com/support/docview.wss?uid=swg24032744

MQ 的设计使得所有版本的客户端都可以与所有版本的队列管理器一起工作。因此，将 7.5 客户端与 6.0 队列管理器或任何其他组合一起使用肯定不是问题。

我确信 IBM 会在某个时候宣布通过 IBM MQ 支持 Java 8，但据我所知，目前还没有公开任何日期。您可以在此处请求支持(和功能增强):https://www.ibm.com/developerworks/rfe/

在您的案例中，可能值得为 IBM MQ 上的 Java 8 提交 RFE。 (注意:在 RFE 页面上它仍然被称为 WebSphere MQ)