Barrie, To disable those flows, you can just comment out the JMS and JCA flow elements in conf/servicemix.xml. This is unrelated to using a JMS endpoint in your flow -- you can still have JMS endpoints when using the SedaFlow internally to send exchanges between components. Using the JMS/JCA flow will use JMS queues under the covers to transfer exchanges, but it's usually a better idea to use explicit jms endpoints like you are doing because then you have control yourself of when things are getting queued.
Could you give it another go with both flows disabled to see if that's where the problems are coming from? Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/10/21 Barrie Treloar <[email protected]>: > On Wed, Oct 21, 2009 at 6:14 AM, Gert Vanthienen > <[email protected]> wrote: >> Barrie, >> >> It looks like those are all JMS/JCA flow threads. Could you try >> disabling those two flows in conf/servicemix.xml and see if that fixes >> the issue? It might only be a workaround if you're not using those >> flows, but it will also give us a clue where to look for solving this >> issue. > > My Proof of Concept uses JMS but not JCA. > > Request: File Poller -> ESB -> JMS Q > Response: JMS Topic -> ESB -> File Sender > > I'm happy to give this a go, this is the only bit I can find referencing > jms/jca > > ${SMX_HOME}/conf/servicemix.xml > <!-- Use a secured broker (see security.xml) > and define the 3 standard flows --> > <sm:broker> > <sm:securedBroker authorizationMap="#authorizationMap"> > <sm:flows> > <sm:sedaFlow /> > <sm:jmsFlow jmsURL="${activemq.url}" /> > <sm:jcaFlow connectionManager="#connectionManager" > jmsURL="${activemq.url}" /> > </sm:flows> > </sm:securedBroker> > </sm:broker> > > How do I disable these flows? > > I'm attempting to remove the jms-su from my sa and see whether that > still has an issue. >
