Webkit timeout kills long running tasks

Hi There
We have just been forced to refactor/recode a significant
portion of one of our AIR based RIA's due to an arbitrary decision
made by the Webkit team to restrict all XML HTTP requests via a
hard coded, hidden timeout of 60 seconds. This decision not only
affects AIR but also affects Safari and other browsers based upon
Webkit.
Our application performs complex analytic queries which may
run to a few minutes. Whilst long synchronous requests are not
generally a good idea for web based solutions, we believe that RIA
intranet applications are a completely different ball game and
should not be subject to arbitrary constraints such as these with
no flexibility or warning. We would not see this behaviour in Java
/ C# or other such application languages, so why are we seeing this
in Adobe AIR?
Our MD has understandably questioned the suitability of Adobe
AIR for future developments of enterprise RIA's, and we are all
naturally concerned about other "features" being added or removed
to the Adobe AIR functionality, even indirectly and whether in fact
we can rely upon Adobe to monitor the stability of their runtime.
We don't believe it is acceptable for us to tell our customers that
it was the fault of a component nested within multiple layers of
the runtime outside of our control and believe that it is equally
unacceptable for Adobe to stand by and claim the same.
We are excited about the prospects of investing in Adobe AIR
for delivering rapid RIAs to our customers, but are we to expect
similar show stoppers to arise over the coming months or even
years, and can we trust the Adobe runtime as an "In production"
solution going forward.
Mark Robertshaw
Director
Oxford Information Labs
http://www.oxil.co.uk

Mark,
Thanks for bringing this to our attention. We, as I'm sure
you realize, aren't claiming that this sort of thing is ok. And we
do work hard to maintain the stability of the runtime. However, it
can be difficult to know a priori everything that we need to keep
an eye on. That's one of the reasons we have forums like this one
and we very much appreciate this kind of feedback.
As for this particular issue, I'll just point out that you
might consider taking advantage of the flash.net.* APIs to manage
your network request, at least as a temporary workaround.
regards,
Oliver Goldman | Adobe AIR Engineering

Similar Messages

Does win8/8.1/10 kill long-running programs automatically as stated in specs? reasons why?

does win8/8.1/10 kill/end-task long-running programs automatically as stated in specs? how specifically does it detect a locked-up process?
has this been put into windows 7 at any time to make it similar to windows 8?
Please supply accurate answers. thank you.
My understanding the reason for this change was to handle locked-up programs.
I do have a number of long-running processes. some examples of mine and scenarios for other users:
simulations on a Workstation or HPC Server
doing a directory tree walk on a hard disk with >=1TB of data
reference articles I have found on the subject:
windows 7
http://windows.microsoft.com/en-us/windows/exit-program-not-responding#1TC=windows-7
windows 8
From some of what I understand, you can also get the "Program Not Responding" or similarly titled dialog box when:
bug in the source code of the program in question. for instance, while(1){} such as forever loops (win7)
similar program bug when declaring a function one way but defining it a different way and then calling it (mismatch in function signature) (win7)
similar to above with DLLs in using MSVCRT*.DLL or other
(?) can't remember for sure on this, but I think some badly formed calls or it was invalid values or data type mismatch to Win32 API can do this from buggy code. (win7)
for (x=0; x < 16777216; x++) {your code here...} in other words, large values for loop termination (win7)
this is a repost of http://answers.microsoft.com/en-us/windows/forum/windows_8-performance/does-win88110-kill-long-running-programs/d35c3c9e-c6f4-4bbf-846a-2041bf2167a0?tm=1427518759476
here due to a request to do so.

does win8/8.1/10 kill/end-task long-running programs automatically as stated in specs? how specifically does it detect a locked-up process?
has this been put into windows 7 at any time to make it similar to windows 8?
Please supply accurate answers. thank you.
My understanding the reason for this change was to handle locked-up programs.
Hi Jim,
First, I have to admit that I'm not fully understanding the question, If a program is not responding, it means the program is interacting more slowly than usual with Windows, typically could be a confliction of software or hardware resources between
two programs, lack of system resources, or a bug in the software or drivers. In that case, we can choose to wait or end the program. This design is similiar in Windows 7, Windows 8 and other OS.
For deeper analysis, system determines whether the system considers that a specified application is not responding using a "IsHungAppWindow function",
https://msdn.microsoft.com/en-us/library/ms633526.aspx
And this link also give some explanation: Preventing Hangs in Windows Applicationshttps://msdn.microsoft.com/en-us/library/windows/desktop/dd744765%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
While I'm not a developer, to better understand this, I recommend you contact members in the MSDN Forum:
https://social.msdn.microsoft.com/Forums/en-US/home
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Script to kill long running reports in OBIEE

Hi
I have requirement to kill long running reports . I am using OBIEE version 10.1.3.4.0 which has a bug where it is not taking query limits governor and the reports are not getting killed if i am setting that parameter in RPD.
Oracle support has advised me to upgrade to next version, but for now, i cannot upgrade.
Can anyone suggest me script to run on obiee app server that can kill long running reports on obiee and database server.
I have AIX server and all reports run on database with same functional ID that is being used for ETL as well to Analytics database.

Shikhs17 wrote:
Hi
I have requirement to kill long running reports . I am using OBIEE version 10.1.3.4.0 which has a bug where it is not taking query limits governor and the reports are not getting killed if i am setting that parameter in RPD.
Oracle support has advised me to upgrade to next version, but for now, i cannot upgrade.
Can anyone suggest me script to run on obiee app server that can kill long running reports on obiee and database server.
I have AIX server and all reports run on database with same functional ID that is being used for ETL as well to Analytics database.Do you want to enforce the limitation on the database to automatically kill running sessions that run over specific period of time?

Long Running Task ...

I have a requirement where a user kicks off a long running task ( usually 2
to 5 minutes). I want to show a 'In Progress' message while the task is
procesing. The long running process needs to be passed an ArrayList. To
achieve this , I use a ServerSessionPool and a QueueListener.
In the servlet I assign a unique ID to the task , send a JMS message ( with
the serialized ArrayList) on the queue. The servlet returns to the
user saying 'In progress' message . When the user hits refresh , I want to
know if the message has been consumed ( or the process is over ) and
I need get the 'processed' ArrayList back in the servlet. How do I achieve
this ?
Thanks in advance
~ J

instead of asking the user to hit refresh, you can have the browser
automatically refresh the page every X seconds by putting in a header
parameter.
I forgot the actual parameter, but this is pure HTML so look it up in that
spec
Filip
~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[email protected]
www.filip.net
"Cameron Purdy" <[email protected]> wrote in message
news:[email protected]..
http://dima.dhs.org/misc/LongRunningTask.jsp
Peace,
Cameron Purdy
Tangosol Inc.
<< Tangosol Server: How Weblogic applications are customized >>
<< Download now from http://www.tangosol.com/registration.jsp >>
"John Doe" <[email protected]> wrote in message
news:[email protected]..
I have a requirement where a user kicks off a long running task
usually
2
to 5 minutes). I want to show a 'In Progress' message while the task is
procesing. The long running process needs to be passed an ArrayList. To
achieve this , I use a ServerSessionPool and a QueueListener.
In the servlet I assign a unique ID to the task , send a JMS message (with
the serialized ArrayList) on the queue. The servlet returns to the
user saying 'In progress' message . When the user hits refresh , I want
to
know if the message has been consumed ( or the process is over ) and
I need get the 'processed' ArrayList back in the servlet. How do Iachieve
this ?
Thanks in advance
~ J

Long running task - what do you show?

There are a lot of discussions about long running tasks. But what do you show in the GUI while these tasks are running? The obvious choice is the standard hour-glass cursor, or a JProgressBar. I'm sure though that there must be other creative alternatives, like a Java2D animation for example.
Would people like to share what they show during long running tasks?

I have both Fusion and Parallels on all my machines. For Windows7, I have found that
the most recent version of Parallels is much faster and efficient than Fusion. With
XP, either one seems just fine. Also, if Linux is a future consideration, Fusion seems
to be the better bet. Parallels has some USB issues when running Linux.
I have tried Virtual Box, but for my uses, hardware and firmware engineering, it has
been problematic.
Since you mentioned Autocad, I would not recommend VirtualBox. Either of Fusion
or Parallels should serve you well. However, graphics performance does seem a
bit snappier with Parallels than with Fusion.

SQL Developer Locking up/Unable to Cancel long Running tasks

I have had the same problem with a number of versions of SQL Developer (and version 3.2.09). It occurs when trying to cancel a long-running PL-SQL Function or procedure that has been started by 'Run' in SQL Developer.
Select Terminate in Run Manager does not stop the job. Nor does trying to exit SQLDeveloper; it asks whether I want to kill the job; then doesn't kill it and doesn't exit either.
Trying to save modifications to anything the process depends on results in SQL Developer locking for ~20 minutes.
I have to resort to getting a DBA to manually kill the process at the server.
Is there any possiblity of a workaround or a way of making the PL/SQL not lock so it can be terminated please?
Thanks

I have had the same problem with a number of versions of SQL Developer (and version 3.2.09). It occurs when trying to cancel a long-running PL-SQL Function or procedure that has been started by 'Run' in SQL Developer.
Select Terminate in Run Manager does not stop the job. Nor does trying to exit SQLDeveloper; it asks whether I want to kill the job; then doesn't kill it and doesn't exit either.
Trying to save modifications to anything the process depends on results in SQL Developer locking for ~20 minutes.
I have to resort to getting a DBA to manually kill the process at the server.
Is there any possiblity of a workaround or a way of making the PL/SQL not lock so it can be terminated please?
Thanks

NiDAQ 6008 -- Long running task stability

I have a small C program using nidaqmxbase, based on the example code provided.
This runs with a usb connected 6008 on a Red Hat Linux machine. The task is simple, read the analog voltage (differential, reference source 2.5v range) from one channel at 1000hz in blocks of 50 samples. The results are placed into network messages to send to another program for analysis.
This program works fine, but has a long run-time stability issue when left running for more than about 24 hours continuously (and, for my application I need to capture in realtime 24/7 indefinitly). The symptom observed is that the 6008 stops returning data -- and "lsdaq" shows that the device is no longer seen by the system. Sometimes the green LED stops blinking as well. Has the DAQ crashed? Did some counter overflow and cause the driver to malfunction? I am able to restore function only by physically disconnecting and re-connecting the 6008.
Thank you
Andy.

Hi aws-
It sounds like the problem you are seeing could be related to bus powering or resource conflicts on your system. The fact that the failure results in total loss of connectivity with your device certainly seems to indicate a hardware problem.
You said your code is based on the example code; please verify if an unmodified shipping example fails similarly. If so, please let us know which program fails and I will attempt to replicate the issue here. Do you see this problem on multiple computers and/or with multiple USB-6008 devices?
Thanks-
Tom W
National Instruments

OHS Webserver Timeout for long running requests

Hi,
I have applications which have some pages which make requests that take longer than 60 seconds to complete (say a report that takes more than a minute). I know that this may not be considered ideal to make a user wait this long, but the users are ok with this. And I know that there are work arounds, but I'd like to research if this problem is simply one of configuration before implementing such work arounds.
I have checked that the apache webserver timeout is set to the default of 300 seconds in httpd.conf, so this is not the issue. I have checked the other conf files (both for Apache and mod_plsql) on the webserver and these have been left with default settings, none of which suggest a 60 second limitation.
The databases being connected to are 10.1 and 10.2. The apex versions are 2.0 and 2.2.
To further test this issue I created a page in the app that submits a sleep request using a variable wait time (P1_WAIT). When P1_WAIT is set to 59 seconds it runs successfully. However, when I set P1_WAIT = 60 seconds (or greater) it timesout (the process continues successfully on the database, it's just that the OHS disconnects). I see no helpful information in either the apache or mod_plsql logs.
Any ideas?
begin
DBMS_LOCK.SLEEP(to_number(:P1_WAIT));
end;

Hello. We had a problem with long running web services as well. Main culprit is the httpd.conf Timeout setting. If the service took longer than 5 minutes to run, BPEL would get a generic remoteFault with a generic empty detail message. We worked with Oracle support and together figured this out: 1) the server hosting the web service needs to have the $ORACLE_HOME/Apache/Apache/conf/httpd.conf Timeout value set longer than the longest running web service - the default value is 5 minutes; 2) the BPEL partner link can be given the "timeout" property (ends up in the bpel.xml partnerlinkBinding section) which controls how long BPEL is willing to wait before giving up on the web service call. If this second limit is reached before the web service has completed you get a useful remoteFault, showing "java.net.SocketTimeoutException: Read timed out"

How to delay a long running tasks start until display is updated?

I am having a problem in that a progress bar I want to use to show progress of a long running background process is not showing up for a long time (up to 10 seconds) after the long running process is started. This is in an AIR application and the background process is an external native process, so once it is launched the UI thread is free to run, but the launch of the process can take time.
Below is the current state of the relevant code.
In addition to the current format I have also tried using the CREATION_COMPLETE, EXIT_FRAME and RENDER events with the same results.
If I up the value in setTimeout to 500ms the progress bar displays quickly, but I would prefer to not delay the launch of the background process for no reason.
If I comment out the loadPorject call the progress bar is displayed instantly.
Any help is appreciated.
private function continueLoad(evt:Event):void
     // We are about to start some potentially long running process
     CursorManager.setBusyCursor();
     curPopup = new SyncProgress();
     curPopup.addEventListener(Event.ENTER_FRAME, popupLoadedHandler);
     PopUpManager.addPopUp(curPopup, parentView, true);
     PopUpManager.centerPopUp(curPopup);
     curPopup.stage.invalidate();
private function popupLoadedHandler(event:Event):void
     curPopup.removeEventListener(Event.ENTER_FRAME, popupLoadedHandler);
     setTimeout(function():void{syncManager.loadProject(mainViewModel.selectedUserItem.id,proj ectFile.nativePath,overwrite);},0);

DBMS_SCHEDULER is very powerful and can be a bit unwieldy. I tend to use DBMS_SCHEDULER for jobs which are purely 'in the database' i.e. not specifically APEX-related - in addition, I find it's better for stuff that needs to be run regularly without human intervention (some sort of refresh process, daily cleanup etc).
If you are intending to run this process from APEX as a pseudo "on demand" process (i.e. generated by a user request) and have quite simple requirements (e.g. there's no dependencies on other jobs), it might be worth checking out the apex scheduling API - namely the package APEX_PLSQL_JOB:
http://download.oracle.com/docs/cd/E14373_01/apirefs.32/e13369/apex_plsql_job.htm#BGBCJIJI
It generates a unique job number which you can use to reference its progress - plus it's much simpler to use.
p.s. using DBMS_SCHEDULER, yes the job name has to be unique but you can generate one by either using a sequence or data not likely to be repeated, like the current timestamp.

How to extend the timeout for long running queries

I unfortunately have a query that needs to run for 2 hours (long story) to load a year's worth of data into PowerPivot (RTM). PowerPivot stops with an error after running for 1 hour. I tried changing the "General Timeout" setting from 0 to 28800
(8 hours) in the SQL conneciton settings (native client 10.0) and I also managed to get the server owner to increase the "Query Timeout" setting in the SQL Server's Connections dialog but PowerPivot still errors out after 1 hr.
A workaround will be to use SSIS to run the query and store the result in another database but I'd rather not do that if I don't have to.
Error Message
The refresh operation failed because the source data base or the table does not exist, or because you do not have access to the source
More Details:
OLE DB or ODBC error: Query timeout expired; HYT00.
An error occurred while processing the 'XXXX' table.
The operation has been cancelled.
Is there any other place where the timeout can be set or controlled that I've missed?

Try
1) Setting "ExternalCommandTimeout" in the server configuration file (msmdsrv.ini) to a multiple of seconds you want (in this case >7200, by default it is 3600(1hr)).
2) Restart the server.
3) Refresh the data.
Please let me know, if this doesn't work.

Killing long running SQl automatically

I want to put a restriction on my database, if a sql query is running for more then 15 min, then killing this automatically. If this is possible kindly let me know.

Hi,
yes you can do that, use Resource Manager for that like described below:
http://www.pythian.com/blog/oracle-limiting-query-runtime-without-killing-the-session/
Best regards,
Nikolay

EJB3 long running task handling

Dear all,
Please help me on this,
We developed application using struts2 ejb3webservice.runing on jboss5.
This is a hotel reservation system. User make a request to get the hotel listing that is available, ejb3 Stateful get the connection to the web service and retrieve the hotels and process with the pricing then send back to the struts to display it to user. This happens only once for a search. The problem here is the EJB processing takes lots of time if it is more hotels available.
So I am expecting to implement a solution such as, if the first 10 hotels found return it to user and display while other hotels are processing background In the EJB. Then I can update those results with the user while he/her running over pagination.
Is this correct solution? If so how can I implement such a thing using EJB? any suggestion please?
Thanks
Emil

I am not a struts expert but I think that if you want a background processing you should use a Message Driven Bean.
When you receive the client request in your Session Bean, you send a message to the MDB and then continue. While the MDB is processing the result it can send partial data back to the Session Bean.
Hope it helps.

How to kill long running package?

Hi,
Oracle version : 11.0.1.7.0
OS: IBM-AIX
I have executed health check package "DBMS_HM.RUN_CHECK" But my Database performance badly degraded. I wish to end the execution of the package.
How can i kill it?
Thanks
KSG

-- show PROCESS id for all the active sessions
select p.spid,s.sid,s.serial#,s.username,s.status,s.client_identifier,s.last_call_et,p.program,p.terminal,logon_time,module,s.osuser
from V$process p,V$session s
where s.paddr = p.addr and s.status = 'ACTIVE' and s.username not like '%SYS%';
Find out the session and kill the session.
alter system kill session 'sid,serial#';
alter system kill session '32,87568';
Regards
Asif kabir

Handle long-running EDT tasks (f.i. TreeModel searching)

Note: this is a cross-post from SO
http://stackoverflow.com/questions/9378232/handle-long-running-edt-tasks-f-i-treemodel-searching
copied below, input highly appreciated :-)
Cheers
Jeanette
Trigger is a recently re-detected SwingX issue (https://java.net/jira/browse/SWINGX-1233): support deep - that is under collapsed nodes as opposed to visible nodes only, which is the current behaviour - node searching.
"Nichts leichter als das" with all my current exposure to SwingWorker: walk the TreeModel in the background thread and update the ui in process, like shown in a crude snippet below. Fest's EDT checker is happy enough, but then it only checks on repaint (which is nicely happening on the EDT here)
Only ... strictly speaking, that background thread must be the EDT as it is accessing (by reading) the model. So, the questions are:
- how to implement the search thread-correctly?
- or can we live with that risk (heavily documented, of course)
One possibility for a special case solution would be to have a second (cloned or otherwise "same"-made) model for searching and then find the corresponding matches in the "real" model. That doesn't play overly nicely with a general searching support, as that can't know anything about any particular model, that is can't create a clone even if it wanted. Plus it would have to apply all the view sorting/filtering (in future) ...
// a crude worker (match hard-coded and directly coupled to the ui)
public static class SearchWorker extends SwingWorker<Void, File> {
    private Enumeration enumer;
    private JXList list;
    private JXTree tree;
    public SearchWorker(Enumeration enumer, JXList list, JXTree tree) {
        this.enumer = enumer;
        this.list = list;
        this.tree = tree;
    @Override
    protected Void doInBackground() throws Exception {
        int count = 0;
        while (enumer.hasMoreElements()) {
            count++;
            File file = (File) enumer.nextElement();
            if (match(file)) {
                publish(file);
            if (count > 100){
                count = 0;
                Thread.sleep(50);
        return null;
    @Override
    protected void process(List<File> chunks) {
        for (File file : chunks) {
            ((DefaultListModel) list.getModel()).addElement(file);
            TreePath path = createPathToRoot(file);
            tree.addSelectionPath(path);
            tree.scrollPathToVisible(path);
    private TreePath createPathToRoot(File file) {
        boolean result = false;
        List<File> path = new LinkedList<File>();
        while(!result && file != null) {
            result = file.equals(tree.getModel().getRoot());
            path.add(0, file);
            file = file.getParentFile();
        return new TreePath(path.toArray());
    private boolean match(File file) {
        return file.getName().startsWith("c");
// its usage in terms of SwingX test support
public void interactiveDeepSearch() {
    final FileSystemModel files = new FileSystemModel(new File("."));
    final JXTree tree = new JXTree(files);
    tree.setCellRenderer(new DefaultTreeRenderer(IconValues.FILE_ICON, StringValues.FILE_NAME));
    final JXList list = new JXList(new DefaultListModel());
    list.setCellRenderer(new DefaultListRenderer(StringValues.FILE_NAME));
    list.setVisibleRowCount(20);
    JXFrame frame = wrapWithScrollingInFrame(tree, "search files");
    frame.add(new JScrollPane(list), BorderLayout.SOUTH);
    Action traverse = new AbstractAction("worker") {
        @Override
        public void actionPerformed(ActionEvent e) {
            setEnabled(false);
            Enumeration fileEnum = new PreorderModelEnumeration(files);
            SwingWorker worker = new SearchWorker(fileEnum, list, tree);
            PropertyChangeListener l = new PropertyChangeListener() {
                @Override
                public void propertyChange(PropertyChangeEvent evt) {
                    if (evt.getNewValue() == SwingWorker.StateValue.DONE) {
                        //T.imeOut("search end ");
                        setEnabled(true);
                        ((SwingWorker) evt.getSource()).removePropertyChangeListener(this);
            worker.addPropertyChangeListener(l);
            // T.imeOn("starting search ... ");
            worker.execute();
    addAction(frame, traverse);
    show(frame)
}

At the end of the day, it turned out that I asked the wrong question (or right question in a wrong context ;-): the "problem" arose by an assumed solution, the real task to solve is to support a hierarchical search algorithm (right now the AbstractSearchable is heavily skewed on linear search).
Once that will solved, the next question might be how much a framework can do to support concrete hierarchical searchables. Given the variety of custom implementations of TreeModels, that's most probably possible only for the most simple.
Some thoughts that came up in the discussions here and the other forums. In a concrete context, first measure if the traversal is slow: most in-memory models are lightning fast to traverse, nothing needs to be done except using the basic support.
Only if the traversal is the bottleneck (as f.i. in the FileSystemModel implementations of SwingX) additional work is needed:
- in a truly immutable and unmodifiable TreeModel we might get away with read-only access in a SwingWorker's background thread
- the unmodifiable precondition is violated in lazy loading/deleting scenarios
there might be a natural custom data structure which backs the model, which is effectively kind-of "detached" from the actual model which allows synchronization to that backing model (in both traversal and view model)
- pass the actual search back to the database
- use an wrapper on top of a given TreeModel which guarantees to access the underlying model on the EDT
- "fake" background searching: actually do so in small-enough blocks on the EDT (f.i. in a Timer) so that the user doesn't notice any delay
Whatever the technical option to a slow search, there's the same usability problem to solve: how to present the delay to the end user? And that's an entirely different story, probably even more context/requirement dependent :-)
Thanks for all the valuable input!
Jeanette

Unable to Kill the Consolidation task for HFM application

User is unable to kill the Consolidation task in HFM application. Consolidation process which usually takes 2 mins has been showing status as running @79% since 4-6 hrs. User ID is has the provisioning manager, lock Data and unlock data provisions in Shared Services. The stop task button in the Running Tasks list is not enabled . Our Support team has advanced user access which is not also able to stop the task. Please note Admin access is restricted and not allowed for such tasks.

I would check the HFM Log to see if you find anything referring to locked / blocked records.
If your HFM app is killed in the middle of consolidating or performing other activities that requires it to 'lock' a segment of memory in the database, that 'lock' is still held on those data points when the application restarts.
If you then try to perform another consolidation and it hits one of those locked data points, it will sit there for a very long amount of time waiting for the 'lock' to clear.
I forget the exact error message that you will find in the log AND I forget the timeout period; however, it sucks having to wait through that.
The other possibility that comes to mind is that the consolidation really aborted and the status didn't update. (once again check the logs)
Charles

Webkit timeout kills long running tasks

Similar Messages

Maybe you are looking for