Return-Path: X-Original-To: apmail-openejb-commits-archive@www.apache.org Delivered-To: apmail-openejb-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BF11DD055 for ; Sun, 25 Nov 2012 20:58:58 +0000 (UTC) Received: (qmail 49013 invoked by uid 500); 25 Nov 2012 20:58:58 -0000 Delivered-To: apmail-openejb-commits-archive@openejb.apache.org Received: (qmail 48984 invoked by uid 500); 25 Nov 2012 20:58:58 -0000 Mailing-List: contact commits-help@openejb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openejb.apache.org Delivered-To: mailing list commits@openejb.apache.org Received: (qmail 48977 invoked by uid 99); 25 Nov 2012 20:58:58 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Nov 2012 20:58:58 +0000 Date: Sun, 25 Nov 2012 20:58:58 +0000 (UTC) From: "Howard W. Smith, Jr. (JIRA)" To: commits@openejb.apache.org Message-ID: <1481038043.21559.1353877138705.JavaMail.jiratomcat@arcas> In-Reply-To: <489527687.21189.1353837658357.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (OPENEJB-1955) TomEE 1.5.1 SNAPSHOT running slow on my production server; may be caused by Atmosphere 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/OPENEJB-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503550#comment-13503550 ] Howard W. Smith, Jr. commented on OPENEJB-1955: ----------------------------------------------- pf_OrdersController is 'huge' in size (or byte count, lines of code). That is the core of the web application. I couldn't even find pf_OrdersController in jvisualvm output; I'm glad you found it. Evidently, I was looking at the output incorrectly. I just navigated through some of the pages. I guess it is best to do one jvisualvm output file per page in JSF web app. Along with what Mark recommended about rendered=, i need to eliminate/minimize use of rendered=... and I need to move much of the (potentially-stateless) code in pf_OrdersController to @CDI RequestScoped or @Stateless. So, PrimeFaces Push (Atmosphere) is not the cause of this problem? FYI, PrimeFaces Push (Atmosphere) is working perfectly/flawlessly in TomEE/Windows Server 2003 environment; it pushes. You think it is injection of pf_OrdersController? > TomEE 1.5.1 SNAPSHOT running slow on my production server; may be caused by Atmosphere > -------------------------------------------------------------------------------------- > > Key: OPENEJB-1955 > URL: https://issues.apache.org/jira/browse/OPENEJB-1955 > Project: OpenEJB > Issue Type: Question > Components: container system > Affects Versions: 1.6.0 > Environment: Windows Server 2003, 32-bit, PrimeFaces 3.5 SNAPSHOT, PrimeFaces Push (Atmosphere/websockets) configured; > Internet connection is powered by Verizon Wireless 4G > Reporter: Howard W. Smith, Jr. > Priority: Minor > Labels: 2003, atmosphere, server, tomee, windows > Fix For: 1.6.0 > > Attachments: jvisualvm_tomee_excel_smaller.csv, jvisualvm_tomee.html, jvisualvm_tomee.nps, jvisualvm_tomee_smaller.csv, jvisualvm_tomee_smaller.html, web.xml > > Original Estimate: 612h > Remaining Estimate: 612h > > I was working with Romain and Mark Struberg on this one, and decided to open an issue, so I could attach files and continue discussion here. > My JSF web application is running really slow on production server (Windows Server 2003 32-bit Verizon Wireless 4G internet connection); runs faster on Windows Server 2008 64bit (cablemodem internet connection). > Per Romain and Mark, I ran jvisualvm, and it appears as though Atmosphere 'may' be slowing down the web app, or the root cause. > Please review attached files and confirm and advise. -- 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