2.5. Server Configuration Migration

HornetQ configuration differs significantly from JBoss Messaging, so it is not possible to provide a one-to-one mapping between the two. Table 2.2, “Server attribute mapping between JBoss Messaging and HornetQ” lists JBoss Messaging server attributes and their equivalents (where possible) in HornetQ.
Unless explicitly indicated, attributes in the HornetQ Server Attributes column are configured in <JBOSS_HOME>/jboss-as/server/<PROFILE>/deploy/hornetq/hornetq-configuration.xml. The full set of supported directives in this file are documented in Appendix A, Configuration Reference

Table 2.2. Server attribute mapping between JBoss Messaging and HornetQ

JBoss Messaging Server Attributes (Server Peer MBean) Equivalent HornetQ Server Attributes
ServerPeerID N/A - HornetQ does not require a specified server ID
DefaultQueueJNDIContext, DefaultTopicJNDIContext N/A
PostOffice N/A
DefaultDLQ N/A - HornetQ defines dead letter addresses at the core level. There is no default dead letter address for an address unless you specify one.
DefaultMaxDeliveryAttempts N/A - In HornetQ, the default is always 10.
DefaultExpiryQueue N/A - HornetQ defines expiry addresses at the core level. There is no default expiry address for an address unless you specify one.
DefaultRedeliveryDelay N/A - HornetQ's default redelivery delay is always 0 (no delay).
MessageCounterSamplePeriod message-counter-sample-period
FailoverStartTimeout N/A
FailoverCompleteTimeout N/A
DefaultMessageCounterHistoryDayLimit N/A
ClusterPullConnectionFactory N/A
DefaultPreserveOrdering N/A
RecoverDeliveriesTimeout N/A
EnableMessageCounters message-counter-enabled
SuckerPassword cluster-password
SuckerConnectionRetryTimes bridges.reconnect-attempts
SuckerConnectionRetryInterval bridges.reconnect-interval
StrictTCK N/A
Destinations, MessageCounters, MessageStatistics N/A - These are part of HornetQ's management functions. Refer to the appropriate chapter for details.
SupportsFailover N/A
PersistenceManager N/A - HornetQ uses its built-in high-performance journal as its persistence utility.
JMSUserManager N/A
SecurityStore N/A - The security manager is configured in hornetq-beans.xml or hornetq-jboss-beans.xml.