AnsweredAssumed Answered

Adaptive Authentication issue

Question asked by RSA Admin

on Jul 20, 2015
Latest reply on Mar 1, 2016 by Somi Reddy Devireddy

Like • Show 0 Likes0
Comment • 2

We are usign RSA API in application to check the risk analyz. But sometimes we are getting some timout error. Below mentioed the

RSA server log.

015-07-10 01:35:25,402 WARN [[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [] [] [com.passmarksecurity.utils.Stopwatch] - <Elapsed time for Commiting API transaction : 517 ms>

2015-07-10 01:35:25,403 WARN [[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [] [] [com.passmarksecurity.utils.Stopwatch] - <Elapsed time for analyze ws method execution : 43409 ms>

2015-07-10 01:35:25,402 WARN [[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'] [] [] [com.passmarksecurity.utils.Stopwatch] - <Elapsed time for Commiting API transaction : 529 ms>

Anyone faced issues like this?

Somi Reddy Devireddy Mar 1, 2016 2:03 PM

Correct Answer

This is not a timeout, but a slow response from RSA AA. It can be a timeout for the application that is waiting for the response from RSA.

Slow response can be due to few of the following reasons,

- If active thread count between Application server and the database exceeds the Max Connection limit

- Slow response from the database (check the AWR reports from database)

- Network related

See the reply in context

No one else had this question

Outcomes

2 Replies

A93C4COVonAywLoSqjSqM3sgPbNT8QnwbHnIiluCYM0= Feb 16, 2016 12:05 PM
Mark Correct
Correct Answer
I have seen these warning messages but they did not result in timeouts. They occur when the analyze call reaches a preset threshold. The 52 second analyze could be indicative of a problem. If this is a VM environment, check your host and cores in the database. If there are too many cores in a VM environment and the environment is loaded, it might result in the database being swapped out during the analyze call.
Like • Show 0 Likes0
Actions
Somi Reddy Devireddy Mar 1, 2016 2:03 PM
Unmark Correct
Correct Answer
This is not a timeout, but a slow response from RSA AA. It can be a timeout for the application that is waiting for the response from RSA.
Slow response can be due to few of the following reasons,
- If active thread count between Application server and the database exceeds the Max Connection limit
- Slow response from the database (check the AWR reports from database)
- Network related
Like • Show 0 Likes0
Actions

Adaptive Authentication issue

Outcomes

Related Content

Recommended Content