Yes I can some messages in dlq.type.specfic.queue and some messgaes on type specific queue.
Messges not route to outbound queue. Pls suggest what is the fix for this. It almost 2 days I am having this issue pls suggest On Sep 5, 2013 8:17 AM, "ceposta [via Camel]" < ml-node+s465427n5738709...@n5.nabble.com> wrote: > Maybe your TTL is set too short and the broker is rejecting those > messages. > Can you check your DLQ to see whether the messages are in there? > > > On Wed, Sep 4, 2013 at 7:07 PM, [hidden > email]<http://user/SendEmail.jtp?type=node&node=5738709&i=0> > <[hidden email] <http://user/SendEmail.jtp?type=node&node=5738709&i=1>>wrote: > > > > I am using simple failover url > > > > Failover:(ssl://br1,ssl://br2) > > > > my aim is set expiry time to message thats why I am producertemplate it > > creating issue here. > > > > Message will send > > > > Type specific queue After that camel use producertemplate set expiry > time > > to msg it send msg to another outbound queue. > > > > Now what is happening message staying on type specific queue and it > routing > > message each 3 to 5 min time.taking long time to route msg. > > > > Pls kindly help me. > > On Sep 5, 2013 1:42 AM, "ceposta [via Camel]" < > > [hidden email] <http://user/SendEmail.jtp?type=node&node=5738709&i=2>> > wrote: > > > > > What does it do? Does the broker dispatch messages to the client (you > can > > > see with the "in-flight" metrics on the broker)? Can you turn up the > > > logging and see what camel is doing? what sort of ack mode are you > using > > > on > > > the connection? > > > > > > > > > On Wed, Sep 4, 2013 at 11:50 AM, [hidden email]< > > http://user/SendEmail.jtp?type=node&node=5738702&i=0> > > > <[hidden email] <http://user/SendEmail.jtp?type=node&node=5738702&i=1 > > >>wrote: > > > > > > > > > > My code worked fine in activemq 5.5 only issue after upgrading > activemq > > > 5.8 > > > > > > > > Camel i having code like > > > > > > > > from(MESSAGING_TEST_CONSUMER_TYPE_SPECIFIC_QNAME).process(new > > > > MemosProcess(getContext().createProducerTemplate())) > > > > .end(); > > > > > > > > > > > > > > > > class MemosProcess implements Processor,QnamesInterface { > > > > private static final Logger LOG = > > > > LoggerFactory.getLogger(MemosProcess.class); > > > > > > > > ProducerTemplate prodtemplate=null; > > > > public MemosProcess(){ > > > > > > > > } > > > > public MemosProcess(ProducerTemplate template) { > > > > this.prodtemplate=template; > > > > } > > > > > > > > @Override > > > > public void process(Exchange exchange) throws Exception { > > > > JmsMessage msg = (JmsMessage) exchange.getIn(); > > > > Map<String, Object> headers = msg.getHeaders(); > > > > > > > > String eventType = (String) > > > headers.get(EVENT_TYPE); > > > > String msgId = (String) > > > headers.get(MESSAGE_ID); > > > > System.out.println("Memos-msgid:"+msgId); > > > > int msg_Expiry_Time = Integer.parseInt((String) > > > > headers.get(EXPIRY_TIME)); > > > > InetAddress address = InetAddress.getLocalHost(); > > > > String hostname = address.getHostName(); > > > > long MSG_EXPIRY = System.currentTimeMillis() + > > > msg_Expiry_Time; > > > > headers.put(JMSExpiration,MSG_EXPIRY); > > > > > > > > String restfulServiceURL =(String) > > > > headers.get(MEMOS_RESTFULSERVICE_URL); > > > > restfulServiceURL=restfulServiceURL+"update"; > > > > > > > > if (eventType.equalsIgnoreCase(CONSUMER_EVENT_TYPE)) { > > > > > > > > String serversList = (String) > > > > headers.get(MEMOS_TARGET_SERVERS); > > > > > > > > String servers [] = serversList.split(":"); > > > > String handler1 = ""; > > > > String handler2 = ""; > > > > > > > > if (servers.length >=2) { > > > > handler1 = servers[0]; > > > > handler2 = servers[1]; > > > > } > > > > headers.put(MEMOS_TARGET_SERVER,handler1); > > > > > > > prodtemplate.sendBodyAndHeaders(CONSUMER_TEST_QNAME,"Consumer > > > > test",headers); > > > > headers.put(MEMOS_TARGET_SERVER,handler2); > > > > new MemosProcess().callService(msgId, > > > > hostname,restfulServiceURL); > > > > > > > prodtemplate.sendBodyAndHeaders(CONSUMER_TEST_QNAME,"Consumer > > > > test",headers); > > > > }else if(eventType.equalsIgnoreCase(PRODUCER_EVENT_TYPE)){ > > > > new MemosProcess().callService(msgId, > > > > hostname,restfulServiceURL); > > > > > > > prodtemplate.sendBodyAndHeaders(PRODUCER_TEST_QNAME,"Producer > > > > test",headers); > > > > } > > > > } > > > > > > > > > > > > above code worked fine in active 5.5 but after upgrade into active > 5.8 > > > it > > > > is > > > > not working > > > > > > > > Message getting hang in MESSAGING_TEST_CONSUMER_TYPE_SPECIFIC_QNAME > not > > > > calling memosprocess class. > > > > > > > > Please kindly help me. > > > > > > > > > > > > > > > > -- > > > > View this message in context: > > > > > > > > > > http://camel.465427.n5.nabble.com/Camel-routing-issue-after-upgrade-into-active-mq-5-8-tp5738700.html > > > > Sent from the Camel - Users mailing list archive at Nabble.com. > > > > > > > > > > > > > > > > -- > > > *Christian Posta* > > > http://www.christianposta.com/blog > > > twitter: @christianposta > > > http://www.christianposta.com/blog > > > > > > > > > ------------------------------ > > > If you reply to this email, your message will be added to the > discussion > > > below: > > > > > > > > > http://camel.465427.n5.nabble.com/Camel-routing-issue-after-upgrade-into-active-mq-5-8-tp5738700p5738702.html > > > To unsubscribe from Camel routing issue after upgrade into active-mq > > 5.8, click > > > here< > > > > > > . > > > NAML< > > > http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > > > > > > > > > > > > > > > > -- > > View this message in context: > > > http://camel.465427.n5.nabble.com/Camel-routing-issue-after-upgrade-into-active-mq-5-8-tp5738700p5738708.html > > Sent from the Camel - Users mailing list archive at Nabble.com. > > > > > > -- > *Christian Posta* > http://www.christianposta.com/blog > twitter: @christianposta > http://www.christianposta.com/blog > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://camel.465427.n5.nabble.com/Camel-routing-issue-after-upgrade-into-active-mq-5-8-tp5738700p5738709.html > To unsubscribe from Camel routing issue after upgrade into active-mq 5.8, > click > here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5738700&code=cHJhYnVtY2EwNkBnbWFpbC5jb218NTczODcwMHw4OTY0MTU3ODg=> > . > NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://camel.465427.n5.nabble.com/Camel-routing-issue-after-upgrade-into-active-mq-5-8-tp5738700p5738712.html Sent from the Camel - Users mailing list archive at Nabble.com.
