It really depends on a whole lot of things: * flow used * thread pool config * debug logging turned off * listeners registered (i'm thinking about some listeners that could serialize the whole exchange to a DB for example) The channel.send() method time will depends on those 4 parameters (at least), so I would suggest the following: * only enable SEDA flow * raise thread pools * make sure logging is at INFO level * use a trimmed configuration (no audit, no spagic listeners, etc...)
On Fri, Sep 19, 2008 at 3:21 PM, Andrea Zoppello <[EMAIL PROTECTED]> wrote: > Hi all, > > After investigating some performance problem using an eip pipeline under a > load of > 20 concurrent client, i've found enablig some detailed tracing of time for > each instruction of > "org.apache.servicemix.http.processors.Processor" class ( I've modified the > source to add detailed time level logging ) and > i've discovered the problem is in channel.send() method. > > This is probably because the external webservice have a big soap response. > > At the moment i've think the problem was in Unmarshalling phase but after > detailed ( debug level ) > tracing, i diecovered the problem is in the send method. > > I've time of 19, 20 seconds for sendig message, i've not measured the size > of soap response, i'll trace > the size and let you know, but it seem that big messages are not handled in > very efficient way. > > Any idea about that?? > > Andrea > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://open.iona.com
