Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DC30610D3A for ; Fri, 29 Nov 2013 12:29:41 +0000 (UTC) Received: (qmail 444 invoked by uid 500); 29 Nov 2013 12:29:41 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 370 invoked by uid 500); 29 Nov 2013 12:29:39 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 282 invoked by uid 99); 29 Nov 2013 12:29:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Nov 2013 12:29:36 +0000 Date: Fri, 29 Nov 2013 12:29:36 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CAMEL-7026) camel-jms - Allow a message to control the request timeout using a header MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Claus Ibsen created CAMEL-7026: ---------------------------------- Summary: camel-jms - Allow a message to control the request timeout using a header Key: CAMEL-7026 URL: https://issues.apache.org/jira/browse/CAMEL-7026 Project: Camel Issue Type: Bug Components: camel-jms Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.12.3, 2.13.0 If you do request/reply over JMS then all messages uses the endpoint configured requestTimeout (default 20 sec). Though sometimes you want individual timeouts per message. So we should have a header to define what timeout to use. We have other headers today for destination, time to live etc. So its not something new. -- This message was sent by Atlassian JIRA (v6.1#6144)