Tasks Failing at Random in vApp
Article ID: 207695
Updated On:
Products
Issue/Introduction
Under a heavier load, the default vApp journal file size may be inadequate. vApp defaults to 25MB and 2 files. This KB provides steps on how to set 20 journals of 25MBs. This means about twenty 25mb size journal files will be created at startup. When one file gets full, Jboss uses the next one.
This can cause tasks to run but fail at random times. It could be different or the same tasks where they work most of the time but sometimes run and sometimes fail.
Environment
Release : 14.3 and 14.4
Component : IdentityMinder(Identity Manager) on Virtual Appliance
Resolution
You must sudo add-user.sh and create a new management console user. I create a new "<username>". Create the user needed and password. Run the commands in bold below.
>:/opt/CA/wildfly-idm/bin > sudo ./add-user.sh
What type of user do you wish to add?
a) Management User (mgmt-users.properties)
b) Application User (application-users.properties)
(a):
Enter the details of the new user to add.
Using realm 'ManagementRealm' as discovered from the existing property files.
Username : <username>
Password recommendations are listed below. To modify these restrictions edit the add-user.properties configuration file.
- The password should not be one of the following restricted values {root, admin, administrator}
- The password should contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), 1 non-alphanumeric symbol(s)
- The password should be different from the username
Password :
Password must have at least 1 digit.
Are you sure you want to use the password entered yes/no? y
Re-enter Password :
What groups do you want this user to belong to? (Please enter a comma separated list, or leave blank for none)[ ]:
About to add user '<username>' for realm 'ManagementRealm'
Is this correct yes/no? y
Added user '<username>' to file '/opt/CA/wildfly-idm/standalone/configuration/mgmt-users.properties'
Added user '<username>' to file '/opt/CA/wildfly-idm/domain/configuration/mgmt-users.properties'
Added user '<username>' with groups to file '/opt/CA/wildfly-idm/standalone/configuration/mgmt-groups.properties'
Added user '<username>' with groups to file '/opt/CA/wildfly-idm/domain/configuration/mgmt-groups.properties'
Is this new user going to be used for one AS process to connect to another AS process?
e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB calls.
yes/no? n
>: /opt/CA/wildfly-idm/bin >
>:/opt/CA/wildfly-idm/bin >
>:/opt/CA/wildfly-idm/bin > ./jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect
Authenticating against security realm: ManagementRealm
Username: <username>
Password:
Note: There are differences between vApp 14.3 and 14.4, check below the command for your version.
For Virtual Appliance 14.3
}
[> /] /subsystem=messaging/hornetq-server=default/:read-attribute(name=journal-min-files)
{
"outcome" => "success",
"result" => 2
}
[> /] /subsystem=messaging/hornetq-server=default/: write-attribute(name=journal-min-files,value=20)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[> /] reload
[> /] /subsystem=messaging/hornetq-server=default/:read-attribute(name=journal-min-files)
{
"outcome" => "success",
"result" => 20
}
For Virtual Appliance 14.4
[> /] /subsystem=messaging-activemq/server=default/:read-attribute(name=journal-min-files)
{
"outcome" => "success",
"result" => 2
}
[> /] /subsystem=messaging-activemq/server=default/: write-attribute(name=journal-min-files,value=20)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[> /] reload
If the reload command fails, please, restart the Identity Manager service to reload the new configuration.
[> /] /subsystem=messaging-activemq/server=default/:read-attribute(name=journal-min-files)
{
"outcome" => "success",
"result" => 20
}
-----
There are 4 commands, the first one to load the current configuration and the second one to update the parameter with the value 20, the third one to reload the configuration, and the last one to confirm the value was set correctly.
We then run the second command. This writes the value to 20.
Run a reload. If the reload fails, please, restart the Identity Manager service to reload the new configuration
In the last command, we read the attribute again where it now returns 20 confirming the change was made.
If a cluster, this should be done on all nodes. This should also be done on any backup servers.
Feedback
