You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by lo...@jakarta.apache.org on 2003/03/26 07:24:01 UTC
ezmlm probe
Hi! This is the ezmlm program. I'm managing the
log4j-dev@jakarta.apache.org mailing list.
I'm working for my owner, who can be reached
at log4j-dev-owner@jakarta.apache.org.
Messages to you from the log4j-dev mailing list seem to
have been bouncing. I sent you a warning message, but it bounced.
I've attached a copy of the bounce message.
This is a probe to check whether your address is reachable. If this
probe bounces, I will remove your address from the
log4j-dev@jakarta.apache.org mailing list, without further notice. You can re-subscribe
by sending an empty message to the following address:
<lo...@jakarta.apache.org>
--- Enclosed is a copy of the bounce message I received.
Return-Path: <>
Received: (qmail 57950 invoked from network); 14 Mar 2003 11:24:49 -0000
Received: from exchange.sun.com (192.18.33.10)
by daedalus.apache.org with SMTP; 14 Mar 2003 11:24:49 -0000
Received: (qmail 29511 invoked for bounce); 14 Mar 2003 11:26:43 -0000
Date: 14 Mar 2003 11:26:43 -0000
From: MAILER-DAEMON@nagoya.betaversion.org
To: log4j-dev-return-warn-1047641085.bencfpgaandcnpdiejcm-qmlist-jakarta-archive-log4j-dev=nagoya.apache.org@jakarta.apache.org
Subject: failure notice
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
Hi. This is the qmail-send program at nagoya.betaversion.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<qm...@nagoya.betaversion.org>:
/opt/ezmlm/sbin/archive: Cannot open file "/opt/ezmlm/archive/jakarta.apache.org/log4j-dev/200303"
--- Below this line is a copy of the message.
Return-Path: <lo...@jakarta.apache.org>
Received: (qmail 29506 invoked from network); 14 Mar 2003 11:26:43 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
by nagoya.betaversion.org with SMTP; 14 Mar 2003 11:26:43 -0000
Received: (qmail 57656 invoked by uid 500); 14 Mar 2003 11:24:45 -0000
Mailing-List: contact log4j-dev-help@jakarta.apache.org; run by ezmlm
Date: 14 Mar 2003 11:24:45 -0000
Message-ID: <10...@jakarta.apache.org>
From: log4j-dev-help@jakarta.apache.org
To: qmlist-jakarta-archive-log4j-dev@nagoya.apache.org
Content-type: text/plain; charset=us-ascii
Subject: ezmlm warning
Hi! This is the ezmlm program. I'm managing the
log4j-dev@jakarta.apache.org mailing list.
I'm working for my owner, who can be reached
at log4j-dev-owner@jakarta.apache.org.
Messages to you from the log4j-dev mailing list seem to
have been bouncing. I've attached a copy of the first bounce
message I received.
If this message bounces too, I will send you a probe. If the probe bounces,
I will remove your address from the log4j-dev mailing list,
without further notice.
I've kept a list of which messages from the log4j-dev mailing list have
bounced from your address.
Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per request),
send an empty message to:
<lo...@jakarta.apache.org>
To receive a subject and author list for the last 100 or so messages,
send an empty message to:
<lo...@jakarta.apache.org>
Here are the message numbers:
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
--- Enclosed is a copy of the bounce message I received.
Return-Path: <>
Received: (qmail 96048 invoked from network); 2 Mar 2003 17:06:27 -0000
Received: from exchange.sun.com (192.18.33.10)
by daedalus.apache.org with SMTP; 2 Mar 2003 17:06:27 -0000
Received: (qmail 4850 invoked for bounce); 2 Mar 2003 17:08:07 -0000
Date: 2 Mar 2003 17:08:07 -0000
From: MAILER-DAEMON@nagoya.betaversion.org
To: log4j-dev-return-3513-qmlist-jakarta-archive-log4j-dev=nagoya.apache.org@jakarta.apache.org
Subject: failure notice
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
Hi. This is the qmail-send program at nagoya.betaversion.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<qm...@nagoya.betaversion.org>:
/opt/ezmlm/sbin/archive: Cannot open file "/opt/ezmlm/archive/jakarta.apache.org/log4j-dev/200303"
--- Below this line is a copy of the message.
Return-Path: <lo...@jakarta.apache.org>
Received: (qmail 4845 invoked from network); 2 Mar 2003 17:08:07 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
by nagoya.betaversion.org with SMTP; 2 Mar 2003 17:08:07 -0000
Received: (qmail 95783 invoked by uid 500); 2 Mar 2003 17:06:25 -0000
Mailing-List: contact log4j-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <ma...@jakarta.apache.org>
List-Subscribe: <ma...@jakarta.apache.org>
List-Help: <ma...@jakarta.apache.org>
List-Post: <ma...@jakarta.apache.org>
List-Id: "Log4J Developers List" <log4j-dev.jakarta.apache.org>
Reply-To: "Log4J Developers List" <lo...@jakarta.apache.org>
Delivered-To: mailing list log4j-dev@jakarta.apache.org
Received: (qmail 95761 invoked from network); 2 Mar 2003 17:06:25 -0000
Received: from exchange.sun.com (192.18.33.10)
by daedalus.apache.org with SMTP; 2 Mar 2003 17:06:25 -0000
Received: (qmail 4839 invoked by uid 50); 2 Mar 2003 17:08:05 -0000
Date: 2 Mar 2003 17:08:05 -0000
Message-ID: <20...@nagoya.betaversion.org>
From: bugzilla@apache.org
To: log4j-dev@jakarta.apache.org
Cc:
Subject: DO NOT REPLY [Bug 14933] -
NDC stack not serializable
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14933>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14933
NDC stack not serializable
------- Additional Comments From horst.scheruga@gmx.at 2003-03-02 17:08 -------
I have developed a multi tier web application with a Web-Container and a self
made Application-Server.
I patched the Diagnostic Context to be serializable, because it is a very
valueable feature in our environment, to know wich request on the WebServer
causes calls on the Application Server.
The connection between the Web-Container and the Application-Server is over
Corba (Visibroker) so we need the serialization.
We have a lot of advantages to have the DiagnosticContext beeing serializable
and I do not see any disadvantage, so where is the problem to make it
serializable?
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org