> We are running a web server, which holds our jsps and controller (the war
> file), and a backend app server, which holds our ejbs (the ear) file. We
> are running SunOne and log4j1.2.6
> 
> Everything runs fine until the log file needs to deleted as part of its
> rolling max size limit. The delete fails because the web server does not
> have the authority/privileges to delete from the app server and vice
> versa. 
> 
> I believe the problem is the result of our collection classes being built
> on one server and operated on by the other, and thus logging across jvms. 
> 
> I have been able to get everything to work by opening the security.policy
> to allow deletes. But that is a short term fix only, I can't rollout into
> production the ability to delete through our firewall. Another option is
> to set the log file size huge, then do cron-based delete during system
> shutdowns. I think we should be able to get this going within the normal
> log4j framework.
> 
> Has anyone else seen this and provided a more robust solution than the one
> above? I think I may be able to limit the delete entry in the
> security.policy to a single file or the log directory structure, but even
> that causes raised eyebrows here. Any help is greatly appreciated!!
> 
> Thanks!
> Bill Cameron (904) 281-4797
> Washington Mutual Bank
> 
> 
>       -----Original Message-----
>       From:   [EMAIL PROTECTED]
> [SMTP:[EMAIL PROTECTED]]
>       Sent:   Monday, December 23, 2002 3:05 PM
>       To:     [EMAIL PROTECTED]
>       Subject:        WELCOME to [EMAIL PROTECTED]
> 
>       Hi! This is the ezmlm program. I'm managing the
>       [EMAIL PROTECTED] mailing list.
> 
>       I'm working for my owner, who can be reached
>       at [EMAIL PROTECTED]
> 
>       Acknowledgment: I have added the address
> 
>          [EMAIL PROTECTED]
> 
>       to the log4j-user mailing list.
> 
>       Welcome to [EMAIL PROTECTED]!
> 
>       Please save this message so that you know the address you are
>       subscribed under, in case you later want to unsubscribe or change
> your
>       subscription address.
> 
> 
>       --- Administrative commands for the log4j-user list ---
> 
>       I can handle administrative requests automatically. Please
>       do not send them to the list address! Instead, send
>       your message to the correct command address:
> 
>       To subscribe to the list, send a message to:
>          <[EMAIL PROTECTED]>
> 
>       To remove your address from the list, send a message to:
>          <[EMAIL PROTECTED]>
> 
>       Send mail to the following for info and FAQ for this list:
>          <[EMAIL PROTECTED]>
>          <[EMAIL PROTECTED]>
> 
>       Similar addresses exist for the digest list:
>          <[EMAIL PROTECTED]>
>          <[EMAIL PROTECTED]>
> 
>       To get messages 123 through 145 (a maximum of 100 per request),
> mail:
>          <[EMAIL PROTECTED]>
> 
>       To get an index with subject and author for messages 123-456 , mail:
>          <[EMAIL PROTECTED]>
> 
>       They are always returned as sets of 100, max 2000 per request,
>       so you'll actually get 100-499.
> 
>       To receive all messages with the same subject as message 12345,
>       send an empty message to:
>          <[EMAIL PROTECTED]>
> 
>       The messages do not really need to be empty, but I will ignore
>       their content. Only the ADDRESS you send to is important.
> 
>       You can start a subscription for an alternate address,
>       for example "[EMAIL PROTECTED]", just add a hyphen and your
>       address (with '=' instead of '@') after the command word:
>       <[EMAIL PROTECTED]>
> 
>       To stop subscription for this address, mail:
>       <[EMAIL PROTECTED]>
> 
>       In both cases, I'll send a confirmation message to that address.
> When
>       you receive it, simply reply to it to complete your subscription.
> 
>       If despite following these instructions, you do not get the
>       desired results, please contact my owner at
>       [EMAIL PROTECTED] Please be patient, my owner is
> a
>       lot slower than I am ;-)
> 
>       --- Enclosed is a copy of the request I received.
> 
>       Return-Path: <[EMAIL PROTECTED]>
>       Received: (qmail 14152 invoked by uid 98); 23 Dec 2002 20:04:46
> -0000
>       Delivered-To:
> qmvirus-jakarta-log4j-user-sc.1040672896.mflghnjjjhjddnghjjid-BCameron=hom
> [EMAIL PROTECTED]
>       X-Antivirus: nagoya (v4218 created Aug 14 2002)
>       Received: (qmail 14132 invoked from network); 23 Dec 2002 20:04:44
> -0000
>       Received: from daedalus.apache.org (HELO apache.org) (63.251.56.142)
>         by nagoya.betaversion.org with SMTP; 23 Dec 2002 20:04:44 -0000
>       Received: (qmail 63910 invoked by uid 500); 23 Dec 2002 20:03:28
> -0000
>       Delivered-To:
> apmail-jakarta-log4j-user-sc.1040672896.mflghnjjjhjddnghjjid-BCameron=home
> [EMAIL PROTECTED]
>       Received: (qmail 63903 invoked from network); 23 Dec 2002 20:03:27
> -0000
>       Received: from smtp2.homeside.com (12.27.152.125)
>         by daedalus.apache.org with SMTP; 23 Dec 2002 20:03:27 -0000
>       Received: by HSLNT100JAX with Internet Mail Service (5.5.2653.19)
>               id <ZA68FX3Z>; Mon, 23 Dec 2002 14:48:11 -0500
>       Message-ID:
> <[EMAIL PROTECTED]>
>       From: "Cameron, Bill" <[EMAIL PROTECTED]>
>       To:
> "'log4j-user-sc.1040672896.mflghnjjjhjddnghjjid-BCameron=homeside.com@jaka
> rta.apache.org'"
>       
> <log4j-user-sc.1040672896.mflghnjjjhjddnghjjid-BCameron=homeside.com@jakar
> ta.apache.org>
>       Subject: RE: confirm subscribe to [EMAIL PROTECTED]
>       Date: Mon, 23 Dec 2002 14:48:08 -0500
>       MIME-Version: 1.0
>       X-Mailer: Internet Mail Service (5.5.2653.19)
>       Content-Type: text/plain
>       X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
> 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to