This content has been marked as final. Show 8 replies
Okay, so it's not the first request.
It's a request for a specific pages that breaks down.
Can you narrow down the issue by selectively (one by one) set each reagion to "never" (under conditions).
As soon as your page runs again, you know where the issue lies.
If this question is answered, please mark the thread as closed and assign points where earned..
pj**** wrote:Why are you making your users sit and stare at the screen for 10 minutes?
I encounter some problem using Apex listener standalone mode, if the query running about 10 mins, some error
For long-running processes, use DBMS_JOB or APEX_PLSQL_JOB to run the process in the background (on the server) so the user can go and do something useful in the meantime.
It's has nothing to do with the region, the report can run if we using oracle http server, the timeout issue appear only when we use standalone apex listener.Judging from the error message you receive ( com.sun.grizzly.http.KeepAliveThreadAttachment timedOut ...) the embedded JEE Container (Grizzly) used in Standalone Mode terminated your idle request thread, probably due to some thread timeout default. This is not configurable, at least not in any documented or undocumented config/properties file.
Note that Standalone Mode is not recommended for production environments. The fact that OHS doesn't care about hanging requests doesn't mean it's good style to create such. If you don't want to consider Mortens really useful advice to move long running reports into a database job in background, you should at least deploy APEX Listener to a regular JEE Container. Most of them will have other defaults for idle threads or at least offer you to configure the idle timeout.