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 38C09200BC3 for ; Fri, 18 Nov 2016 15:25:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3748C160B04; Fri, 18 Nov 2016 14: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 80126160AFE for ; Fri, 18 Nov 2016 15:25:03 +0100 (CET) Received: (qmail 45727 invoked by uid 500); 18 Nov 2016 14:24:57 -0000 Mailing-List: contact user-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@karaf.apache.org Delivered-To: mailing list user@karaf.apache.org Received: (qmail 45716 invoked by uid 99); 18 Nov 2016 14:24:57 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Nov 2016 14:24:57 +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 43857C1434 for ; Fri, 18 Nov 2016 14:24:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.479 X-Spam-Level: X-Spam-Status: No, score=0.479 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=telensa-com.20150623.gappssmtp.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id R3eUsel15jPz for ; Fri, 18 Nov 2016 14:24:56 +0000 (UTC) Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 86AD95F570 for ; Fri, 18 Nov 2016 14:24:55 +0000 (UTC) Received: by mail-wm0-f53.google.com with SMTP id f82so40917528wmf.1 for ; Fri, 18 Nov 2016 06:24:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telensa-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=jDN2qUHR6QTpLmiChJ0/jCTvacJY0YExesgeri03ppk=; b=yXY6WB+/Upyw1LJYJ1d3eCFs9mEZv91RteqMexN4QAtVMQTMvb+cUuiGGjXbOjleN4 2Qd8s1qQs/tZ1hVD1zuuXqo8DO/smYIBOqEtseDcYSlE6dPBjMKjKBipgJyEPCPUd31I qWXF0ZDw6pNwTff88HFVaocjK4cR/8X3CnwABLq2pCE+d+85UhCx++Y/Wq2sDxCBi1XS cxuIOuMBb4yDXIbQNrhNP6xHkcRQmeANy/xCzBRxxpTjLgyVk0tqxp3P43AAWMbgzRKI KzpMQ3wuIU27SAFJx+17thR9b6caODSZPcCGnkhWww+D58AUlKwfz9NXB6REu9JCUHo6 9MLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=jDN2qUHR6QTpLmiChJ0/jCTvacJY0YExesgeri03ppk=; b=PFSONRe5E54vAkZEfmHjI+EbV5qA/yDZD3Ea8Is8MKBqIU1FeTFmXg5zJJTVIEX4bl TVkWMNJUkrtGvMC7YNXdDzlymI3IGdCs5eXqM9gXwJqa6HC6BNWHhoEQb+l54WK4aCQk z54664qIdONXx6Ltqov+dEYsaIwguMXVLbvcur44HP/ODmQKlTy7HjeENOMDtuUtsDOv 7+XP984aLaWTPDNf8eag6Re3Fn7Rbb1qSLZrekFo2OVYvWKUNpvP/dkFQXpQ1cgLLbzF qkozOQWbP481oT0qcTIbjycDuBi+xKxVnHs+zUD2mBbwU2exmEPP9Ait9BCWA/0gQCD1 6Wnw== X-Gm-Message-State: AKaTC01JXvawJ2ta1gpGaD7zJj4E9pt3Y56oM6hFgevMXG/izsk9Tgv1HP5ZXNJHCttlg7uv X-Received: by 10.28.105.194 with SMTP id z63mr414007wmh.78.1479479094908; Fri, 18 Nov 2016 06:24:54 -0800 (PST) Received: from [10.0.0.133] ([81.187.182.225]) by smtp.gmail.com with ESMTPSA id v2sm9098951wja.41.2016.11.18.06.24.54 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Nov 2016 06:24:54 -0800 (PST) Subject: Re: Beginner's question - Jetty configuration To: user@karaf.apache.org References: From: Tim Ward Message-ID: <225d4091-1999-d6d3-b915-fb9d051ebe03@telensa.com> Date: Fri, 18 Nov 2016 14:24:52 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit archived-at: Fri, 18 Nov 2016 14:25:04 -0000 Thanks, but as I said, that's one of the things I tried: "I've tried creating a gibberish jetty.xml, pointed to by org.ops4j.pax.web.config.file in org.ops4j.paw.web.cfg, in the hope of getting some error messages about the gibberish, showing that at least something was reading the jetty.xml, but that didn't work." (Typo in the above, of course I meant org.ops4j.pax.web.cfg not org.ops4j.paw.web.cfg.) I expected to see something in log\karaf.log telling me about syntax errors in the jetty.xml, but I didn't, even at DEBUG level, so I can have no confidence that the jetty.xml was read (and thus no obvious incentive to invest further time working out what to put in it). On 18/11/2016 14:16, Jean-Baptiste Onofré wrote: > Hi Tim, > > when you install the jetty feature, you can override the default > configuration using etc/org.ops4j.pax.web.cfg. > > This cfg file can refer to a jetty.xml using: > > org.ops4j.pax.web.config.file=${karaf.base}/etc/jetty.xml > > Then the etc/jetty.xml is a jetty file. > > Regards > JB > > On 11/18/2016 03:11 PM, Tim Ward wrote: >> Very simple, I hope, but days of research haven't found an answer that >> works yet. >> >> How do change the configuration of Jetty in Karaf? As the simplest >> possible initial beginner's question, how do I turn on request logging? >> >> The osgi-dev mailing list referred me here. >> >> (I can actually see what it's doing with requests by setting the log >> level to DEBUG in org.ops4j.pax.logging.cfg and then looking in >> data\log\karaf.log, but given the volume and format of output that's not >> a practical solution. >> >> I've tried putting stuff like >> org.ops4j.pax.web.log.ncsa.format=yyyy_mm_dd.request.log in >> org.ops4j.paw.web.cfg but that doesn't seen to do anything. >> >> I've tried creating a gibberish jetty.xml, pointed to by >> org.ops4j.pax.web.config.file in org.ops4j.paw.web.cfg, in the hope of >> getting some error messages about the gibberish, showing that at least >> something was reading the jetty.xml, but that didn't work. It didn't >> work doing the same via configuration.json either. >> >> I haven't really found any actual *documentation* of any of the above, >> just snippets of example code, so all my attempts were probably wrong >> anyway.) >> >> -- >> Tim Ward >> > -- Tim Ward