A fault handler on your RO may help.

<mx:RemoteObject ... fault="onRemObjError(event)">

Then define the handler function and maybe show an alert containing
event.fault.faultstring to let you know a fault occurred.


--- In [email protected], "digital_eyezed" <[EMAIL PROTECTED]>
wrote:
>
> Ok how weird is this:
> 
> In the remote object debug you can see the return with all the data 
> being sent:
> 
> Info: Completed 'uk.co.mycompany.dao.GetSalesDAO.getData' with reply 
> method 'onResult' in 96295ms
> Info: Serializing response
>   (Message #0 targetURI=/1/onResult, responseURI=null)
>     (Array #0)
>       [0] = (Typed Object #1 'uk.co.mycompany.dao.SalesVO')
>         mtotal = 143.0
>         avgevnt = 9.569930076599121
>         total = 1173.0
>         paffected = 0.2663846015930176
>         hrspermac = 36.56489562988281
>         lostsales = 24.324005126953125
>         _remoteClass = "uk.co.mycompany.dao.SalesVO"
>         affected = 19.83356475830078
>         lostunits = 25.21294403076172
>         hrsout = 5228.7802734375
>         rosaff = 115.84265899658203
> 
> But the showbusy cursor just keeps on going and no data is shown!!!!!
> 
> Where am I going wrong?
> 
> I have even taken out the binding to the dataProvider and just have 
> the result handler showing an alert, but no alert shows, just the 
> blinking showBusyCursor!
> 
> Any suggestions would be greatly received,
> 
> Thanks in advance.
> 
> Iain
> 
> 
> --- In [email protected], "digital_eyezed" 
> <iain.mclean@> wrote:
> >
> > Hi,
> > 
> > here it is:
> > 
> > <mx:RemoteObject  id="getDataOOS" 
> source="uk.co.mycompany.SalesDAO" 
> > showBusyCursor="true">
> >     <mx:method name="getData" result="setDataProvider(event)"/>
> > </mx:RemoteObject>
> > 
> > public function setDataProvider(event){
> >     summaryGrid.dataProvider = event.result;
> > }
> > 
> > I will try to see what the remoteObject debug shows.
> > 
> > Regards,
> > 
> > Iain
> > 
> > 
> > --- In [email protected], "Doug Lowder" <douglowder@> 
> > wrote:
> > >
> > > Can you post the RemoteObject declaration?
> > > 
> > > If you haven't already done so, try setting <remote-objects-
> debug> 
> > > to true in WEB-INF/flex/flex-config.xml, just to see if there's 
> > any 
> > > debug info that might be useful.
> > > 
> > > 
> > > --- In [email protected], "digital_eyezed" 
> > > <iain.mclean@> wrote:
> > > >
> > > > Actually it's the same amount of data being returned, it just 
> > > takes 
> > > > longer to return it because the data that the database has to 
> > > check 
> > > > over is a larger set because of the increase in the from and 
> to 
> > > > dates.
> > > > 
> > > > I.E.
> > > > 
> > > > I have a sales summary report which sends the date from and 
> the 
> > > date 
> > > > to as arguments to a remoteObject, it uses this to do a query 
> on 
> > > the 
> > > > database, then returns the result as an ArrayList to the flex 
> app
> > > > (there is only ever 1 array in the list) and it then 
> represents 
> > > this 
> > > > in a datagrid as a single row.
> > > > 
> > > > If I run the sales query for 1 week, it fills in the datagrid 
> > > > without any issues.
> > > > 
> > > > If I run the query for a month then the busy cursor stays on 
> > > forever 
> > > > and the result is not shown. I know that the database returns 
> > the 
> > > > data and that the java function also returns the ArrayList 
> > because 
> > > I 
> > > > can see it doing so in the console, the result handler just 
> > seems 
> > > to 
> > > > miss it and therfore nothing happens.
> > > > 
> > > > I really don't know where to go next ;-(
> > > > 
> > > > Cheers,
> > > > 
> > > > Iain
> > > > 
> > > > --- In [email protected], "Doug Lowder" <douglowder@> 
> > > > wrote:
> > > > >
> > > > > Yes, sounds like there is something different going on.
> > > > > 
> > > > > So the same result handler that works for a smaller query 
> > hangs 
> > > on 
> > > > a 
> > > > > large query, where the only difference is the amount of data 
> > > being 
> > > > > returned by the service?
> > > > > 
> > > > > 
> > > > > --- In [email protected], "digital_eyezed" 
> > > > > <iain.mclean@> wrote:
> > > > > >
> > > > > > Thanks,
> > > > > > 
> > > > > > I 've tried all what you have suggested and I do get a 
> > return 
> > > in 
> > > > a 
> > > > > > JSP app. I also tried changing the connectionTimout value, 
> > but 
> > > > > that 
> > > > > > didn't work either. It's really weird as I can see Tomcat 
> > > > > returning 
> > > > > > the object (an ArrayList)in the console (eclipse) but flex 
> > > just 
> > > > > sits 
> > > > > > their saying "well, where is my return then?".
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > --- In [email protected], "Doug Lowder" 
> > <douglowder@> 
> > > > > > wrote:
> > > > > > >
> > > > > > > The underlying HTTP connection may be timing out.  You 
> can 
> > > try 
> > > > > > > writing a test JSP page that executes the same large sql 
> > > > query - 
> > > > > > if 
> > > > > > > that times out as well, then the problem is not specific 
> > to 
> > > > Flex.
> > > > > > > 
> > > > > > > Or, if you're running Tomcat as your server you can just 
> > > take 
> > > > a 
> > > > > > look 
> > > > > > > at server.xml and bump the connectionTimeout value of 
> the 
> > > > > > > <Connector> tag up to something higher.
> > > > > > > 
> > > > > > > Hope that helps,
> > > > > > > Doug
> > > > > > > 
> > > > > > > --- In [email protected], "digital_eyezed" 
> > > > > > > <iain.mclean@> wrote:
> > > > > > > >
> > > > > > > > Hi,
> > > > > > > > 
> > > > > > > > I have a simple remoteObject that returns no problem 
> > > unless 
> > > > > the 
> > > > > > > > remoteObject takes longer than 1 minute to return, 
> then 
> > > flex 
> > > > > > never 
> > > > > > > > picks up the return. Has anyone seen this before?
> > > > > > > > 
> > > > > > > > i.e. If I run a query over a time period  of 2 weeks 
> it 
> > > > return 
> > > > > > no 
> > > > > > > > problem in about 35 seconds (it's a big sql query at 
> the 
> > > > Java 
> > > > > > > side). 
> > > > > > > > If I increase the time period to a 1 month period for 
> > the 
> > > > > query 
> > > > > > > then 
> > > > > > > > return from the Java side is not pcked up by Flex, it 
> > just 
> > > > > sits 
> > > > > > > there 
> > > > > > > > in the busy Cursor state. Is there an underlying timer 
> > > that 
> > > > > > gives 
> > > > > > > up 
> > > > > > > > waiting for a return?
> > > > > > > > 
> > > > > > > > Cheers,
> > > > > > > > 
> > > > > > > > Iain
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>






--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/flexcoders/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to