You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Richard Kettelerij (JIRA)" <ji...@apache.org> on 2010/12/06 22:02:14 UTC
[jira] Commented: (CAMEL-3396) Problem in message listener - Camel
2.5 + JMS + WebsphereMQ
[ https://issues.apache.org/jira/browse/CAMEL-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968407#action_12968407 ]
Richard Kettelerij commented on CAMEL-3396:
-------------------------------------------
What Spring version do you use? The camel-jms component is build on Spring, in fact the message you're seeing ("Setup of JMS message listener invoker failed for destination.....") is logged by Spring.
> Problem in message listener - Camel 2.5 + JMS + WebsphereMQ
> -----------------------------------------------------------
>
> Key: CAMEL-3396
> URL: https://issues.apache.org/jira/browse/CAMEL-3396
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 2.5.0
> Environment: Websphere 6.1 + WebSphereMQ + Camel 2.5 JMS
> Reporter: Carlos Eduardo Leite
>
> I have an application where I used jms camel2.4 Websphere MQ after upgrading to version 2.5 of camel noticed that after some time the messages were no longer removed from the reply queue and following error occurs:
> [12/4/10 13:46:23:173 WGT] 00000587 SystemOut O INFO 2010-12-04 13:46:21,508 [DefaultMessageListenerContainer-56] org.apache.camel.component.jms.reply.PersistentQue
> ueReplyManager$PersistentQueueMessageListenerContainer: Setup of JMS message listener invoker failed for destination 'OUT.QUEUE' - trying to recover. Cause: null
> java.lang.StackOverflowError
> at com.ibm.disthub2.impl.matching.MatchingContext.fmtMsgAccess(MatchingContext.java:133)
> at com.ibm.disthub2.impl.matching.MatchingContext.getIdentifierValue(MatchingContext.java:121)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.evalInternal(Evaluator.java:145)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.eval(Evaluator.java:76)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.evalInternal(Evaluator.java:174)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.eval(Evaluator.java:76)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.evalInternal(Evaluator.java:174)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.eval(Evaluator.java:76)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.evalInternal(Evaluator.java:175)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.eval(Evaluator.java:76)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.evalInternal(Evaluator.java:175)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.eval(Evaluator.java:76)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.evalInternal(Evaluator.java:175)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.eval(Evaluator.java:76)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.evalInternal(Evaluator.java:175)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.eval(Evaluator.java:76)
> at com.ibm.disthub2.impl.matching.selector.Evaluator.evalInternal(Evaluator.java:175)
> I wonder if this might be a error since the class: org.apache.camel.component.jms.reply.PersistentQueueReplyManager only exists in version 2.5.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.