camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-6411) Setting a receiveTimeout for a shared fixed reply does not take effect
Date Sat, 01 Jun 2013 05:59:20 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-6411.
--------------------------------

       Resolution: Not A Problem
    Fix Version/s: 2.12.0
         Assignee: Claus Ibsen

Please use the user mailing list / forum first for your Camel help.

receiveTime is not a timeout. Its about how frequent to poll for new messages. Read the docs
at: http://camel.apache.org/jms and the spring JMS docs also as camel-jms is based on spring
jms.

If you do request/reply over JMS then its requestTimeout that is the timeout value. Its 20
sec by default.
                
> Setting a receiveTimeout for a shared fixed reply does not take effect
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-6411
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6411
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core, camel-jms
>    Affects Versions: 2.10.4
>         Environment: OS - RHEL 5.3
> Tomcat - 7.0.39
> JDK - 1.7
> Spring - 3.0.2
> WebSphere MQ - 7.0
>            Reporter: Siva B
>            Assignee: Claus Ibsen
>             Fix For: 2.12.0
>
>
> Setting the receiveTimeout of 1 second does not take effect. It's still waiting the reply
infinitely. Hence, we are seeing thread pile-ups in tomcat.
> From tomcat thread dump, all threads are waiting in CountDownLatch.await though we are
NOT using async mode.
> Queue Config: jms:queue:QUEUE.REQUEST?replyTo=SYNC.REPLY&?useMessageIDAsCorrelationID=true&receiveTime=1000&preserveMessageQos=true&replyToType=Shared&disableReplyTo=false
> Stack trace from thread dump:
> "ajp-bio-8010-exec-349" daemon prio=10 tid=0x0000000005eaf000 nid=0x73f9 waiting on condition
[0x0000000054758000]
>    java.lang.Thread.State: WAITING (parking)
>         at sun.misc.Unsafe.park(Native Method)
>         - parking to wait for  <0x00000000be675930> (a java.util.concurrent.CountDownLatch$Sync)
>         at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
>         at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
>         at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:115)
>         at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:86)
>         at org.apache.camel.processor.UnitOfWorkProducer.process(UnitOfWorkProducer.java:63)
>         at org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:360)
>         at org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:331)
>         at org.apache.camel.impl.ProducerCache.doInProducer(ProducerCache.java:227)
>         at org.apache.camel.impl.ProducerCache.sendExchange(ProducerCache.java:331)
>         at org.apache.camel.impl.ProducerCache.send(ProducerCache.java:186)
>         at org.apache.camel.impl.DefaultProducerTemplate.send(DefaultProducerTemplate.java:115)
>         at org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:119)
>         at org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:136)
>         at org.apache.camel.impl.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:284)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message