Jeff, hi How about DataServiceTransaction.createItem(). Does this spin off a new Thread?
--- In flexcoders@yahoogroups.com, "Jeff Vroom" <[EMAIL PROTECTED]> wrote: > > There's nothing in the "refreshFill" process that would spin off a > separate thread so this sounds strange. All of the fill methods should > be executed in the same thread as the 'createItem'. This should happen > synchronously as part of the "commit" method (if you are committing the > transaction yourself). > > > > Maybe a stack dump would help diagnose where the threads are and what > they are doing? > > > > I'm on vacation till Wednesday but the other thing that would help is to > enable server debug logging for Message.* and DataService.* patterns > (also Service.Data.* if you are using 2.5) I'd be glad to take a look at > the logs to try and understand what is going wrong when I get back. > > > > Jeff > > > > ________________________________ > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Dmitry Miller > Sent: Thursday, May 24, 2007 5:35 PM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] FDS and Spring please, help > > > > Hi, I am using FDS and Spring framework > > I have a destination that supports a few fills > autoSynchEnabled=true > I am using Assembler approach > > On a server-side when I create a new item via > DataServiceTransaction.createItem() FDS tries to reexecute all my > fills which are controlled by refreshFill method. However, each of the > above fills is executed in a separate thread which never dies. So > eventually, as I create items I reach the max thredas allowed limit > and the server chokes. > > Please, note, this this behavior noted only when Spring got introduced > into the system. Any help is greately appreciated >
