org.apache.camel.ExchangeTimedOutException

The OUT message was not received within: 20000 millis due reply message with correlationID: ID-server-vm-2-dakosy-de-54767-1359566014882-7-81 not received. Exchange[Message: de.dakosy.pcs.ehge.kernel.exchange.EhgeExchange@bd5192]

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web24

  • The OUT message was not received within: 20000 millis due reply message with correlationID: ID-server-vm-2-dakosy-de-54767-1359566014882-7-81 not received. Exchange[Message: de.dakosy.pcs.ehge.kernel.exchange.EhgeExchange@bd5192]
  • The OUT message was not received within: 20000 millis due reply message with correlationID: ID-server-vm-2-dakosy-de-54767-1359566014882-7-81 not received. Exchange[Message: de.dakosy.pcs.ehge.kernel.exchange.EhgeExchange@bd5192]
  • The OUT message was not received within: 20000 millis due reply message with correlationID: ID-Dimas-PC-61919-1341382148513-0-2 not received. Exchange[Message: com.qqq.dw.beans.invocations.Ping@10699ea]
  • Stack trace

    • org.apache.camel.ExchangeTimedOutException: The OUT message was not received within: 20000 millis due reply message with correlationID: ID-server-vm-2-dakosy-de-54767-1359566014882-7-81 not received. Exchange[Message: de.dakosy.pcs.ehge.kernel.exchange.EhgeExchange@bd5192] at org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:122) at org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onTimeout(TemporaryQueueReplyHandler.java:61) at org.apache.camel.component.jms.reply.CorrelationMap.onEviction(CorrelationMap.java:49) at org.apache.camel.component.jms.reply.CorrelationMap.onEviction(CorrelationMap.java:26) at org.apache.camel.util.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:202) at org.apache.camel.util.DefaultTimeoutMap.run(DefaultTimeoutMap.java:158) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.