Avoid Stuck Threads Caused by User Interaction on Slow Requests (Doc ID 1918388.1)

Last updated on AUGUST 04, 2016

Applies to:

Oracle JDeveloper - Version 11.1.1.0.2 and later
Information in this document applies to any platform.

Goal

Currently if a user clicks from same browser window while previous request is still running, the new request will be blocked for up to 10 min. This could result in stuck threads in the server but these are stuck simply because the original request is slow. In the worst case, an impatient user could create many stuck threads to cause a server restart or in a warning status.

When it gets to this state most users are unable to access the web application.

A restart resolves the issue, but it returns after a number of days.

Solution

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