The busy cursor is set when a RemoteObject operation is invoked using CursorManager.setBusyCursor(). It's removed when a result or fault for the invocation is returned, via a call to CursorManager.removeBusyCursor().
If you're not receiving a result or fault event, that would explain why the busy cursor is not being unset. RemoteObject, and the other RPC-related client components, define a 'requestTimeout' property that represents the number of seconds the RemoteObject will wait for a response or fault from the server/network before giving up and just faulting the call locally on the client. You may want to enable this property, in order to abort requests that are lost in the network (although this sort of failure should be very intermittent and if it's common you should do more debugging or your network to attempt to determine why the requests are dropping). Best, Seth ________________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Maciek Sakrejda Sent: Monday, January 14, 2008 9:37 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] LCDS AMF call not firing result events, busycursor does not go away Ok, I suppose there may be no answer since this is not exactly a minimal test case. Let me simplify the question: Under what circumstances would a RemoteObject AMF call not restore the cursor from the 'busy' state? Relevant source: override public function init():void { // create service _remote = new RemoteObject(); _remote.showBusyCursor = true; _remote.destination = "fooService"; _remote.addEventListener("result", handleResultReceived); _remote.addEventListener("fault", handleFault); var params:Object = new Object(); for each (var f:Filter in _filterCollection.filters) { if (f.isServerFilter) { f.refreshValue(); params[f.field] = f.value; } } _remote.executeStaticQuery(super._queryId, params, super._serverTransformer); } Again, this error is not consistently reproducible: it works most of the time, but occasionally, the busy cursor never goes away, and neither the result handler nor the fault handler get invoked. I can understand that the handlers not getting invoked could be something that I'm doing wrong, but why would the busy cursor stay? Any suggestions? Thanks, -- Maciek Sakrejda Truviso, Inc. http://www.truviso.com -----Original Message----- From: Maciek Sakrejda <[EMAIL PROTECTED]> Reply-To: flexcoders@yahoogroups.com To: flexcoders@yahoogroups.com Subject: [flexcoders] LCDS AMF call not firing result events, busy cursor does not go away Date: Fri, 11 Jan 2008 10:52:53 -0800 I'm running into some odd Flex behavior, and I was wondering if anyone had run into something similar before. Basically, it looks like my RemoteObject result handlers are sometimes not being called. More specifically, I have a remote object that corresponds to a Java class which makes a jdbc call and returns some data. This remote object call is invoked from a button and adds a new tab to a dashboard. The new tab renders the results. Most of the time, this works fine, but occasionally, the AMF call never fires the handler (neither success nor failure), and the busy cursor never goes away. I've double-checked to make sure that I register result handlers before I invoke the method. The flashlog.txt file does not show anything odd. A Java thread dump on the server does not show any outstanding AMF calls being serviced, and if I re-try the same action, it works fine (although the original tab still never gets any data). The busy cursor remains until I close the client Flash object, but other than that, the client behaves normally. I've verified that the event listeners are being added before the remote call is made, but it almost seems like a bigger issue: the busy cursor should go away as soon as the result event is fired, whether I registered for it or not, right? For what it's worth, I seem to hit this more frequently if I open a burst of new tabs quickly one after another. I'm using: Java HotSpot(TM) Server VM (1.5.0_14-b03 mixed mode) Adobe Flash Player 9,0,115,0 (debug) Apache Tomcat 5.5.23 LCDS 2.5.1 Any thoughts? Thanks, -- Maciek Sakrejda Truviso, Inc. http://www.truviso.com