[
https://issues.apache.org/jira/browse/CAMEL-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015704#comment-13015704
]
Hadrian Zbarcea commented on CAMEL-3781:
----------------------------------------
Heath, what about using the requestTimeout instead of introducing another
option?
requestTimeout=0 would have the same effect.
{code}
- if (answer instanceof JmsTemplate && requestTimeout > 0) {
+ if (answer instanceof JmsTemplate && requestTimeout >= 0) {
JmsTemplate jmsTemplate = (JmsTemplate) answer;
jmsTemplate.setExplicitQosEnabled(true);
- if (timeToLive < 0) {
+ if (timeToLive < 0 && requestTimeout > 0) {
// If TTL not specified, then default to
jmsTemplate.setTimeToLive(requestTimeout);
}
{code}
> Add option to disable expiration on JMS component
> -------------------------------------------------
>
> Key: CAMEL-3781
> URL: https://issues.apache.org/jira/browse/CAMEL-3781
> Project: Camel
> Issue Type: New Feature
> Components: camel-jms
> Affects Versions: 2.6.0
> Environment: Java 1.6.0_24, Mac OS X 10.6.6
> Reporter: Bryan Keller
> Priority: Minor
> Fix For: 2.8.0
>
> Attachments: patch-3781.diff
>
>
> It would be nice to add an option to the JMS component to disable the use of
> message expirations for InOut exchanges. If a client and server have clocks
> that are out-of-sync, using message expiration can cause problems. More
> details can be found here:
> http://camel.465427.n5.nabble.com/InOut-exchanges-require-synchronized-clocks-td3411881.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
