Last updated on JUNE 01, 2017
Applies to:Oracle Knowledge - Version 126.96.36.199 to 188.8.131.52 [Release 8.4 to 8.5]
Information in this document applies to any platform.
When making runtime requests from any application there is a control block (giml) that is passed with the transaction. The giml is what allows the runtime to be stateless, making it so that any runtime can process the next request. It provides transaction information that makes the processing more efficient.
When runtime requests fail with NO_SUCH_TRANSACTION the information in the request or response does not match the giml. There are two main reasons this can happen.
1. The transactions process out of order
2. The consistency of the main parameters is lost, most commonly, JSessionID. It could be the request information has changed. Search Runtime Error - No_such_transaction When Request Parameters Change (Doc ID 1388270.1)
[219150 Consumer-default-1(33366)] Event(Code=EXECUTE_REQUEST_FAILED, id=#6B1614I33366P-1) with Error occurred at 5/12/15 11:27 AM: Execution of request 1533 failed, cause: com.inquira.request.RequestProcessorException: [Consumer-default-1 @ Tue May 12 14:27:35 EDT 2015] (REQUEST_PROCESSOR_HANDLER_FAILED)
com.inquira.request.RequestProcessorException: [Consumer-default-1 @ Tue May 12 14:27:35 EDT 2015] (REQUEST_PROCESSOR_HANDLER_FAILED)
[219150 WrapperStartStopAppMain (33367)] Error processing request encountered. Cause: com.inquira.request.HandlerException: [Consumer-default-1 @ Tue May 12 14:27:35 EDT 2015] (NO_SUCH_TRANSACTION 1230520659)
Causing: com.inquira.request.HandlerException: [Consumer-default-1 @ Tue May 12 14:27:35 EDT 2015] (ERROR_GETTING_RESULTS)
Oracle knowledge does not support multiple requests from the same user at a time. The user should not search a second time in the same browser before the first search finishes.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms