Increasing journaling size as tasks are going in progress mode in vApp
Article ID: 214890
Updated On:
Products
Issue/Introduction
Some tasks are getting stuck in-progress. New tasks mostly work but a group of tasks from last night are stuck in-progress.
Environment
Release : 14.3, 14.4
Component : CA IDENTITY SUITE (VIRTUAL APPLIANCE) vApp
Cause
By Default the jmsqueue journaling size if set to 2. We will be increasing this to 20.
Resolution
If you did not have a user to connect to JBoss-CLI, see the steps below:
You must sudo add-user.sh and create a new management console user. I create a new "jbossuser". You can create the user you need and password. Run the commands in bold below.
config@<Server Name> (##.##.###.##):/opt/CA/wildfly-idm/bin > ls
add-user.bat init.d standalone.bat
add-user.properties jboss-cli.bat standalone.conf
add-user.sh jboss-cli-logging.properties standalone.conf.bat
appclient.bat jboss-cli.sh standalone.conf.NOT_IN_USE
appclient.conf jboss-cli.xml standalone.sh
appclient.conf.bat jconsole.bat vault.bat
appclient.sh jconsole.sh vault.sh
client jdr.bat wsconsume.bat
domain.bat jdr.sh wsconsume.sh
domain.conf run.bat wsprovide.bat
domain.conf.bat run.sh wsprovide.sh
domain.sh service
config@<Server Name> VAPP-14.3.0 (##.##.###.##):/opt/CA/wildfly-idm/bin >
config@<Server Name> Vapp03 VAPP-14.3.0 (##.##.###.##):/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 : jbossuser
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 :
JBAS015266: 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 'jbossuser' for realm 'ManagementRealm'
Is this correct yes/no? y
Added user 'jbossuser' to file '/opt/CA/wildfly-idm/standalone/configuration/mgmt-users.properties'
Added user 'jbossuser' to file '/opt/CA/wildfly-idm/domain/configuration/mgmt-users.properties'
Added user 'jbossuser' with groups to file '/opt/CA/wildfly-idm/standalone/configuration/mgmt-groups.properties'
Added user 'jbossuser' 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
config@<Server Name> VAPP-14.3.0 (##.##.###.##):/opt/CA/wildfly-idm/bin >
config@<Server Name> VAPP-14.3.0 (##.##.###.##):/opt/CA/wildfly-idm/bin >
If you already have a user, start from here:
config@<Server Name>VAPP-14.3.0 (##.##.###.##):/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: jbossuser
Password:
Note: There are differences between vApp 14.3 and 14.4, check below the command for your version.
For Virtual Appliance 14.3
[standalone@localhost:9990 /] /subsystem=messaging/hornetq-server=default/:read-attribute(name=journal-min-files)
{
"outcome" => "success",
"result" => 2
}
[standalone@localhost:9990 /] /subsystem=messaging/hornetq-server=backup/:read-attribute(name=journal-min-files)
{
"outcome" => "success",
"result" => 2
}
[standalone@localhost:9990 /] /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"
}
}
[standalone@localhost:9990 /] /subsystem=messaging/hornetq-server=backup/:write-attribute(name=journal-min-files,value=20)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[standalone@localhost:9990 /] reload
[standalone@localhost:9990 /] /subsystem=messaging/hornetq-server=default/:read-attribute(name=journal-min-files)
{
"outcome" => "success",
"result" => 20
}
[standalone@localhost:9990 /] /subsystem=messaging/hornetq-server=backup/:read-attribute(name=journal-min-files)
{
"outcome" => "success",
"result" => 20
}
For Virtual Appliance 14.4
For version 14.4 use the same commands as in the example above 14.3 but instead of the path /subsystem=messaging/hornetq-server=default and /subsystem=messaging/hornetq-server=backup replace with the path /subsystem=messaging-activemq/server=default and /subsystem=messaging-activemq/server=backup
subsystem=messaging-activemq/server=default
[standalone@localhost:9990 server=default] :read-attribute(name=journal-min-files)
{
"outcome" => "success",
"result" => 2
}
/subsystem=messaging-activemq/server=backup
[standalone@localhost:9990 server=backup] :read-attribute(name=journal-min-files)
{
"outcome" => "success",
"result" => 2
}
/subsystem=messaging-activemq/server=backup
[standalone@localhost:9990 server=backup] :write-attribute(name=journal-min-files,value=20)
subsystem=messaging-activemq/server=default
[standalone@localhost:9990 server=default] :write-attribute(name=journal-min-files,value=20)
subsystem=messaging-activemq/server=default
[standalone@localhost:9990 server=default] :read-attribute(name=journal-min-files)
{
"outcome" => "success",
"result" => 20
}
/subsystem=messaging-activemq/server=backup
[standalone@localhost:9990 server=backup] :read-attribute(name=journal-min-files)
{
"outcome" => "success",
"result" => 20
}
-----
There are 6 commands, the first two to load the current configuration and the third and fourth to update the parameter with the value 20, the fifth one to reload the configuration, and the last ones to confirm the value was set correctly.
We then run the third and fourth commands. 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
