Return-Path: X-Original-To: apmail-axis-java-dev-archive@www.apache.org Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 61BB710B2A for ; Tue, 25 Nov 2014 19:03:15 +0000 (UTC) Received: (qmail 60471 invoked by uid 500); 25 Nov 2014 19:03:14 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 60336 invoked by uid 500); 25 Nov 2014 19:03:14 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 60320 invoked by uid 99); 25 Nov 2014 19:03:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Nov 2014 19:03:14 +0000 Date: Tue, 25 Nov 2014 19:03:14 +0000 (UTC) From: "Himakar Chennapragada (JIRA)" To: java-dev@axis.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AXIS2-5679) Axis2 "Hot Deployment" server spins CPU on idle - not acceptable in Production - customer BLOCKED MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AXIS2-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Himakar Chennapragada updated AXIS2-5679: ----------------------------------------- Component/s: deployment Description: The server (Tomcat + Axis2) spins CPU/MIPS on idle when there is no workload when "hot deployment" is enabled in Axis2. When "hot deployment" is disabled there is no CPU spin. This needs urgent attention as our customer is CRITICALLY BLOCKED in PRODUCTION environment running hundreds of SOAP services. Restarting the server on every new service deployment is unacceptable because of the restart and restart also takes higher CPU because it loads all services in memory at server startup. Kindly look into this ASAP and any help highly appreciated. Priority: Blocker (was: Major) Environment: Tomcat 7.0.51 and Axis2 1.6.1 Affects Version/s: 1.6.0 Summary: Axis2 "Hot Deployment" server spins CPU on idle - not acceptable in Production - customer BLOCKED (was: Axis2 "Hot Deployment) > Axis2 "Hot Deployment" server spins CPU on idle - not acceptable in Production - customer BLOCKED > ------------------------------------------------------------------------------------------------- > > Key: AXIS2-5679 > URL: https://issues.apache.org/jira/browse/AXIS2-5679 > Project: Axis2 > Issue Type: Bug > Components: deployment > Affects Versions: 1.6.0 > Environment: Tomcat 7.0.51 and Axis2 1.6.1 > Reporter: Himakar Chennapragada > Priority: Blocker > > The server (Tomcat + Axis2) spins CPU/MIPS on idle when there is no workload when "hot deployment" is enabled in Axis2. When "hot deployment" is disabled there is no CPU spin. This needs urgent attention as our customer is CRITICALLY BLOCKED in PRODUCTION environment running hundreds of SOAP services. Restarting the server on every new service deployment is unacceptable because of the restart and restart also takes higher CPU because it loads all services in memory at server startup. Kindly look into this ASAP and any help highly appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org For additional commands, e-mail: java-dev-help@axis.apache.org