Tl;dr: change persistent-con-timeout in the ISVA [server] stanza from 5 to a value larger than 6

We were routing traffic from various clients to an IBM Security Verify Access (ISVA, formerly ISAM) Reverse Proxy (WebSEAL) via an AWS Load Balancer (ALB).

tl;dr Run support > purge from the CLI to delete all temporary files

I recently tried to create a Support file on an ISAM/ISVA virtual appliance, but after a few minutes it failed (“The system failed to create the support file”).

I was given a Hotfix by IBM when we were investigating a memory utilisation problem with IBM Security Verify Access (ISVA, formerly IBM Security Access Manager, ISAM), earlier this year. This Hotfix generated a set of resource monitor diagnostic files every 20 minutes, so