Version 15



    JBossMQ destintation configuration is controlled by the DestinationManager.


    For technical reasons the configuration can be found in the persistence configuration files,

    e.g. deploy{-hasingleton}/jms/hsqldb-jdbc2-service.xml (the config varies slightly depending upon how the persistence works).

    In older versions of JBoss it was in jbossmq-service.xml


    Default Configuration

      <mbean code="" name="">
        <depends optional-attribute-name="MessageCache"></depends>
        <depends optional-attribute-name="PersistenceManager"></depends>
        <depends optional-attribute-name="StateManager"></depends>


    Configurable Attributes

    • PersistenceManager

      - the object name of the PersistenceManager

    • StateManager

      - the object name of the StateManager

    • MessageCache

      - the object name of the MessageCache

    • TemporaryMaxDepth

      - the maximum depth of TemporaryQueues and TemporaryTopics

    • TemporaryInMemory

      - whether to avoid message softening when using the NullPersistenceManager (from JBoss-3.2.4)

    • ReceiversImpl

      - the class to use for the receivers implementation (from JBoss-3.2.4)

    • RecoveryRetries

      - the default recovery retries for queues and durable subscriptions - default 0 - zero(from JBoss-4.0.3)

    • ExpiryDestination - the default expiry destination for messages that expire on JBoss.  default null (from JBoss-4.0.4, 3.2.8)




    • ClientCount

      - the number of ClientConsumers connected to the server

    • Clients

      - a map of ConnectionToken -> ClientConsumer

    • listMessageCounter

      - a list of MessageCounters one for each ClientSubscription

    • resetMessageCounter

      - clear the MessageCounter data for all ClientSubscriptions



    • createQueue(String name)

      - create a new Queue with jndi name queue/name

    • createQueue(String name, String jndiName)

      - create a new Queue with the given jndi name

    • createTopic(String name)

      - create a new Topic with jndi name topic/name

    • createTopic(String name, String jndiName)

      - create a new Topic with the given jndi name

    +NOTE: The destinations created using these operations do not survive a reboot of the server although

    persistence messages are not lost so they can be recovered by recreating the queue/topic+