Return-Path: 
 <issues-return-7318-apmail-geode-issues-archive=geode.apache.org@geode.incubator.apache.org>
X-Original-To: apmail-geode-issues-archive@minotaur.apache.org
Delivered-To: apmail-geode-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id EBBA0188F7
	for <apmail-geode-issues-archive@minotaur.apache.org>;
 Thu,  3 Mar 2016 21:27:20 +0000 (UTC)
Received: (qmail 14018 invoked by uid 500); 3 Mar 2016 21:27:20 -0000
Delivered-To: apmail-geode-issues-archive@geode.apache.org
Received: (qmail 13990 invoked by uid 500); 3 Mar 2016 21:27:20 -0000
Mailing-List: contact issues-help@geode.incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@geode.incubator.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@geode.incubator.apache.org>
List-Post: <mailto:issues@geode.incubator.apache.org>
List-Id: <issues.geode.incubator.apache.org>
Reply-To: dev@geode.incubator.apache.org
Delivered-To: mailing list issues@geode.incubator.apache.org
Received: (qmail 13981 invoked by uid 99); 3 Mar 2016 21:27:20 -0000
Received: from pnap-us-west-generic-nat.apache.org (HELO
 spamd4-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Mar 2016 21:27:20 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org)
 with ESMTP id 74081C06C5
	for <issues@geode.apache.org>; Thu,  3 Mar 2016 21:27:20 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -4.349
X-Spam-Level: 
X-Spam-Status: No, score=-4.349 tagged_above=-999 required=6.31
	tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5,
	RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
	RP_MATCHES_RCVD=-0.329] autolearn=disabled
Received: from mx1-lw-eu.apache.org ([10.40.0.8])
	by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new,
 port 10024)
	with ESMTP id ibEm1vFmMg_k for <issues@geode.apache.org>;
	Thu,  3 Mar 2016 21:27:19 +0000 (UTC)
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP
 id 149AC5F571
	for <issues@geode.incubator.apache.org>;
 Thu,  3 Mar 2016 21:27:18 +0000 (UTC)
Received: (qmail 12553 invoked by uid 99); 3 Mar 2016 21:27:18 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Mar 2016 21:27:18 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 1F04A2C1F5C
	for <issues@geode.incubator.apache.org>;
 Thu,  3 Mar 2016 21:27:18 +0000 (UTC)
Date: Thu, 3 Mar 2016 21:27:18 +0000 (UTC)
From: "Jens Deppe (JIRA)" <jira@apache.org>
To: issues@geode.incubator.apache.org
Message-ID: <JIRA.12933460.1453493802000.213206.1457040438124@Atlassian.JIRA>
In-Reply-To: <JIRA.12933460.1453493802000@Atlassian.JIRA>
References: <JIRA.12933460.1453493802000@Atlassian.JIRA>
 <JIRA.12933460.1453493802273@arcas>
Subject: [jira] [Updated] (GEODE-834) Java Util Logging not showing up on
 server logs
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/GEODE-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Deppe updated GEODE-834:
-----------------------------
    Component/s:     (was: management)
                 logging

> Java Util Logging not showing up on server logs
> -----------------------------------------------
>
>                 Key: GEODE-834
>                 URL: https://issues.apache.org/jira/browse/GEODE-834
>             Project: Geode
>          Issue Type: Bug
>          Components: logging
>            Reporter: William Markito Oliveira
>
> When trying to use java.util.logging.Logger from a callback (CacheWriter, Listeners..) it looks like the output is not being displayed on <server>.log 
> I've checked gemfire-core-dependencies/META-INF/MANIFEST.mf and we are including log4j-jul-2.5.jar which was supposed to the bridge and capture those calls. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)