-
1. Re: Strange error
davsclaus Mar 8, 2011 8:15 AM (in response to larasith)Could you provide more details. Which version of Fuse ESB are you using. What bundle is it. What did you do to have it stop working? Can you post the complete stack trace. etc. etc.
-
2. Re: Strange error
larasith Mar 8, 2011 9:16 AM (in response to davsclaus)Yes, my version is FUSE 4.3.1 and this is the complete stack trace:
15:10:31,405 | WARN | erTimeoutChecker | CorrelationMap | ? ? | 68 - org.apache.camel.camel-core - 2.6.0.fuse-00-00 | Exception occurred during purge task. This exception will be ignored.
java.lang.IllegalStateException: COMPLETE,resumed,expired
at org.eclipse.jetty.server.AsyncContinuation.dispatch(AsyncContinuation.java:364)[144:org.eclipse.jetty.server:7.2.2.v20101205]
at org.eclipse.jetty.server.AsyncContinuation.resume(AsyncContinuation.java:769)[144:org.eclipse.jetty.server:7.2.2.v20101205]
at org.apache.camel.component.jetty.CamelContinuationServlet$1.done(CamelContinuationServlet.java:110)[203:org.apache.camel.camel-jetty:2.6.0.fuse-00-00]
at org.apache.camel.management.InstrumentationProcessor$1.done(InstrumentationProcessor.java:78)[68:org.apache.camel.camel-core:2.6.0.fuse-00-00]
at org.apache.camel.processor.UnitOfWorkProcessor$1.done(UnitOfWorkProcessor.java:107)[68:org.apache.camel.camel-core:2.6.0.fuse-00-00]
at org.apache.camel.processor.Pipeline$1.done(Pipeline.java:156)[68:org.apache.camel.camel-core:2.6.0.fuse-00-00]
at org.apache.camel.processor.DefaultChannel$1.done(DefaultChannel.java:275)[68:org.apache.camel.camel-core:2.6.0.fuse-00-00]
at org.apache.camel.processor.RedeliveryErrorHandler$1.done(RedeliveryErrorHandler.java:311)[68:org.apache.camel.camel-core:2.6.0.fuse-00-00]
at org.apache.camel.management.InstrumentationProcessor$1.done(InstrumentationProcessor.java:78)[68:org.apache.camel.camel-core:2.6.0.fuse-00-00]
at org.apache.camel.processor.DefaultChannel$1.done(DefaultChannel.java:275)[68:org.apache.camel.camel-core:2.6.0.fuse-00-00]
at org.apache.camel.processor.RedeliveryErrorHandler$1.done(RedeliveryErrorHandler.java:311)[68:org.apache.camel.camel-core:2.6.0.fuse-00-00]
at org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:150)[198:org.apache.camel.camel-jms:2.6.0.fuse-00-00]
at org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onTimeout(TemporaryQueueReplyHandler.java:59)[198:org.apache.camel.camel-jms:2.6.0.fuse-00-00]
at org.apache.camel.component.jms.reply.CorrelationMap.onEviction(CorrelationMap.java:34)[198:org.apache.camel.camel-jms:2.6.0.fuse-00-00]
at org.apache.camel.component.jms.reply.CorrelationMap.onEviction(CorrelationMap.java:26)[198:org.apache.camel.camel-jms:2.6.0.fuse-00-00]
at org.apache.camel.util.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:206)[68:org.apache.camel.camel-core:2.6.0.fuse-00-00]
at org.apache.camel.util.DefaultTimeoutMap.run(DefaultTimeoutMap.java:158)[68:org.apache.camel.camel-core:2.6.0.fuse-00-00]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)[:1.6.0_23]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)[:1.6.0_23]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)[:1.6.0_23]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)[:1.6.0_23]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)[:1.6.0_23]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)[:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)[:1.6.0_23]
at java.lang.Thread.run(Thread.java:662)[:1.6.0_23
-
3. Re: Strange error
davsclaus Mar 8, 2011 10:44 AM (in response to larasith)Ah okay the error is harmless.
I assume you use Jetty and JMS request/reply in a Camel route? If so it seems as the JMS timed out waiting for a reply, and it would then done this exchange. During this work it would done the Jetty continuation. Which also seems to be expired.
What we should do int he Camel code is to reduce the WARN logging as its harmless.
-
4. Re: Strange error
davsclaus Mar 8, 2011 10:46 AM (in response to davsclaus)I have logged a JIRA at Apache
-
-
6. Re: Strange error
davsclaus Mar 9, 2011 5:21 AM (in response to larasith)You could for example
- disable Jetty continuation
- or adjust Jetty continuation timeout to be higher
See more at
-
7. Re: Strange error
larasith Mar 9, 2011 7:13 AM (in response to davsclaus)Do it, thanks davsclaus.
-
8. Re: Strange error
davsclaus Mar 12, 2011 12:51 PM (in response to larasith)I managed to reproduce the issue and will commit a fix to the trunk so those WARN logs will not be present in the future.