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 68FB6200CA6 for ; Tue, 13 Jun 2017 13:25:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6772C160BDC; Tue, 13 Jun 2017 11:25:04 +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 AEB38160BC9 for ; Tue, 13 Jun 2017 13:25:03 +0200 (CEST) Received: (qmail 56474 invoked by uid 500); 13 Jun 2017 11:25:02 -0000 Mailing-List: contact issues-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 issues@activemq.apache.org Received: (qmail 56465 invoked by uid 99); 13 Jun 2017 11:25:02 -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; Tue, 13 Jun 2017 11:25:02 +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 663CFC0335 for ; Tue, 13 Jun 2017 11:25:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id o0HFIFN8BSVu for ; Tue, 13 Jun 2017 11:25:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id B52C45FAF3 for ; Tue, 13 Jun 2017 11:25:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 4EFC6E00A3 for ; Tue, 13 Jun 2017 11:25:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 06FC221D8E for ; Tue, 13 Jun 2017 11:25:00 +0000 (UTC) Date: Tue, 13 Jun 2017 11:25:00 +0000 (UTC) From: "Sridip Bhattacharya (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMQ-6701) Intermittent CPU spikes in one broker in a network bridge MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 13 Jun 2017 11:25:04 -0000 [ https://issues.apache.org/jira/browse/AMQ-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sridip Bhattacharya updated AMQ-6701: ------------------------------------- Description: Hi, We have a setup with network bridge between two activemq, say *http-broker12 & http-broker21* in two different VM, where communication occurs in both ways. {noformat} {noformat} {noformat} {noformat} Now we are facing intermittent CPU spikes (400%) in http-broker12 broker. Whereas http-broker21 works normal. Could you please confirm if anything abnormal/identified bug or config issue here? //SB was: Hi, We have a setup with network bridge between two activemq, say *http-broker12 & http-broker21* in two different VM, where communication occurs in both ways. {noformat} {noformat} {noformat} {noformat} Now we are facing intermittent CPU spikes (400%) in http-broker12 broker. Whereas http-broker21 works normal. Could you please confirm if anything abnormal/identified bug or config issue here? //SB > Intermittent CPU spikes in one broker in a network bridge > --------------------------------------------------------- > > Key: AMQ-6701 > URL: https://issues.apache.org/jira/browse/AMQ-6701 > Project: ActiveMQ > Issue Type: Task > Components: Broker > Affects Versions: 5.12.0 > Environment: RHEL 7.2 in VMWARE ESXi virtual machines, JDK 1.8 > Reporter: Sridip Bhattacharya > Priority: Minor > > Hi, > We have a setup with network bridge between two activemq, say *http-broker12 & http-broker21* in two different VM, where communication occurs in both ways. > {noformat} > > > {noformat} > {noformat} > > > {noformat} > Now we are facing intermittent CPU spikes (400%) in http-broker12 broker. Whereas http-broker21 works normal. > Could you please confirm if anything abnormal/identified bug or config issue here? > //SB -- This message was sent by Atlassian JIRA (v6.4.14#64029)