JMS Details Description
This is the list of properties that sets up the topics, queues, or connection factories. Some of the properties you can view in the SAP NetWeaver Administrator are purely informative, that is, you cannot edit them.
In the Show field, select JMS Resources to display the details related to the JMS connection factories and JMS destinations, Queues and Topics. The properties that are related to durable subscribers are in the Details section and are available only for Topics.
Properties of JMS Resources
Configuration Property Name |
Default Value |
Used In |
Description |
Agent Keep Alive Time (seconds) |
300 |
topic, queue |
The time in seconds to keep the message delivery agent alive after the last consumer or producer is closed.
This property is obsolete. |
Average Message Size (kilobytes) |
|
topic, queue |
The average message size in KB.
This property is obsolete. |
Connection ID |
- |
topic, queue |
The Connection ID. |
Client ID |
“” |
connection factory |
The Client ID of the connection factory. |
Connection Type |
- |
connection factory |
Displays the type of the connection factory. Possible values are: ConnectionFactory TopicConnectionFactory QueueConnectionFactory XATopicConnectionFactory XAQueueConnectionFactory XAConnectionFactory |
Set Limit To Delivery Attempts Count |
true |
queue |
This property is relevant only for queue destinations. Limits the number of delivery attempts and points out if the undeliverable messages have to be moved to a dead message queue. Refer also to Maximum Delivery Attempts. |
Destination Id |
|
topic, queue |
The ID of the destination. |
Is Temporary |
false |
topic, queue |
Indicates whether the destination is temporary.
This property is obsolete. |
Enable JMS Delivery Count |
true |
topic, queue |
Switches the optional message property JMSXDeliveryCount on or off. Shows the number of time the message has been delivered to a customer. |
Load Balance Behavior |
3 |
queue |
Defines the load balance behavior of the queue in case the destination has more than one consumer. The possible values are: · 1 (Exclusive) - the registering of a second consumer fails. · 3 (Round-robin) - messages are distributed among all registered consumers in a round-robin fashion. |
Maximum Delivery Attempts |
5 |
queue |
Defines the maximum number of delivery attempts. This property is active only if Set Limit To Delivery Attempts Count is set to true. |
Memory Queue Size (bytes) |
4096 |
topic, queue |
This property is obsolete. The amount of data to be loaded with a DB round-trip in KB. |
Memory Queue Maximum Rows To Select |
|
topic, queue |
This property is obsolete. The maximum number of messages to select from the database into the memory queue.
This property is obsolete. |
NoLocal |
false |
durable subscriber |
The selector expression to filter messages for the durable subscriber. |
Subscription Name |
- |
durable subscriber |
The subscription name. |
Subscription ID |
- |
durable subscriber |
The ID of the durable subscriber. |
Work List Buffer Size (bytes) |
- |
topic, queue |
The total size of the work list buffer in bytes.
This property is obsolete. |
Work List Maximum Rows To Select |
- |
topic, queue |
The maximum number of messages to select from the database into the work list.
This property is obsolete. |
In the Show field, select JMS Virtual Providers to display the following properties.
Properties of JMS Virtual Providers
Configuration Property Name |
Default Value |
Description |
ID |
- |
The unique ID of the JMS Virtual Provider. |
Agent Thread Count |
10 |
The maximum number of threads that can work simultaneously to deliver messages to the destinations belonging to this JMS Virtual Provider.
This property is obsolete. |
Clean Up Service Sleep Interval (milliseconds) |
600000 |
The time interval in milliseconds after which the Cleanup Service is triggered. The Cleanup Service is responsible for deleting the obsolete JMS messages from the database – these are the expired messages and the already acknowledged messages. |
Client Memory Size (bytes) |
104857600 |
This is the total amount of memory a JMS client can occupy. The implication of increasing this is that the JMS client will occupy more memory, and thus might affect the performance of other components and applications. |
Destination Count |
- |
The current number of destinations of the JMS Virtual Provider. |
Heap Usage |
0.1 |
The percentage of the heap to be used by the JMS Virtual Provider.
This property is obsolete. |
Count Limit In Master Queue |
32000 |
The maximum number of messages in the master queue.
This property is obsolete. |
Memory Queue Load Size (kilobytes) |
4096 |
The amount of data to load with a Database roundtrip in Kilobytes.
This property is obsolete. |
Client Consumer Buffer Size (bytes) |
102400 |
This is the amount of memory a JMS consumer can use for its message buffer (to pre-fetch messages from the server), that is, this is the size of the client-side in-memory message cache per consumer. The minimum recommended value is the size of the largest expected message. Values lower than that may lead to suboptimal performance. |
Size Limit In Master Queue (bytes) |
1048576 |
The size of the server-side in-memory message cache per destination allocated in memory for a destination.
This property is obsolete. |
Fetch Size On Startup In Master Queue |
4096 |
The number of messages that are loaded on destination startup.
This property is obsolete. |
Maximum Fetch Size In Master Queue |
1024 |
The maximum size of the loaded messages on destination startup.
This property is obsolete. |