Chapter 3. JEUS MQ Server Configuration

Table of Contents

3.1. Overview
3.1.1. Directory Structure
3.1.2. Screen Layout
3.2. Configuring JMS Resources
3.2.1. Configuring Destinations
3.2.2. Configuring Durable Subscribers
3.3. Configuring JMS Engines
3.3.1. Basic Information
3.3.2. Configuring Service Channels
3.3.3. Configuring Connection Factories
3.3.4. Configuring Persistence Stores
3.3.5. Configuring Message Sorting
3.4. Server Management and Monitoring
3.4.1. Server Management
3.4.2. Server Monitoring

This chapter describes how to configure the JMS engines and resources that are used to run a JEUS MQ server.

A JEUS MQ server functions as a JMS engine in JEUS, and a single JEUS MQ server can run on each JEUS server. For more information about each component of JEUS, refer to JEUS Server Guide. "Chapter 1. Introduction".

Click [Servers] on the left pane to go to the Servers page. Click [Add] to add a server.

In JEUS WebAdmin, the JEUS MQ Server configuration includes the following menus.

  • [Basic]

  • [Resource]

  • [Engine]

It is recommended to use WebAdmin to configure JEUS MQ servers.

The following describes each JMS configuration screen. Since the [Basic] menu does not contain JMS related settings, its description is omitted.

[Resource]

The Jms Resource screen is used to configure JMS resources. Go to [Servers] > [Server Name] > [Resource] tab, and select the [Jms Resource] menu.

The following is the Jms Resource page. For more information, refer to "3.2. Configuring JMS Resources".


[Engine]

The Jms Resource screen is used to configure JMS MQ servers. Go to [Servers] > [Server Name] > [Engine] tab, and select the [Jms Engine] menu.


The JMS Engine screen contains the following menus.

JMS resources can be configured from the Jms Resource screen. Go to [Servers] > [Server Name] > [Resource] tab, and select the [Jms Resource] menu.


The Jms Resource screen contains the following two sections.

Like Queues or Topics, JEUS MQ servers register destinations in JEUS JNDI Service by reading the domain configuration. In the Destination section of the Jms Resource screen, select a resource from the list to go to the resource configuration screen.


Enter the Destination settings and then click [OK]. To reset the settings, click [Reset].

Destination Memory Management

If messages, which could not be sent to a client, are accumulated at the destination, an OutOfMemoryError may occur on the JVM and the server may be terminated. To resolve this problem, JEUS MQ applies different memory management policies for each destination.

JEUS MQ servers hold strong references to message contents when the destination does not use a lot of memory. JEUS MQ servers operate according to the Limit and High Mark property settings.

  • If the amount of memory used exceeds the Limit value, messages from the clients will trigger a JMSException. The default value is 128MB.

  • If the amount of memory used exceeds the High Mark value, the memory can no longer manage the stored messages. The default value is 96MB.

Even after a message at a destination is deleted from the memory, the message will not be lost. Since the message is saved in the storage, a JEUS MQ server can read and process the messages in the storage when necessary. The processing speed is slower when using the storage than memory.

Note

The memory of a JEUS MQ server always keeps the messages that are not saved in the storage. The High Mark property is applicable only when a storage is configured and a message is set to DeliveryMode.PERSISTENT.

Controlling Message Flow

The "Max Pending Limit" and "Resume Dispatch Factor'" properties in the destination screen are used to control the message flow. If the message listener is registered in a queue or topic, and when messages arrive, the messages will be immediately sent to the consumers. If the client cannot process the messages fast enough, the messages will be accumulated on the client and an OutOfMemory error will be raised. To prevent such error, specify the maximum number of messages that can accumulate on the client after which the server suspends sending messages for a given time.

JEUS MQ servers can be configured from the Jms Engine screen. Go to [Servers] > [Server Name] > [Engine] tab, and select the [Jms Engine] menu.

A Persistence Store is needed to restore messages, subscriptions, or transactions to the previous state when the server restarts. If a Persistence Store is not configured, a message that the client sent in the DeliveryMode.PERSISTENT mode cannot be properly delivered if the server fails. JEUS MQ provides two types of Persistence Stores, journal log and database.

To configure a Persistence Store, go to [Servers] > [Engine] > [Jms Engine] > [Persistence Store] in WebAdmin.


Select Journal to use the logging method or select Jdbc to use the database method for the Persistent Store.

For detailed information about each column of the tables created when JDBC is configured, refer to "Appendix B. JDBC Persistence Store Columns".

JEUS MQ servers should be managed through the following functions in order to guarantee seamless services without message loss.

  • Manages and monitors the resources on running JEUS MQ servers.

    The following resources are managed and monitored.

    • JMS management objects including connection factories and destinations

    • Messages in destinations and durable subscriptions

    • Connections, sessions, and message producers and consumers

    • Memory space occupied by JEUS MQ servers

    • Persistent storage used by JEUS MQ servers

  • Handles failures and recovers JEUS MQ servers from them.

This chapter introduces how to manage JEUS MQ servers with jmsadmin, the JEUS console tool, and WebAdmin.

Servers can be monitored using jmsadmin and WebAdmin.

Using WebAdmin

Go to [Monitoring] > [JMS] to monitor the current status of JEUS MQ servers.

Using the Console Tool

Server resources can be checked by executing various commands in the console tool. The console tool is in the following directory.

JEUS_HOME/bin/

The following commands are provided for server monitoring.

  • Connection factories

    CommandDescription
    list-jms-connection-factoriesChecks the connection factory list and displays connection factory information.
  • Destinations

    CommandDescription
    list-jms-destinationsChecks the destination list and displays destination information.
    control-jms-destinationControls the state of the specified destination.
  • Messages

    CommandDescription
    list-jms-messagesSearches for messages in a specified destination.
    view-jms-messageSearches for the detailed information of a specified message.
    move-jms-messagesMoves the specified messages to another destination in the cluster or server.
    delete-jms-messagesDeletes the specified messages from the destination.
    export-jms-messagesSends the specified messages in the XML format.
    import-jms-messagesRetrieves the exported XML messages to the specified destination.
  • Durable Subscriptions

    CommandDescription
    list-jms-durable-subscriptionsSearches the list of Durable Subscriptions or the information about a specified Durable Subscription.
  • Clients

    CommandDescription
    list-jms-clientsSearches the list of clients and displays the client information.
    ban-jms-clientForcibly closes the connection with the client.
  • Transactions

    CommandDescription
    list-jms-pending-transactionsDisplays the list of pending transactions.
    commit-jms-pending-transactionForcibly commits the specified pending transaction.