[
https://issues.apache.org/jira/browse/CAMEL-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015760#comment-13015760
]
Bryan Keller commented on CAMEL-3781:
-------------------------------------
Message expiration is something handled by the message broker (not Camel). A
message that has expired will not be delivered by the broker. This feature
requires clocks on the server and client be synchronized to work properly.
Request timeout is used by Camel to define how long a client should wait for a
response from an InOut request before throwing an exception. It is implemented
on the client only and thus does not require clocks be synchronized.
I still wanted the request timeout (I don't wait forever for a response on the
client), but I wanted to turn off using message expiration because I could not
guarantee the client and server clocks were in sync.
> 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
