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" <[EMAIL PROTECTED]> 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/
