Tuning the poolsize in the configuration of ServiceMix I've been able to postpone the errors. I've given the corePoolSize a value of 64 and it makes it much harder to block the queue, though it's still possible. Once it starts increasing the size of the queue (messages getting blocked) I can restart the queue from the jconsole and it comes back to normal again, but it's not very elegant to do it this way. Has someone got any idea to make the queue unblockable (or at least as solid as possible)?
On Wed, Dec 10, 2008 at 12:47 PM, Sebastian Gomez <[EMAIL PROTECTED]> wrote: > Hi everyone. > I'm about to finish a project using ServiceMix 3.2.2, and after doing some > stress tests I've found that if I send lots of messages to the same > servicemix-bean endpoint to do quite complex operations (they take a long > time and should return quite large amounts of data, including attachments), > the Seda Queue finally gets stuck. The only way I've found to "unstuck" it > is to restart ServiceMix (something I won't be able to do after handing in > my application). > > Debugging I've seen my application reaches the SedaFlow "doSend" method, it > enqueues the packet correctly, but I suppose it never dequeues (how could I > see if this is true?). > > I've seen using jconsole that servicemix-bean's Seda Queue size keeps > increasing as I send messages into my application, and never decreases, so > there must be something going wrong. I'd like to know if there's some known > issue involving this, and if luckily there's some kind of solution. > > My project's deadline is near, so I'd really appreciate any help. > > Thanks in advance. > > Sebastian Gomez. >
