An issue might occur where the initial loading of the Historic Transaction tab on the SAS^® Anti-Money Laundering 8.3 Customer Details page takes some time, but the page loads quickly with subsequent attempts.

If you determine that the database returns the query result (the amlcore microservice calls the database directly for the Historic Transaction), and the connection from amlcore to the database is severed because of an idle connection, try adjusting the SAS Anti-Money Laundering database connection parameters.

• Test on Borrow Setting:
  • “java_option_test_on_borrow”
  • “-Dtomcat.jdbc.pool.testOnBorrow=true”
• Validation Interval Setting:
  • “java_option_validation_interval”
  • “-Dtomcat.jdbc.pool.validationInterval=30000”

The steps are as follows:

1. . source /opt/sas/viya/config/consul.conf
2. export CONSUL_HTTP_TOKEN=$(sudo cat /opt/sas/viya/config/etc/SASSecurityCertificateFramework/tokens/consul/^
   default/client.token)
3. /opt/sas/viya/home/bin/sas-bootstrap-config kv write --force config/amlcore/jvm/java_option_test_on_borrow "-Dtomcat.jdbc.pool.testOnBorrow=true"
4. /opt/sas/viya/home/bin/sas-bootstrap-config kv write --force config/amlcore/jvm/java_option_validation_interval "-Dtomcat.jdbc.pool.validationInterval=30000"
5. sudo systemctl restart sas-viya-amlcore-default (run this on each microservices machine)