ActiveMQ之XML配置元素官方参考手册.docx

Elements By TypeTheorg.apache.activemq.broker.TransportConnectorType ImplementationsTwork.jms.InboundQueueBridgeType ImplementationsCreate an Inbound Queue BridgeTwork.NetworkConnectorType Implementationsclass to create dynamic network connectors listed in an directory server using the LDAP v3 protocol as defined in RFC 2251, the entries listed in the directory server must implement the ipHost and ipService objectClasses as defined in RFC 2307.A network connector which uses some kind of multicast-like transport that communicates with potentially many remote brokers over a single logical link Transport instance such as when using multicast. This implementation does not depend on multicast at all; any other group based transport could be used.A network connector which uses a discovery agent to detect the remote brokers available and setup a connection to each available remote brokerTheorg.apache.activemq.broker.BrokerServiceType ImplementationsAn ActiveMQ Message Broker. It consists of a number of transport connectors, network connectors and a bunch of properties which can be used to configure the broker as its lazily created.Theorg.apache.activemq.usage.TempUsageType ImplementationsUsed to keep track of how much of something is being used so that a productive working set usage can be controlled. Main use case is manage memory usage.Theorg.apache.activemq.broker.region.policy.PendingSubscriberMessageStoragePolicyType ImplementationsPending messagesPending messages heldTheorg.apache.activemq.usage.MemoryUsageType ImplementationsUsed to keep track of how much of something is being used so that a productive working set usage can be controlled. Main use case is manage memory usage.Theorg.apache.activemq.broker.BrokerPluginType ImplementationsAn authorization plugin where each operation on a destination is checked against an authorizationMapADOTfile creator plugin which creates a DOT file showing the current connectionsADOTfile creator plugin which creates a DOT file showing the current topic & queue hierarchies.Provides a JAAS based authentication pluginProvides a JAAS based SSL certificate authentication pluginA simple Broker interceptor which allows you to enable/disable logging.A Broker interceptor which allows you to trace all operations to a Multicast socket.Provides a simple authentication pluginA Broker interceptor which updates a JMS Clients timestamp on the message with a broker timestamp. Useful when the clocks on client machines are known to not be correct and you can only trust the time set on the broker machines. Enabling this plugin will break JMS compliance since the timestamp that the producer sees on the messages after as send() will be different from the timestamp the consumer will observe when he receives the message. This plugin is not enabled in the default ActiveMQ configuration.A Broker interceptor which allows you to trace all operations to a UDP socket.Theorg.apache.activemq.store.jdbc.JDBCAdapterType ImplementationsAxion specific Adapter. Axion does not seem to support ALTER statements or sub-selects. This means: - We cannot auto upgrade the schema was we roll out new versions of ActiveMQ - We cannot delete durable sub messages that have be acknowledged by all consumers.This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob() operations. This is a little more involved since to insert a blob you have to: 1: insert empty blob. 2: select the blob 3: finally update the blob with data value. The databases/JDBC drivers that use this adapter are:This JDBCAdapter inserts and extracts BLOB data using the setBytes()/getBytes() operations. The databases/JDBC drivers that use this adapter are:Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter.sub-classing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations.The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations.The databases/JDBC drivers that use this adapter are:Provides JDBCAdapter since that uses IMAGE datatype to hold binary data. The databases/JDBC drivers that use this adapter are: Sybase MS SQLJDBC Adapter for Informix database. Because Informix database restricts length of composite primary keys, length ofcontainer namefield andsubscription idfield must be reduced to 150 characters. Therefore be sure not to use longer names for container name and subscription id than 150 characters.Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter.Subclassing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations.The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations.The databases/JDBC drivers that use this adapter are:This JDBCAdapter inserts and extracts BLOB data using the setBinaryStream()/getBinaryStream() operations. The databases/JDBC drivers that use this adapter are: AxionTheorg.apache.activemq.broker.region.policy.PendingQueueMessageStoragePolicyType ImplementationsPendingPending messagesPending messagesThejavax.jms.TopicConnectionFactoryType ImplementationsASpringenhanced connection factory which will automatically use the Spring bean name as the clientIDPrefix property so that connections created have client IDs related to your Spring.xml file for easier comprehension fromJMX.ASpringenhanced XA connection factory which will automatically use the Spring bean name as the clientIDPrefix property so that connections created have client IDs related to your Spring.xml file for easier comprehension fromJMX.Theorg.apache.activemq.broker.region.virtual.VirtualDestinationType ImplementationsRepresents a virtual queue which forwards to a number of other destinations.Represents a virtual topic which forwards to a number of other destinations.CreatesVirtual Topicsusing a prefix and postfix. The virtual destination creates a wildcard that is then used to look up all active queue subscriptions which match.Theorg.apache.activemq.broker.region.policy.PolicyMapType ImplementationsRepresents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies.Theorg.apache.activemq.usage.UsageCapacityType ImplementationsIdentify if a limit has been reachedIdentify if a limit has been reachedTheorg.apache.activemq.broker.region.policy.PendingMessageLimitStrategyType ImplementationsThis PendingMessageLimitStrategy is configured to a constant value for all subscriptions.This PendingMessageLimitStrategy sets the maximum pending message limit value to be a multiplier of the prefetch limit of the subscription.Theorg.apache.activemq.usage.SystemUsageType ImplementationsHolder for Usage instances for memory, store and temp files Main use case is manage memory usage.Thejavax.jms.DestinationType ImplementationsAn ActiveMQ QueueAn ActiveMQ TopicTheorg.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicyType ImplementationsThis implementation of link SubscriptionRecoveryPolicy will keep a fixed count of last messages.This implementation of link SubscriptionRecoveryPolicy will keep a fixed amount of memory available in RAM for message history which is evicted in time order.This implementation of link SubscriptionRecoveryPolicy will only keep the last message.This SubscriptionRecoveryPolicy disable recovery of messages.This implementation of link SubscriptionRecoveryPolicy will perform a user specific query mechanism to load any messages they may have missed.This implementation of link SubscriptionRecoveryPolicy will keep a timed buffer of messages around in memory and use that to recover new subscriptions.Thejavax.jms.QueueConnectionFactoryType ImplementationsASpringenhanced connection factory which will automatically use the Spring bean name as the clientIDPrefix property so that connections created have client IDs related to your Spring.xml file for easier comprehension fromJMX.ASpringenhanced XA connection factory which will automatically use the Spring bean name as the clientIDPrefix property so that connections created have client IDs related to your Spring.xml file for easier comprehension fromJMX.Theorg.apache.activemq.broker.jmx.ManagementContextType ImplementationsA Flow provides different dispatch policies within the NMRTheorg.apache.activemq.store.jdbc.StatementsType ImplementationsTheorg.apache.activemq.store.PersistenceAdapterFactoryType ImplementationsAn implementation of link PersistenceAdapterFactoryCreates a default persistence model using the Journal and JDBCTheorg.apache.activemq.security.AuthorizationEntryType ImplementationsRepresents an entry in a link DefaultAuthorizationMap for assigning different operations (read, write, admin) of user roles to a specific destination or a hierarchical wildcard area of destinations.Represents an entry in a link DefaultAuthorizationMap for assigning different operations (read, write, admin) of user roles to a temporary destinationTheorg.apache.activemq.broker.region.policy.PendingDurableSubscriberMessageStoragePolicyType ImplementationsPending messages for durable subscribersPending messages for a durablePendingTheorg.apache.activemq.broker.region.group.MessageGroupMapFactoryType ImplementationsA factory to create instances of link SimpleMessageGroupMap when implementing theMessage Groupsfunctionality.A factory to create instances of link SimpleMessageGroupMap when implementing theMessage Groupsfunctionality.Theorg.apache.activemq.usage.StoreUsageType ImplementationsUsed to keep track of how much of something is being used so that a productive working set usage can be controlled. Main use case is manage memory usage.Theorg.apache.activemq.broker.region.policy.DeadLetterStrategyType ImplementationsA link DeadLetterStrategy where each destination has its own individual DLQ using the subject naming hierarchy.A default implementation of link DeadLetterStrategy which uses a constant destination.Thejavax.jms.TopicType ImplementationsAn ActiveMQ TopicTheorg.apache.activemq.ActiveMQPrefetchPolicyType ImplementationsDefines the prefetch message policies for different types of consumersTheorg.apache.activemq.broker.BrokerType ImplementationsA simple Broker interceptor which allows you to enable/disable logging.A Broker interceptor which allows you to trace all operations to a Multicast socket.A Broker interceptor which updates a JMS Clients timestamp on the message with a broker timestamp. Useful when the clocks on client machines are known to not be correct and you can only trust the time set on the broker machines. Enabling this plugin will break JMS compliance since the timestamp that the producer sees on the messages after as send() will be different from the timestamp the consumer will observe when he receives the message. This plugin is not enabled in the default ActiveMQ configuration.A Broker interceptor which allows you to trace all operations to a UDP socket.Theorg.apache.activemq.store.PersistenceAdapterType ImplementationsAn implementation of link PersistenceAdapter designed for use with a link Journal and then check pointing asynchronously on a timeout with some other long term persistent storage.A link PersistenceAdapter implementation using JDBC for persistence storage. This persistence adapter will correctly remember prepared XA transactions, but it will not keep track of local transaction commits so that operations performed against the Message store are done as a single uow.An implementation of link PersistenceAdapter designed for use with a link Journal and then check pointing asynchronously on a timeout with some other long term persistent storage.Theorg.apache.activemq.broker.region.policy.PolicyEntryType ImplementationsRepresents an entry in a link PolicyMap for assigning policies to a specific destination or a hierarchical wildcard area of destinations.Twork.DemandForwardingBridgeSupportType ImplementationsA demand forwarding bridge which works with multicast style transports where a single Transport could be communicating with multiple remote brokersForwards messages from the local broker to the remote broker based on demand.Twork.jms.OutboundQueueBridgeType ImplementationsCreate an Outbound Queue BridgeTheorg.apache.activemq.store.jdbc.JDBCPersistenceAdapterType ImplementationsA link PersistenceAdapter implementation using JDBC for persistence storage. This persistence adapter will correctly remember prepared XA transactions, but it will not keep track of local transaction commits so that operations performed against the Message store are done as a single uow.Tmand.ActiveMQDestinationType ImplementationsAn ActiveMQ QueueAn ActiveMQ TopicTwork.jms.InboundTopicBridgeType ImplementationsCreate an Inbound Topic BridgeTwork.jms.JmsConnectorType ImplementationsA Bridge to other JMS Queue providersA Bridge to other JMS Topic providersTheorg.apache.activemq.RedeliveryPolicyType ImplementationsConfiguration options used to control how messages are re-delivered when they are rolled back.Theorg.apache.activemq.security.AuthorizationMapType ImplementationsRepresents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies. Each entry in the map represents the authorization ACLs for each operation.An link AuthorizationMap which uses LDAPAn AuthorizationMap which is configured with individual DestinationMaps for each operation.Theorg.apache.activemq.security.TempDestinationAuthorizationEntryType ImplementationsRepresents an entry in a link DefaultAuthorizationMap for assigning different operations (read, write, admin) of user roles to a temporary destinationTheorg.apache.activemq.broker.region.policy.DispatchPolicyType ImplementationsSimple dispatch policy that sends a message to every subscription that matches the message.Simple dispatch policy that sends a message to every subscription that matches the message.Dispatch policy that causes every subscription to see messages in the same order.Thejavax.jms.ConnectionFactoryType ImplementationsASpringenhanced connection factory which will automatically use the Spring bean name as the clientIDPrefix property so that connections created have client IDs related to your Spring.xml file for easier comprehension fromJMX.ASpringenhanced XA connection factory which will automatically use the Spring bean name as the clientIDPrefix property so that connections created have client IDs related to your Spring.xml file for easier comprehension fromJMX.Thejavax.jms.QueueType ImplementationsAn ActiveMQ QueueTheorg.apache.activemq.broker.region.policy.MessageEvictionStrategyType ImplementationsAn eviction strategy which evicts the oldest message