Red Hat Training

A Red Hat training course is available for Red Hat JBoss Operations Network

3.2.7. JBossAS5 - JBoss Messaging Service

Overview

Table 3.126. Overview

Description:the JBoss Messaging JMS provider
Singleton: yes
Plugin:JBossAS5

Child Resource Types

Connection Properties

Table 3.127. 

NameDescriptionRequiredInternal Name
Component Type  yes componentType
Component Subtype  yes componentSubtype
Component Name  yes componentName

Note

You must use the internal name to reference Configuration Properties in Dynamic Group Definition expressions.

Metrics

none

Configuration Properties

none

Operations

none

Package Types

none

3.2.7.1. JBossAS5 - Queue Service

Overview

Table 3.128. Overview

Description:a JMS queue
Singleton: no
Plugin:JBossAS5

Note

The message counter metrics will not be collected by default. In order for these metrics to be collected for all Topics and Queues for a given application server instance, go to the instance's JMX Console, and invoke the {{enableMessageCounters}} operation on the {{jboss.messaging:service=ServerPeer}} MBean. To ensure the message counters are still enabled when the application server is restarted, edit that instance's {{deploy/messaging/messaging-service.xml}} file and set the {{EnableMessageCounters}} attribute to "true".
Child Resource Types
none
Connection Properties

Table 3.129. 

NameDescriptionRequiredInternal Name
Jms Type  yes jms-type
Custom PropertiesMaps a list of custom property names to the the fully qualified class names of the org.rhq.plugins.jbossas5.adapter.api.PropertyAdapter implementations that should be used for those properties. no customProperties
Component Type  yes componentType
Component Subtype  yes componentSubtype
Component Name  yes componentName
Template Name  yes templateName
Component Name PropertyThe name of the Resource configuration property whose value should be used as the underlying ManagedComponent name when creating a new Resource of this type. yes componentNameProperty

Note

You must use the internal name to reference Configuration Properties in Dynamic Group Definition expressions.
Metrics

Table 3.130. Metrics

NameTypeDescriptionInternal Name
Run StatetraitRun StaterunState
Created ProgrammaticallytraitWas this queue created programmatically? If Yes, the queue will not survive a restart of the application server. If No, the queue was created via a deployment XML file.createdProgrammatically
Message Counter History Day LimittraitThis queue's message counter history day limit - <0: unlimited, =0: history disabled, >0: maximum day countmessageCounterHistoryDayLimit
Consumer CountmeasurementThe number of consumers on the queueconsumerCount
Delivering CountmeasurementThe number of messages currently being delivereddeliveringCount
Message CountmeasurementThe number of messages in the queuemessageCount
Scheduled Message CountmeasurementThe number of scheduled messages in the queuescheduledMessageCount
CountmeasurementThe total message count since startup or last counter resetmessageStatistics.count
Count DeltameasurementThe message count delta since last method callmessageStatistics.countDelta
DepthmeasurementThe current message count of pending messages within the queue waiting for dispatchmessageStatistics.depth
Depth DeltameasurementThe message count delta of pending messages since last method callmessageStatistics.depthDelta
Time Last UpdatemeasurementThe timestamp of the last message addmessageStatistics.timeLastUpdate
ClusteredtraitTrue if this queue is clustered, false otherwiseclustered

Note

You must use the internal name to reference Traits in Dynamic Group Definition expressions.
Configuration Properties

Table 3.131. 

NameDescriptionRequiredInternal Name
NameThe name of this queue (e.g. 'MyQueue'). yes name
JNDI NameThis queue's JNDI name (e.g. '/queue/MyQueue'). yes JNDIName
ClusteredIs this queue clustered? For an existing queue, this property is read-only. If not specified when creating a new queue, the default value is false. no clustered
Down Cache SizeWhen paging messages to storage from a subscription, they first go into a "Down Cache" before being written to storage. This enables the write to occur as a single operation, thus aiding performance. This setting determines the maximum number of messages that the Down Cache will hold before they are flushed to storage. Updates to this property will not go into effect until the queue has been restarted. The default value is 2000. no downCacheSize
Full SizeThe maximum number of messages for the queue held in memory at any one time. The actual queue can hold many more messages than this, but these are paged to and from storage as necessary, as messages are added or consumed. Updates to this property will not go into effect until the queue has been restarted. The default value is 200000. no fullSize
Max Delivery AttemptsThe number of delivery attempts before a message to a subscriber of this queue is moved to the DLQ. The default value is 10. A value of -1 indicates the default value should be used. no maxDeliveryAttempts
Max SizeThe maximum number of messages this queue can hold before they are dropped. A value of -1 means there is no maximum. The default value is -1. no maxSize
Page SizeWhen loading messages from a subscription, this is the maximum number of messages to pre-load in one operation. Must be less than Full Size and greater than or equal to Down Cache Size. Updates to this property will not go into effect until the queue has been restarted. The default value is 2000. no pageSize
Redelivery DelayThe delay in milliseconds before a rolled back or recovered message is redelivered. Set to 0 to disable redelivery. The default value is 0. A value of -1 indicates the default value should be used. no redeliveryDelay
DLQThe JMX ObjectName of the dead letter queue (DLQ) for this queue (e.g. "jboss.messaging.destination:service=Queue,name=PrivateDLQ") - overrides the default DLQ on the server peer. no DLQ
Expiry QueueThe JMX ObjectName of the expiry queue for this queue (e.g. "jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue") - overrides the default expiry queue on the server peer. no expiryQueue
Server PeerThe JMX ObjectName of the server peer this queue was deployed on (e.g. "jboss.messaging:service=ServerPeer"). Updates to this property will not go into effect until the queue has been restarted. no serverPeer
Security ConfigurationsThis 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. yes securityConfig

Note

You must use the internal name to reference Configuration Properties in Dynamic Group Definition expressions.
Operations

Table 3.132. Metrics

NameDescription
Remove All MessagesRemove all messages from the destination.
StartStart the destination.
StopStop the destination.
List All MessagesList all messages for the specified selector
List Durable MessagesList all durable messages for the specified selector
List Non Durable MessagesList all non durable messages for the specified selector
List Message Counter As HTMLGet the message counter as HTML
List Message Counter History As HTMLGet the message counter history as HTML
Reset Message CounterReset the message counter
Reset Message Counter HistoryReset the message counter history
Package Types
none