Hi Check which kind of message exchange pattern you use: InOnly or InOut. As if you use the latter then sending over JMS will have it wait for a reply. And thus could explain the slow.
Routing slip is sometimes mixed up with recipient list EIP pattern. So take a look if its the right pattern you use. And use Tracer to see what goes on and how slows things are http://camel.apache.org/tracer On Thu, Mar 25, 2010 at 3:30 AM, Muhammad Ichsan <ich...@gmail.com> wrote: > Dear All > > I have strange problem in Camel. I use routingSlip like the following: > > ... > <setExchangePattern pattern="InOut" /> > <routingSlip headerName="InvokerEndpointList" uriDelimiter=","/> > <setExchangePattern pattern="InOnly" /> > ... > > There was no problem before in flowing in a 4-endpoint routing slip. > But now, the third of the endpoints is visited 30s-38s since last > endpoint is visited. What are the possible causes? > > This are the details: > > header InvokerEndpointList: q1, q2, q3, q4 > > This is the way I log my time for all queues above. > > <route> > <from uri="activemq:q1"/> > <wireTap uri="q1timeGetIn"/> > ... > <to uri="mock:x" /> > <wireTap uri="q1timeGetOut"/> > </route> > > The fact is > > q3timeGetIn - q2timeGetOut >= 30s > > Why this happens? > > Thanks > > -- > ~The best men are men who benefit to others > http://michsan.web.id > > Yang berkualitas memang beda rasanya! > http://rizqi-cookies.com > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
