-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Are you by chance using the VM transport on ActiveMQ? I've seen this transport deadlock with a small amount of load. Using the TCP transport (default in ServiceMix) works fine, but it's extra overhead when you aren't doing clustering or anything of the sort.
Guillaume Nodet wrote: > This is the default flow. If you want to ensure that it is used for all > exchanges, just remove the other flows from the servicemix.xml > configuration file: > > <sm:broker> > <sm:securedBroker authorizationMap="#authorizationMap"> > <sm:flows> > <sm:sedaFlow /> > </sm:flows> > </sm:securedBroker> > </sm:broker> > > > On 3/1/07, jlo_gestalt <[EMAIL PROTECTED]> wrote: >> >> Can one of you guys point me in the direction on how to change >> ServiceMix to >> use SedaFlow? >> >> >> William Blackburn-2 wrote: >> > >> > Just a followup to my last reply, I heard back from my QA guys, under >> > all of our hardware configurations, we cannot reproduce the message >> > loss under seda flow. >> > >> > BJ >> > >> > >> > On Feb 28, 2007, at 1:15 PM, Guillaume Nodet wrote: >> > >> >> Have you tried (if possible) to run your tests with a SEDA flow to >> >> see if the problem comes from the jms flow or elsewhere ? >> >> >> >> On 2/28/07, William Blackburn <[EMAIL PROTECTED]> wrote: >> >>> My application uses the servicemix-3.1 release version and leverages >> >>> servicemix 'pojo' components heavily. Everything has been working >> >>> fine up until now, however the app is currently undergoing some >> >>> stress testing. During these tests, I lose message-exchanges >> >>> routinely. About 1 out of every 10 exchanges generated by the >> >>> components in my app never make it to their destination. >> >>> >> >>> I am using JMSflow with an embedded activemq broker. I have tried >> >>> several Activemq persistence strategies, form no-persistence to kaha >> >>> and journalled jdbc, all with the same result. I have extensive >> >>> logging and there is never an error or warning logged. I have >> >>> reveiwed my onMessageExchange implementations in the components to >> >>> check that I am not silently consuming an exception case, I am not. >> >>> >> >>> The issue appears to only be reproducible on higher-end machines with >> >>> two or more cpus when the app is under heavy load (ie: lots of >> >>> concurrent exchanges are firing between components. >> >>> >> >>> Has anyone seen this before? With no exceptions or warnings and a >> >>> seemingly random pattern of success vs. failure, I am at a loss. >> >>> >> >> >> >> >> >> -- >> >> Cheers, >> >> Guillaume Nodet >> >> ------------------------ >> >> Architect, LogicBlaze (http://www.logicblaze.com/) >> >> Blog: http://gnodet.blogspot.com/ >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Message-exchanges-silently-dropped-under-heavy-loads-tf3321785s12049.html#a9259544 >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF6d2OMrBfzfMVwMcRArJyAJ9gSA22Hr97rsTYJc9orOSXoK8E7wCeJWuu bT6AZGterGUBWJeD+wMDD+A= =PIN3 -----END PGP SIGNATURE-----
