无法在 Spring 中代理 JBossMQ 队列

发布于 2024-12-08 23:30:45 字数 1030 浏览 0 评论 0原文

Spring JMS 对抗 JBoss 4.x JBossMQ 队列（我知道，旧的 JBoss，JBossMQ 已被 JBoss Messaging 取代，但我无法更改堆栈）。当启动时加载 Spring JMS 配置时，一切正常，但是当我使 JNDI 查找变得懒惰时，以便在我想要发送 JMS 消息时首先加载它们，我得到以下异常：

org.springframework.jms.InvalidDestinationException: Destination is not an instance of SpyDestination QUEUE.myQueueName; nested exception is javax.jms.InvalidDestinationException: Destination is not an instance of SpyDestination QUEUE.myQueueName
at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:285)

我的配置：

    <jee:jndi-lookup id="beanNameForMyQueue" 
    jndi-name="queue/myQueueName" 
    resource-ref="true" environment-ref="jndiEnvironment" 
    lookup-on-startup="false" cache="true" proxy-interface="javax.jms.Queue" />

我找到了 JBoss JIRA 对此，以及此类似的 HornetQ 帖子，但到目前为止还没有骰子。

我只是对惰性初始化不走运，还是有解决方法？

原文

Spring JMS going against a JBoss 4.x JBossMQ queue (I know, old JBoss, JBossMQ superseded by JBoss Messaging, but I can't change the stack). Everything works when the Spring JMS configuration is loaded at startup, but when I make the JNDI lookups lazy, so that they are first loaded when I want to send a JMS message, I get the following exception:

org.springframework.jms.InvalidDestinationException: Destination is not an instance of SpyDestination QUEUE.myQueueName; nested exception is javax.jms.InvalidDestinationException: Destination is not an instance of SpyDestination QUEUE.myQueueName
at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:285)

My config:

    <jee:jndi-lookup id="beanNameForMyQueue" 
    jndi-name="queue/myQueueName" 
    resource-ref="true" environment-ref="jndiEnvironment" 
    lookup-on-startup="false" cache="true" proxy-interface="javax.jms.Queue" />

I found a JBoss JIRA on this, and this similar HornetQ post, but so far no dice.

Am I just out of luck with the lazy init, or is there a workaround?

分享到QQ

分享到微博