From users-return-49732-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Sun Mar 25 22:57:53 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 756D418063B for ; Sun, 25 Mar 2018 22:57:52 +0200 (CEST) Received: (qmail 94022 invoked by uid 500); 25 Mar 2018 20:57:51 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 94005 invoked by uid 99); 25 Mar 2018 20:57:50 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Mar 2018 20:57:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id EBF73C00CD for ; Sun, 25 Mar 2018 20:57:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.394 X-Spam-Level: **** X-Spam-Status: No, score=4.394 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URI_HEX=1.313, URI_TRY_3LD=0.832] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id qdTEEGS3Nr03 for ; Sun, 25 Mar 2018 20:57:47 +0000 (UTC) Received: from mail-wr0-f172.google.com (mail-wr0-f172.google.com [209.85.128.172]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 2361F5F523 for ; Sun, 25 Mar 2018 20:57:47 +0000 (UTC) Received: by mail-wr0-f172.google.com with SMTP id c24so16907405wrc.6 for ; Sun, 25 Mar 2018 13:57:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=io/DIv8MV3U7LnqAK1ch+ekuagGrdp0A5wJqqIIS6Uc=; b=h7s4Z6/oNVFmBbGS6mo6Lys7KUTILTPxbqfLXhBTjfChWKk6Bl/ykOJkRZka+wDnNt WvFFXETlx7yPviir6/8F5EkZD6LvygwS2AWdA+fgW0tCzopzpzgPdmixC/oCinhU8AgT TuYebXE8EBRjiIagtE3ivFpmzWSbrZaD0q++AawMV3v5TJeL5NOznfphzx45oCggaYlQ ANlxd/JRk9iYcfLs1r3zXBiMOlOx5eYX/fkLytOj0qVTc4lsMnGTMuWSn6UqL3cHruex DO5+h1KUnhzxhqSG1yKju7shFx4gpDgjbHQ7+AyZFGK7rhJJAONNO3SbqQ/irT3LAoRu GCMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=io/DIv8MV3U7LnqAK1ch+ekuagGrdp0A5wJqqIIS6Uc=; b=jXX8IbAe1JVbPCErgd0lsFPV4PE6CVMOHJANqgO34g+No5bt0TaM4plRSgHMiFeIf2 QCBYZu5UGsHIq7HV7miJsI/LbLQZ9NRjYRDQSO0VN0t98J3ldBHDdp6KGdIa7jc08+4K tMIBQMZADZFLZGkEjqDuO1Y4Gxv5BMd+b+850SDGCt4rwp0428Dg/Eeh7G3eF/+zBI+W nw3GffLY5M71mOuQdZFdKL/DOP83tgLXDdiCKTkqvQIBw3An95PxU0YKyD89A8ECpBYr 4WRUIRZ0K7FwY+AkhLNzpiR28t6ms2KLXtw1SoSGGA+uXcVXgWtjM2rrR/NE8viac2// x/VA== X-Gm-Message-State: AElRT7EUyY5K8wN0DNm0JsRrq8GgefJgRssw6WB/7Abfaj2Qbuj7RPcV 0xwt0jDG6Z5l+f8h2Q3EFTxJSTmb9KO3p933DTvsSg== X-Google-Smtp-Source: AG47ELsUn4mGp6OjIgi80Wz8aZYtnwdeyAbKyo+DJq9vGlAPfhKcy8dXhBkJ+0Ir7C+U9SxCcB3FUPI3+9cP2YqVJPM= X-Received: by 10.223.188.1 with SMTP id s1mr30625647wrg.243.1522011466497; Sun, 25 Mar 2018 13:57:46 -0700 (PDT) MIME-Version: 1.0 Sender: tbain98@gmail.com Received: by 10.223.135.89 with HTTP; Sun, 25 Mar 2018 13:57:26 -0700 (PDT) In-Reply-To: <1521886375347-0.post@n4.nabble.com> References: <1520558414548-0.post@n4.nabble.com> <1520568664996-0.post@n4.nabble.com> <1520571483819-0.post@n4.nabble.com> <1520988768365-0.post@n4.nabble.com> <1521386052241-0.post@n4.nabble.com> <1521811996845-0.post@n4.nabble.com> <1521886375347-0.post@n4.nabble.com> From: Tim Bain Date: Sun, 25 Mar 2018 14:57:26 -0600 X-Google-Sender-Auth: TqZeFKuH33vFX0cXTrtj1m3Tlts Message-ID: Subject: Re: Camel generating message with correlationid=null and tmp-queue null To: ActiveMQ Users Content-Type: multipart/alternative; boundary="089e0820c060ce0320056842e80d" --089e0820c060ce0320056842e80d Content-Type: text/plain; charset="UTF-8" Rajesh, First, I want to let you know that although it's possible to edit/delete mailing list posts on the Nabble site after you've posted them, the edits are not sent out to the mailing list via email, so anyone (like me) who works primarily from email will not see the changes you make. So the best workflow is the only one that will work for both modes: treat posts as uneditable once they're sent initially, and make any corrections or additions to them by creating follow-on posts. If you choose to edit/delete posts once they're initially created, it will be harder for me (and anyone else using a workflow based on email) to support you. With that out of the way, I'm struggling to understand exactly what your question is. Clearly a portion of your question is why your clients are being disconnected from your broker, and I'll come to that in the next paragraph, but is that the only question? You started out asking about why certain properties on your messages were null, but you've not asked about that in several posts; is that issue resolved? You then asked about why your pooled connections were failing due to "channel has already failed;" is that issue still relevant? You also asked (in posts that you've since removed from the Nabble site) something about blockingQueue and its relationship to dynamic destination inclusion in a network of brokers; does the fact that you've removed that content from the Nabble site mean that it also is no longer a question you need answers to? For the question of why your connections are being disconnected, the InactivityIOException that you added to the Nabble post on 3/24 seems to indicate that the connection is being terminated because it's been inactive for longer than the inactivity timeout interval allows. Do you have the inactivity monitor enabled? If so, what settings are you using, on both sides of the connection? Details about the inactivity monitor and how it's configured can be found at http://activemq.apache.org/activemq-inactivitymonitor.html. Have you confirmed that the firewall between your client and your broker is not filtering out any traffic between these two processes. If you haven't confirmed that every byte is making it through in both directions, I'd suggest you make that a priority. BTW, there was no file named jstack.out containing a thread dump attached to your message either in email or in the Nabble post. If it's still relevant to your question, can you please re-send that? Tim On Sat, Mar 24, 2018 at 4:12 AM, Rajesh Malla wrote: > Thank you Tim > > for this IOException, we have not observed any reasonable exceptions on > broker [ producer ] side. > > attached thread dump jstack.out. Can you please look into and help. > > > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html > --089e0820c060ce0320056842e80d--