Using Fiddler to assist in with front end JSESSIONID issues
Last updated on JANUARY 02, 2018
Applies to:Oracle Knowledge - Version: 220.127.116.11
Information in this document applies to any platform.
There is a short 8 minute training stream and doc for setting up and using Fiddler.
JSESSIONID is the conventional name of a cookie used by Java application servers. The value of this cookie is an identifier that is used on an application server to find the user's session data, i.e. the user data from their other recent HTTP requests.
When it appears that the JSESSIONID is not being maintained or the parameters in the session cookie are getting lost, it is helpful to monitor the HTTP header information as browser interaction takes place. By testing with the browser and Fiddler you can determine where the changes are being made. In Fiddler the the HTTP request and response headers are visible. As you test InfoCenter in the browser you can see if the values are changing.
Runtime requests require that the JSESSIONID be maintained from user request to user request. If this is not happening it will cause a NO_SUCH_TRANSACTION error on the runtime for subsequent search requests like paging or filtering. If the JSESSIONID is being changed this will cause a empty or bad prior transaction id.
There are a number of known issues that cause the NO_SUCH_TRANSACTION runtime error message. Please see knowledge article 1388270.1 for more information.
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