Download jboss mq - client.jar

It was adapted from the PDF available here. At the point of writing this article you must use the nightly build of JBoss AS 7 if you would like to be able to change the persistence method used by ActiveMQ by editing the broker config file. The configuration overview above corresponds to the XML below, showing a single queue and single topic defined as part of the resource adapter configuration. For a broker running on brokerHostName at port , the stanza would look as follows:.

It needs to be bound to the physical name provided from standalone. For example:. Here is a simple, generic example of how to create a module:. The default configuration is shown below. SecurityDomain : Specify the security domain name to use for authentication and role based authorization. DefaultSecurityConfig : This element specifies the default security configuration settings for destinations. This applies to temporary queues and topics as well as queues and topics that do not specifically specify a security configuration.

The DefaultSecurityConfig should declare some number of role elements which represent each role that is allowed access to a destination. Each role should have the following attributes:. DestinationManager must be the last interceptor in the interceptor stack.

ClientCount : The number of clients connected to the server. Clients : A java. ConnectionToken, org. MessageCounter : An array of org. MessageCounter instances that provide statistics for a JMS destination. Type : Either Queue or Topic indicating the destination type. Name : The name of the destination. Subscription : The subscription ID for a topic. Durable : A boolean indicating if the topic subscription is durable.

Count : The number of message delivered to the destination. CountDelta : The change in message count since the previous access of count. Depth : The number of messages in the destination. DepthDelta : The change in the number of messages in the destination since the previous access of depth. Queues and topics can be created and destroyed at runtime through the DestinationManager MBean. The DestinationManager provides createQueue and createTopic operations for this. Both methods have a one argument version which takes the destination name and a two argument version which takes the destination and the JNDI name of the destination.

Queues and topics can be removed using the destroyQueue and destroyTopic operations, both of which take a destination name is input. The server determines when to move messages to secondary storage by using the org. MessageCache MBean. The cache store is used by the MessageCache to move messages to persistent storage. The value you set here typically depends on the type of persistence manager you are using. As memory usage approaches the max memory mark, the MessageCache will move messages to persistent storage so that the number of messages kept in memory approaches zero.

MakeSoftReferences : This controls whether or not the message cache will keep soft references to messages that need to be removed. The default is true. MinimumHard : The minimum number of the in memory cache. JBoss won't try to go below this number of messages in the cache. The default value is 1. MaximumHard : The upper bound on the number of hard references to messages in the cache.

JBoss will soften messages to reduce the number of hard references to this level. A value of 0 means that there is no size based upper bound. The default is 0. SoftenWaitMillis : The maximum wait time before checking whether messages need softening. The default is milliseconds 1 second. A value of 0 means that this check should be skipped. The default is 0 milliseconds. CacheHits : The number of times a hard referenced message was accessed. CacheMisses : The number of times a softened message was accessed.

HardRefCacheSize : The number of messages in the cache that are not softened. SoftRefCacheSize : The number of messages that are currently softened. SoftenedSize : The total number of messages softened since the last boot. TotalCacheSize : The total number of messages that are being managed by the cache. PersistenceManager should be used as the persistence manager assigned to the DestinationManager if you wish to store messages in a database.

There is a millisecond delay between each connection failed connection attempt and the next attempt. This must be greater than or equal to 1 and defaults to 5. You will need to adjust these properties if you which to run against another database other than Hypersonic. This section describes the destination MBeans used in the jbossmq-destinations-service.

The Queue is used to define a queue destination in JBoss. The following shows the configuration of one of the default JBoss queues. For example. In the case of the queue we just looked at, the name of the queue is testQueue.

SecurityConf : This element specifies a XML fragment which describes the access control list to be used by the SecurityManager to authorize client operations against the destination.

The content model is the same as for the SecurityManager SecurityConf attribute. If this is not set it will be bound under the queue context using the name of the queue. MaxDepth : The MaxDepth is an upper limit to the backlog of messages that can exist for a destination.

If exceeded, attempts to add new messages will result in a org. The MaxDepth can still be exceeded in a number of situations, e. Also transactions performing read committed processing, look at the current size of queue, ignoring any messages that may be added as a result of the current transaction or other transactions.

This is because we don't want the transaction to fail during the commit phase when the message is physically added to the queue. MessageCounterHistoryDayLimit : Sets the destination message counter history day limit with a value less than 0 indicating unlimited history, a 0 value disabling history and a value greater than 0 giving the history days count.

MessageCounter instances that provide statistics for this destination. QueueDepth : The current backlog of waiting messages. ReceiversCount : The number of receivers currently associated with the queue.

ScheduledMessageCount : The number of messages waiting in the queue for their scheduled delivery time to arrive. Topic is used to define a topic destination in JBoss. The following shows the configuration of one of the default JBoss topics. For example, in the case of the topic we just looked at, the name of the topic is testTopic. Download 34MB. Download 98MB Release Notes. Download 93MB Release Notes.

Download 88MB Release Notes. Download 90MB Release Notes. Download 90 MB Release Notes. Download 77 MB Release Notes. Download 74 MB Release Notes. Download 68 MB Release Notes. Download 59 MB Release Notes. JBoss Messaging Installation. Do not simply attempt to copy the Messaging release artifact jboss-messaging. Follow one of the alternate installation procedures outlined below instead. GA, such as 4. GA and 4. Therefore JBoss Messaging only runs with Java 5 or later. If you have a completely clean JBoss AS 4.

If you have a JBoss 4. Automated Installation. If you have modifed the JBoss AS 4. Run the installation script, available in the util directory of the release bundle as follows: If you want to create a simple non clustered installion based on the default configuration: cd util ant -f release-admin. If you have chosen messaging-node0 Warning For a clustered installation it is mandatory that a shared database is available to all nodes in the cluster. Therefore in order to use clustering you must replace this with a different shared database.

If the database is not replaced then clustering will not work. Please note that the default JBoss Messaging service binding manager bindings in sample-bindings. Manual Installation.