In OBDX 21.1, Whenever Users Try to Log In With Incorrect Credentials, The J_Security_Check Rest Call Fails And The Thread Goes Into a Hogging State.
(Doc ID 2853506.1)
Last updated on MAY 16, 2023
Applies to:
Oracle Banking Digital Experience - Version 21.1.0.0.0 to 21.1.0.0.0 [Release 21]Information in this document applies to any platform.
Symptoms
On : 20.1.0.0.0 version, Implementation Support
ACTUAL BEHAVIOR
---------------
Threads go into hogging due to wrong login attempts, this is due to /digx/j_security_check call failure.
Hogging degrades overall application performance
EXPECTED BEHAVIOR
-----------------------
Threads should not go into hogging due to wrong login attempts, this is due to /digx/j_security_check call failure.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Browse the login screen
2. Enter the username and incorrect password
3. /digx/j_security_check rest call failed with status code 403.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, overall application performance degrades.
Changes
No changes done to hardware/product or environment cause this issue.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |