Return-Path: X-Original-To: apmail-batchee-dev-archive@minotaur.apache.org Delivered-To: apmail-batchee-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2AF1E18768 for ; Tue, 19 Jan 2016 09:53:43 +0000 (UTC) Received: (qmail 74154 invoked by uid 500); 19 Jan 2016 09:53:42 -0000 Delivered-To: apmail-batchee-dev-archive@batchee.apache.org Received: (qmail 74124 invoked by uid 500); 19 Jan 2016 09:53:42 -0000 Mailing-List: contact dev-help@batchee.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@batchee.incubator.apache.org Delivered-To: mailing list dev@batchee.incubator.apache.org Received: (qmail 74113 invoked by uid 99); 19 Jan 2016 09:53:42 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jan 2016 09:53:42 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 771C2C21B7 for ; Tue, 19 Jan 2016 09:53:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.779 X-Spam-Level: * X-Spam-Status: No, score=1.779 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id KW2LVx7VBJeV for ; Tue, 19 Jan 2016 09:53:41 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with SMTP id EB79E256E0 for ; Tue, 19 Jan 2016 09:53:40 +0000 (UTC) Received: (qmail 73946 invoked by uid 99); 19 Jan 2016 09:53:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jan 2016 09:53:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D3C802C1F5D for ; Tue, 19 Jan 2016 09:53:39 +0000 (UTC) Date: Tue, 19 Jan 2016 09:53:39 +0000 (UTC) From: "Mark Struberg (JIRA)" To: dev@batchee.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (BATCHEE-90) On the Apache JBatch GUI main screen it would be nice to see the status of all the batches MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/BATCHEE-90?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1510= 6522#comment-15106522 ]=20 Mark Struberg commented on BATCHEE-90: -------------------------------------- Another problem is that a server shutdown seems to not stop those batches p= roperly? Didn't look at those code parts in detail, but just a gut feeling.= .. Imo we should try to stop all the running batches if the whole server gets = shut down.=20 Probably try to wait for some specified amount of time (60 seeconds? config= urable?) and then kill them? > On the Apache JBatch GUI main screen it would be nice to see the status o= f all the batches > -------------------------------------------------------------------------= ----------------- > > Key: BATCHEE-90 > URL: https://issues.apache.org/jira/browse/BATCHEE-90 > Project: BatchEE > Issue Type: Wish > Reporter: =C3=81kos Koz=C3=A1k > Labels: gui > Attachments: gui_one_batch_is_running.png > > > Normally you can get the status of one Batch instance on the instances pa= ge. This is good, but if you open up the GUI main screen, you cannot decide= whether one Batch is running or not. You need to open up all instances pag= e for every batch and check.=20 > This is critical, if you running a not restart-able Batch job, or any kin= d of, and you want to stop the application. > It should be some kind of monitoring like an icon, URL or a text on the s= tart page (see attach). > Or it would be maybe also useful to have a link with the running instance= s. Then if interested, you just click on the link, and you get your informa= tion. Maybe the loading of the main page will be then not slower because th= e background status checks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)