This is from the past where just a couple people were having issues with
IBM's SSL APIs.
A customer talked with IBM and here is what they said:
The application can set GSK_V3_SESSION_TIMEOUT to 0 using the
gsk_attribute_set_numeric_value() API to disable caching for the
application. It must be set the value on the secure environment after the
gsk_environment_open() and before the gsk_environment_init(). See
additional information on the API.
If the application uses an Application ID in DCM, the customer can override
that value on the Application ID secure session property "Secure Session
Cache Time to Live in Seconds" and then they would not need an update to
the application source code.
Now, I find this odd because:
1) It only happens to .001% of calls made with GETURI/HTTPAPI
2) It only started happening recently
3) The part about the application ID makes no sense to me (it is early,
Just something to put out there. I am not sure it will help at all, but
I'm willing to try to help my customer that is having an issue.
Bradley V. Stone
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any Cloud
As an Amazon Associate we earn from qualifying purchases.