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管理器队列的连接？

提前致谢， PM

Answer 1

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

您正在使用令人难以置信的旧版MQ Java客户端6.0.2.3 - IBM甚至不再支持它。您是否考虑过使用7.5.0.5客户端等更新的东西？更新，更新，有许多修复和增强。还值得注意的是，任何版本的MQ Java客户端都不支持Java 8，最新支持的是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）

Answer 2

我遇到了类似的问题，即通过OSGi容器（Karaf）中的Spring CachingConnectionFactory停止使用Camel路由消耗IBM MQ。解决方案是设置：

cachingConnectionFactory.setCacheConsumers(false);

如果这样做没有帮助，请尝试致电：

cachingConnectionFactory.resetConnection();

从某种应用程序的销毁方法中获取。

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

2 个答案: