Announcement Announcement Module
No announcement yet.
DefaultMessageListenerContainer Cause: Unknown destination Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • DefaultMessageListenerContainer Cause: Unknown destination

    Hi all

    I am using the DefaultMessageListenerContainer and configure to do JNDI lookup retry in case of failure. So included the properties like lookupOnStartup, cache and proxyInterface in the config. With these new properties being added, on the logs I can see the below warn message occurs continuously.

    [topicObserverContainer-3] WARN o.s.j.l.DefaultMessageListenerContainer - Setup of JMS message listener invoker failed for destination ''- trying to recover. Cause: Unknown destination type - $Proxy5
    javax.jms.InvalidDestinationException: Unknown destination type - $Proxy5

    And the destination it is reporting in the Warn message is a topic.
    I have included the pubSubDomain property in "org.springframework.jms.listener.DefaultMessa geLi stenerContainer" configuration and set it as true. Still it did not resolve the issue.


    <bean id="topicObserverContainer" class="org.springframework.jms.listener.DefaultMes sageListenerContainer">
    & lt;property name="pubSubDomain" value="true" />
    & lt;property name="connectionFactory" ref="cachingTopicConnectionFactory" />
    & lt;property name="destination" ref="defaultTopicDestination" />
    & lt;property name="messageListener" ref="jmsMessageListener" />
    & lt;/bean>

    & lt;bean id="defaultTopicDestination" class="org.springframework.jndi.JndiObjectFactoryB ean">
    & lt;property name="jndiTemplate" ref="jndiTemplate" />
    & lt;property name="jndiName" value="${}" />
    & lt;property name="lookupOnStartup" value="false" />
    & lt;property name="cache" value="false" />
    & lt;property name="proxyInterface" value="javax.jms.Destination" />
    & lt;/bean>

    Please can anyone give any suggestions to avoid this warn message?

    Last edited by lipiden; Oct 22nd, 2013, 09:29 AM. Reason: Please see the configuration

  • #2
    Sorry for not getting to this sooner. We are in the process of moving to StackOverflow for our forums.

    This question is probably a better candidate for StackOverflow, perhaps against the #spring-jms tag.
    If you do post it there, please reply here with the link.