Return-Path: X-Original-To: apmail-deltacloud-dev-archive@www.apache.org Delivered-To: apmail-deltacloud-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 38546D775 for ; Fri, 19 Oct 2012 12:10:15 +0000 (UTC) Received: (qmail 27294 invoked by uid 500); 19 Oct 2012 12:10:15 -0000 Delivered-To: apmail-deltacloud-dev-archive@deltacloud.apache.org Received: (qmail 27166 invoked by uid 500); 19 Oct 2012 12:10:14 -0000 Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@deltacloud.apache.org Delivered-To: mailing list dev@deltacloud.apache.org Received: (qmail 27027 invoked by uid 99); 19 Oct 2012 12:10:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Oct 2012 12:10:12 +0000 Date: Fri, 19 Oct 2012 12:10:11 +0000 (UTC) From: "Marios Andreou (JIRA)" To: dev@deltacloud.apache.org Message-ID: <1890822000.507.1350648612017.JavaMail.jiratomcat@arcas> In-Reply-To: <351698185.57693.1350480724009.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (DTACLOUD-347) Deltacloud API leaking memory 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/DTACLOUD-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479969#comment-13479969 ] Marios Andreou commented on DTACLOUD-347: ----------------------------------------- michal's patch set @ http://tracker.deltacloud.org/set/97 seems to fix the mem leak: 127.0.0.1 - - [19/Oct/2012 14:43:38] "GET /api/images HTTP/1.1" 200 3319 0.0247 127.0.0.1 - - [19/Oct/2012 14:43:38] "GET /api/images HTTP/1.1" 200 3319 0.0095 127.0.0.1 - - [19/Oct/2012 14:43:38] "GET /api/images HTTP/1.1" 200 3319 0.0099 127.0.0.1 - - [19/Oct/2012 14:43:38] "GET /api/images HTTP/1.1" 200 3319 0.0104 ... 127.0.0.1 - - [19/Oct/2012 14:48:53] "GET /api/images HTTP/1.1" 200 3319 0.0230 127.0.0.1 - - [19/Oct/2012 14:48:53] "GET /api/images HTTP/1.1" 200 3319 0.0111 127.0.0.1 - - [19/Oct/2012 14:48:53] "GET /api/images HTTP/1.1" 200 3319 0.0112 127.0.0.1 - - [19/Oct/2012 14:48:53] "GET /api/images HTTP/1.1" 200 3319 0.0263 > Deltacloud API leaking memory > ----------------------------- > > Key: DTACLOUD-347 > URL: https://issues.apache.org/jira/browse/DTACLOUD-347 > Project: DeltaCloud > Issue Type: Bug > Components: Server > Environment: deltacloud-core, GIT adade32451815c8ee28e29be35636bd0f98473fc > Reporter: Michal Fojtik > Priority: Blocker > Labels: blocker-1.0.5 > > Deltacloud API memory usage is slowly increasing after doing 100+ requests: > Starting Deltacloud API :: mock :: http://localhost:3001/api > >> Thin web server (v1.5.0 codename Knife) > >> Debugging ON > >> Maximum connections set to 1024 > >> Listening on localhost:3001, CTRL+C to stop > 127.0.0.1 - - [17/Oct/2012 15:26:10] "GET /api/images HTTP/1.1" 200 4420 0.0308 > 127.0.0.1 - - [17/Oct/2012 15:26:17] "GET /api/images HTTP/1.1" 200 4420 0.0220 > 127.0.0.1 - - [17/Oct/2012 15:26:52] "GET /api/images HTTP/1.1" 200 4420 0.0219 > ... 1000 requests after: > 127.0.0.1 - - [17/Oct/2012 15:27:53] "GET /api/images HTTP/1.1" 200 4420 0.1539 > 127.0.0.1 - - [17/Oct/2012 15:27:53] "GET /api/images HTTP/1.1" 200 4420 0.1554 > 127.0.0.1 - - [17/Oct/2012 15:27:53] "GET /api/images HTTP/1.1" 200 4420 0.1526 > As you can see the response time is slowly increasing and after few minutes it gets to the point where the request take like 10 seconds to complete and all your free memory is gone ;-) > This is easy to reproduce: > 1. Start Deltacloud API ($ deltacloudd -i mock) > 2. $ while true; do curl -H 'Accept: application/xml' --user 'mockuser:mockpassword' http://localhost:3001/api/images > /dev/null; done > 3. Keep it running for ~1minute and watch the console with Deltacloud API log. > Thanks to Tomas Hrcka for reporting this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira