You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Ron Gavlin (JIRA)" <ji...@apache.org> on 2009/06/22 21:49:35 UTC
[jira] Reopened: (CAMEL-1497) JmsPollingConsumer - receive does not
work
[ https://issues.apache.org/activemq/browse/CAMEL-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ron Gavlin reopened CAMEL-1497:
-------------------------------
Regression: [Regression]
Unfortunately, this commit broke the ability to use Camel 1.x with Spring JMS 2.0.x. Please consider using the correct integer values for the 1.x branch and use the Spring JMS 2.5.x-specific constants only for the trunk.
Thanks.
> JmsPollingConsumer - receive does not work
> ------------------------------------------
>
> Key: CAMEL-1497
> URL: https://issues.apache.org/activemq/browse/CAMEL-1497
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 1.6.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 1.6.1, 2.0-M2
>
>
> The timeout values to set on Spring JmsTemplate is wrong. We should uses the provided constants on JmsTemplate for this
> {code}
> /**
> * Timeout value indicating that a receive operation should
> * check if a message is immediately available without blocking.
> */
> public static final long RECEIVE_TIMEOUT_NO_WAIT = -1;
> /**
> * Timeout value indicating a blocking receive without timeout.
> */
> public static final long RECEIVE_TIMEOUT_INDEFINITE_WAIT = 0;
> {code}
> Is the correct values. Looks like the values was reverted in the camel-jms code
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.