HTTP 500 error with REST API REQUEST ROUTED TO ALREADY COMPLETED SESSION
Last updated on DECEMBER 12, 2017
Applies to:Siebel CRM - Version 16.1 [IP2016] and later
Information in this document applies to any platform.
On : 16.1 [IP2016] version, Siebel EAI
Customer is in the process of carrying out load testing (via SoapUI) with a small subset of users to evaluate the performance and stability of the REST API interface using a business services. There are 10 users in total. Each user submits 3 queries simultaneously, than waits 15 seconds before starting over. After about 30 minutes, some of the requests error out with an HTTP 500 error code.
Customer observed that because the same user submits 3 queries at almost the same time, Siebel creates 3 EAI sessions. The first 2 sessions will timeout eventually and the last one keeps processing the incoming requests.
After some analysis of the log files, it appears that the error coincides with a timeout of the EAI OM session. Our hypothesis is that a request is occasionally sent to an EAI session that already expired. Reviewing the siebel-rest.log file, we see the following:
The issue can be reproduced at will with the following steps:
1. Load Test using SOAPUI or JUNIT
2. 10 users, each user submits 3 queries simultaneously
3. Wait for 15 seconds and start over
4. After 30 minutes some of requests errors out with HTTP 500
The issue has the following business impact:
Due to this issue, customer is seeing a possible issue with higher volumes.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms