在ActiveMQ jmsActivationSpec未触发的情况下打开Liberty JMS

Question

我正在尝试使用activeMq作为具有开放自由的JMS的代理。我设法在队列中获取消息，但我的激活规范从未触发。我在日志中读到了以下内容。

[25/07/20 18:13:51:857 CEST] 00000330 com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime           I CNTR0180I: The FailedKalenderUpdateProcessor message-driven bean in the typedagkalender-backend.jar module of the typedagkalender-ear application is bound to the jms/typedagkalender/kalenderupdates/dlqueueAS activation specification.
[25/07/20 18:13:51:857 CEST] 00000330 com.ibm.ws.jca.cm.ConnectorService                           I J2CA8050I: An authentication alias should be used instead of defining a user name and password on jms/typedagkalender/kalenderupdates/dlqueueAS.
[25/07/20 18:13:51:858 CEST] 00000330 SystemOut                                                    O 2020-07-25 18:13:51,858 [utor-thread-692] INFO  ActiveMQEndpointWorker         - Starting
[25/07/20 18:13:51:858 CEST] 00000330 com.ibm.ws.jca.service.EndpointActivationService             I J2CA8801I: The message endpoint for activation specification jms/typedagkalender/kalenderupdates/dlqueueAS and message driven bean application typedagkalender-ear#typedagkalender-backend.jar#FailedKalenderUpdateProcessor is activated.
[25/07/20 18:13:51:858 CEST] 00000330 com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime           I CNTR0180I: The KalenderUpdateProcessor message-driven bean in the typedagkalender-backend.jar module of the typedagkalender-ear application is bound to the jms/typedagkalender/kalenderupdates/queueAS activation specification.
[25/07/20 18:13:51:858 CEST] 000002cb SystemOut                                                    O 2020-07-25 18:13:51,858 [utor-thread-591] INFO  ActiveMQEndpointWorker         - Establishing connection to broker [tcp://localhost:61616]
[25/07/20 18:13:51:858 CEST] 00000330 com.ibm.ws.jca.cm.ConnectorService                           I J2CA8050I: An authentication alias should be used instead of defining a user name and password on jms/typedagkalender/kalenderupdates/queueAS.
[25/07/20 18:13:51:860 CEST] 00000330 SystemOut                                                    O 2020-07-25 18:13:51,859 [utor-thread-692] INFO  ActiveMQEndpointWorker         - Starting
[25/07/20 18:13:51:860 CEST] 00000330 com.ibm.ws.jca.service.EndpointActivationService             I J2CA8801I: The message endpoint for activation specification jms/typedagkalender/kalenderupdates/queueAS and message driven bean application typedagkalender-ear#typedagkalender-backend.jar#KalenderUpdateProcessor is activated.
[25/07/20 18:13:51:860 CEST] 0000032b SystemOut                                                    O 2020-07-25 18:13:51,860 [utor-thread-687] INFO  ActiveMQEndpointWorker         - Establishing connection to broker [tcp://localhost:61616]
[25/07/20 18:13:51:870 CEST] 000002cb SystemOut                                                    O 2020-07-25 18:13:51,870 [utor-thread-591] INFO  ActiveMQEndpointWorker         - Successfully established connection to broker [tcp://localhost:61616]
[25/07/20 18:13:51:871 CEST] 0000032b SystemOut                                                    O 2020-07-25 18:13:51,870 [utor-thread-687] INFO  ActiveMQEndpointWorker         - Successfully established connection to broker [tcp://localhost:61616]

这是我的server.xml配置jms部分

<?xml version="1.0" encoding="UTF-8"?>
<server>
    <!-- JMS CONFIGURATION -->
    <resourceAdapter id="ActiveMQResourceAdapter" location="${server.config.dir}/resources/lib/resource-adapter/activemq-rar-5.16.0.rar">
      <properties.activemq ServerUrl="tcp://localhost:61616" />
    </resourceAdapter>

    <messagingEngine>
        <queue id="Typedagkalender_destination" />
        <queue id="_SYSTEM.Exception.Destination" />
    </messagingEngine>

    <jmsQueueConnectionFactory jndiName="jms/typedagkalender/kalenderupdates/queueCF" connectionManagerRef="ConMgr">
        <properties.ActiveMQResourceAdapter />
    </jmsQueueConnectionFactory> -->

    <connectionManager id="ConMgr" maxPoolSize="${jms.ConMgr.maxPoolSize}" />

    <jmsQueue id="jms/typedagkalender/kalenderupdates/queue" jndiName="jms/typedagkalender/kalenderupdates/queue">
        <properties.ActiveMQResourceAdapter PhysicalName="Typedagkalender_destination" />
    </jmsQueue>
    <jmsQueue id="jms/typedagkalender/kalenderupdates/dlqueue" jndiName="jms/typedagkalender/kalenderupdates/dlqueue">
        <properties.ActiveMQResourceAdapter PhysicalName="_SYSTEM.Exception.Destination" />
    </jmsQueue>

    <jmsActivationSpec id="jms/typedagkalender/kalenderupdates/queueAS">
        <properties.ActiveMQResourceAdapter destinationType="javax.jms.Queue" destination="jms/typedagkalender/kalenderupdates/queue" />
    </jmsActivationSpec>
    <jmsActivationSpec id="jms/typedagkalender/kalenderupdates/dlqueueAS">
        <properties.ActiveMQResourceAdapter destinationType="javax.jms.Queue" destination="jms/typedagkalender/kalenderupdates/dlqueue" />
    </jmsActivationSpec>
</server>

@TransactionAttribute(NOT_SUPPORTED)
@MessageDriven(mappedName = "jms/typedagkalender/kalenderupdates/queue", activationConfig = {
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
        @ActivationConfigProperty(propertyName = "destination", propertyValue = "jms/typedagkalender/kalenderupdates/queue")
})
public class KalenderUpdateProcessor implements MessageListener {

    private static final Logger LOGGER = LoggerFactory.getLogger(KalenderUpdateProcessor.class);

    @Inject
    private KalenderAbonnementService kalenderAbonnementService;

    @Override
    public void onMessage(Message message) {
        if (!(message instanceof TextMessage)) {
            LOGGER.error("Er is alleen ondersteuning voor TextMessages");
            return;
        }

        Auditor.setTimestamp(now());
        TextMessage textMessage = (TextMessage) message;

        try {
            LOGGER.debug("Textmessage gekregen voor KalenderJaargangVersieUpdate {}", textMessage.getText());
            handle(textMessage.getText());
        } catch (JMSException e) {
            LOGGER.error("Fout tijdens behandelen van message {}: {}", textMessage, e);
            throw new KalenderUpdateNotificationException("Fout tijdens behandelen van message " + textMessage, e);
        } finally {
            Auditor.destroy();
        }
    }
}

Answer 1

我找到了解决方案，似乎我不能为队列使用不同的physicalname，否则它将无法工作。Well solution在这里是一个很大的词也许，也许我不得不说我没有找到一种方法使它使用不同的physicalname而是使用了相同的队列名。

<?xml version="1.0" encoding="UTF-8"?>
<server>
    <!-- JMS CONFIGURATION -->
    <resourceAdapter id="ActiveMQResourceAdapter" location="${server.config.dir}/resources/lib/resource-adapter/activemq-rar-5.16.0.rar">
        <properties.activemq ServerUrl="tcp://localhost:61616" />
    </resourceAdapter>

    <messagingEngine>
        <queue id="jms/typedagkalender/kalenderupdates/queue" />
        <queue id="jms/typedagkalender/kalenderupdates/dlqueue" />
    </messagingEngine>

    <jmsQueueConnectionFactory jndiName="jms/typedagkalender/kalenderupdates/queueCF" connectionManagerRef="ConMgr">
        <properties.ActiveMQResourceAdapter />
    </jmsQueueConnectionFactory> -->

    <connectionManager id="ConMgr" maxPoolSize="${jms.ConMgr.maxPoolSize}" />

    <jmsQueue id="jms/typedagkalender/kalenderupdates/queue" jndiName="jms/typedagkalender/kalenderupdates/queue">
        <properties.ActiveMQResourceAdapter PhysicalName="jms/typedagkalender/kalenderupdates/queue" />
    </jmsQueue>
    <jmsQueue id="jms/typedagkalender/kalenderupdates/dlqueue" jndiName="jms/typedagkalender/kalenderupdates/dlqueue">
        <properties.ActiveMQResourceAdapter PhysicalName="jms/typedagkalender/kalenderupdates/dlqueue" />
    </jmsQueue>

    <jmsActivationSpec id="jms/typedagkalender/kalenderupdates/queueAS">
        <properties.ActiveMQResourceAdapter destinationType="javax.jms.Queue" destination="jms/typedagkalender/kalenderupdates/queue" />
    </jmsActivationSpec>
    <jmsActivationSpec id="jms/typedagkalender/kalenderupdates/dlqueueAS">
        <properties.ActiveMQResourceAdapter destinationType="javax.jms.Queue" destination="jms/typedagkalender/kalenderupdates/dlqueue" />
    </jmsActivationSpec>
</server>