Announcement Announcement Module
Collapse
No announcement yet.
ServerSessionMessageListenerContainer does not failover Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • ServerSessionMessageListenerContainer does not failover

    SETUP:
    =====
    ---------------------------------
    I am using ActiveMQ 5.0 with Spring 2.0.7 and I am using ActiveMQ schema based xbeans.

    <beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:amq="http://activemq.org/config/1.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schem...-beans-2.0.xsd
    http://activemq.org/config/1.0 http://activemq.apache.org/schema/activemq-core-5.0.xsd">

    I have a cluster of brokers configured as peers via the common discoveryUrl. All these brokers individually provide tcp interface. These brokers are configured within the JVMs of the producers. (Using Spring xbean configuration again).

    Consumer clients use activemq connection factory based on a failover URL. This failover URL is comprised of a list of the clusterred brokers:
    failover://(tcp://host1:11111?socket.tcpNoDelay=true&wireFormat.maxI nactivityDuration=0,tcp://host2:11111?socket.tcpNoDelay=true&wireFormat.maxI nactivityDuration=0,tcp://host3:11111?socket.tcpNoDelay=true&wireFormat.maxI nactivityDuration=0,tcp://host4:11111?socket.tcpNoDelay=true&wireFormat.maxI nactivityDuration=0)?initialReconnectDelay=100

    I am using amq:connectionFactory XML element to define the connection factory objects in producer and consumer configuration. (I believe this maps to org.apache.activemq.ActiveMQConnectionFactory)
    ------------------------------------


    ISSUE:
    =====
    I tried DefaultMessageListenerContainer and ServerSessionMessageListenerContainer and the configuration for both was identical. (connectionfactory reference, destination reference and messagelistener reference)

    The failover works perfectly with DefaultMessageListenerContainer but does not work when I use ServerSessionMessageListenerContainer.

    Questions?
    ========
    On the consumer side, do I need to setup connectionfactory in a different way when using ServerSessionMessageListenerContainer?

    Do I need special configuration of ServerSessionMessageListenerContainer itself for failover to work?

    Do I need to setup brokers in a specific way to enable support for ServerSession SPI support?

    thanks for your help
Working...
X