Project

General

Profile

Defect #408

The busy plugin seems to be unreliable when running with Servoy v6.0.4.

Added by Corey Puffalt over 13 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Start date:
01/13/2012
Due date:
% Done:

0%

Estimated time:
Browser (if web client):
IE/Firefox/Chrome

Description

We're seeing a lot of issues where our background processes are completing and we call unblock() but the modal Cancel button remains displayed on screen (this is with Webclient). The user is able to click Cancel to dismiss the blocker but meanwhile the process actually DID complete properly. Even worse some things such as a call like application.showURL() which we call in some cases at the end of a process (after calling unblock()) executes but doesn't take effect until some time later when the user executes another process that uses the busy plugin (very strange). I would guess this has something to do with concurrency/visibility of data being passed across threads or something. I can't say for sure that this is actually a bug in busy plugin or a bug in Servoy itself but thought it best to post it here first.

We're not 100% sure that the problem started with v6.0.4 since that's the first version that we ran in production. (We did test earlier releases of v6.0.x but didn't see it in light testing/development.)

Thanks.

History

#1

Updated by Corey Puffalt over 13 years ago

NOTE: Sorry, I think I missed mentioning that the failure scenarios described above are completely random. It does seem however, that once it fails once it will continue to fail until the user logs out and logs back in with a new session.

#2

Updated by Patrick Talbot over 13 years ago

  • Status changed from New to In Progress
#3

Updated by Corey Puffalt over 13 years ago

It looks like this issue was self-inflected. HTTP requests to the "busy cancel" servlet were being blocked (returning error code 404) so when the user clicked the Cancel button in webclient the cancellation was never signalled properly to the server. I'll open a separate request to add some error checking to the javascript code to check for the servlet return status.

I don't seem to have permission to close this ticket but feel free to do so.

Thanks.

#4

Updated by Patrick Talbot over 13 years ago

  • Status changed from In Progress to Closed

Thanks for the update, I'm closing this one but feel free to open another one for the various changes we talked about in http://forum.servoy.com/viewtopic.php?f=15&t=17610&p=95067
I'll do that asap.

Also available in: Atom PDF