JBoss Messaging ships with a high-performance journal. This journal has been implemented by the JBoss Messaging team with a view to provide a high-performance messaging system. Since JBoss Messaging handles its own persistence, rather than relying on a database or other 3rd party persistence engine, we have been able to tune the journal to gain optimal performance for the persistence of messages and transactions. This guide describes the typical steps that should be taken to keep the journal file system healthy and performing with Symantec Identity Suite.
- Identity Manager is installed
Configuration Tasks and Steps
Need to Know: Folder Management
Delete the following folders on every server restart:
- Tmp – Contains .class files compiled on-the-fly from product JSPs. If new or updated JSPs are provided, then this location will continue to hold stale data.
- Data – The container’s journaling folder can be deleted without causing harm to the product. This is true since the product utilizes a task persistence database wherein key event state will be persisted – no reliance on the container’s journals.
- Log – Can be optionally deleted.
Task 1: Configure the Journal Size
It is recommended to change the default journal size as what comes out of the box is not an adequate size for journal files and their number. The recommended configurations are below and should be made in the standalone-full.xml or the standalone-full-ha.xml (if the environment is clustered).
This configuration means that upon startup, there will be roughly 20 files that are each 25mb each. When one file gets full, Jboss/Wildfly will move onto the next file for consumption until 20 files have been used.
An administrator can add a new Jboss User and manipulate these files from the command line rather than from editing the file directly.
Note: The application must be running for the JBoss CLI to make changes.
Navigate to *Jboss/wildfly_home*\bin>add-user.bat
Now you have the user associated with the Management Realm.
- Navigate to *Jboss/wildfly_home*/bin
- Run the jboss_cli.bat executable. Type “connect” when prompted
- Run the below command to check the minimum amount of journal files.
- Run the below command to increase the amount of minimum journal files.
- Do the same for property “journal-file-size” using write-attribute operation.
- Finally, do a reload:
Run the below command again to verify the change in Journal Min Files. The returned value should be “20”:
Also, you can run this command to get the operations supported
You should do this for both the live and backup nodes in your standalone file. For newer servers, the path to these properties is /subsystem=messaging-activemq/server=default.
Summary of Checking JMS Journals with JBoss/Wildfly
In conclusion, it does not make a difference at all whether the Journal changes are made directly in the configuration xml or inside of the JBoss CLI. The steps outlined here to tune the JBoss Journal File system is directly responsible for helping to maintain persistence and document changes to records, whether the change be an update, create, or delete.
This performance tuning configuration works cohesively with the Garbage Collector performance tuning article, as when delete records are added to the journal, the Garbage Collector algorithm determines if the journal file is needed.
Looking for additional help with the JBoss Application Server? ISX Consulting is an elite IAM security firm that offers boundless expertise in a range of cybersecurity and business process services, including Symantec Identity Suite. Take your interoperability to the next level, and contact an ISX consultant today.