Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Configuring the JBoss server transaction and authentication timeouts


JBoss tuning parameters are set during installation. The "out-of-box" settings should be adequate for most purposes, but you can change these tuning parameters for transactions and re-authentication.

While these parameters can be changed for any installation, you are most likely to need to change them for a remote (federated databases) deployment. In such cases, because there is a significant latency between the JBoss server and the BMC Remedy AR System database server, and if there is much OU data to sync, then you might need to adjust those values using the following instructions. The default settings (for the TransactionTimeout, DefaultCacheTimeout and DefaultCacheResolution parameters), which are set during the installation, are shown in the example code.

Changing transaction timeouts

If a background job cannot finish before timing out, you must increase the TransactionTimeout. For example, syncing a large organizational unit hierarchy with BMC IT Business Management Suite can take longer than a typical job.

To change the transaction timeout

  1. Locate the jboss-service.xml file:
    • In JBoss Enterprise Edition: Go to production\conf.
    • In JBoss Community Edition: Go to default\conf.
  2. In the following section, set the TransactionTimeout to 3600, which is 60 minutes (the default is 300, which is 5 minutes): 


    <!-- JBoss Transactions JTA -->
    <mbean code="com.arjuna.ats.jbossatx.jta.TransactionManagerService"
      name="jboss:service=TransactionManager">
      <attribute name="TransactionTimeout">3600</attribute>
      <attribute name="ObjectStoreDir">${jboss.server.data.dir}/tx-object-store</attribute>
    </mbean>
  3. To apply the changes, restart JBoss.

Changing the JBoss user re-authentication interval

JBoss re-authenticates each logged-on user regularly. For example, BMC IT Business Management Suite contacts the BMC Remedy AR System server periodically to check the user's credentials. The default interval is 60 seconds (1 minute).

To increase the time interval

  1. Locate the jboss-service.xml file:
    • In JBoss Enterprise Edition: Go to production\conf.
    • In JBoss Community Edition: Go to default\conf.
  2. Locate the DefaultCacheTimeout and DefaultCacheResolution parameters.
  3. Change their values to 1800 seconds.
  4. To apply the changes, restart JBoss.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*