Hi
We are having a issue where our Selector mesageid is being overidden by the
messageid from new requests. Its like endpoints are being cached and same
endpoints are being reused.
beanprocessor code
@EndpointInject(uri = "bxJmscomponent:queueName")
JmsEndpoint endpointJMS;
@EndpointInject
ConsumerTemplate consumer;
public void process(Exchange exchange){
//prepare JMS selector
String jmsselector = ""
//set selector
endpointJMS.setSelector(jmsselector);
//
rspExchange = consumer.receiveNoWait(endpoint);
}
bean is of scope prototype a new bean will be created for every request. its
like endpoints are being cached somewhere and camel is returing the
endpoints from the cache instead of creating new.
Is there a option to tell camel to create a new endpoint for every request?
Thanks
Ravi
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-JMS-JMS-Selector-getting-overridden-by-new-requests-tp5774806.html
Sent from the Camel - Users mailing list archive at Nabble.com.
