Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 01E6F200B17 for ; Tue, 21 Jun 2016 15:36:54 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 002EA160A4F; Tue, 21 Jun 2016 13:36:54 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3EA49160A07 for ; Tue, 21 Jun 2016 15:36:53 +0200 (CEST) Received: (qmail 70475 invoked by uid 500); 21 Jun 2016 13:36:52 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 70463 invoked by uid 99); 21 Jun 2016 13:36:52 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jun 2016 13:36:52 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id CE9EDE020A; Tue, 21 Jun 2016 13:36:51 +0000 (UTC) From: tabish121 To: dev@activemq.apache.org Reply-To: dev@activemq.apache.org References: In-Reply-To: Subject: [GitHub] activemq-artemis issue #593: ARTEMIS-585 support send on dynamic sender link Content-Type: text/plain Message-Id: <20160621133651.CE9EDE020A@git1-us-west.apache.org> Date: Tue, 21 Jun 2016 13:36:51 +0000 (UTC) archived-at: Tue, 21 Jun 2016 13:36:54 -0000 Github user tabish121 commented on the issue: https://github.com/apache/activemq-artemis/pull/593 I copied that bit from another test and didn't see how long the delay was, I've updated the PR to use 500 ms instead :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---