headers
bugzilla | 1 Jun 2007 11:15
Picon
Favicon

DO NOT REPLY [Bug 42562] New: - log4j writing in old files

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG路
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42562>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND路
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42562

           Summary: log4j writing in old files
           Product: Log4j
           Version: 1.2beta
          Platform: Sun
        OS/Version: AIX
            Status: NEW
          Severity: critical
          Priority: P1
         Component: Appender
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: jnarula <at> hcl.in

Hello,

we have implemented on logging facility in our web services.
problem: there are 2 web services (WS) A and B. then when users start hitting
the WS loggers start writing in a log file.
the java code creates an obj of logger using getlogger(). assuming if A WS has
created an object of the logger then it will be reused by B WS or any other call
to any WS.
The log files are created daily using DailyRollingFileAppender.
after running for a couple of days the logger starts writing into an old log
(Continue reading)

Permalink | Reply | 1 comment |
headers
bugzilla | 3 Jun 2007 03:04
Picon
Favicon

DO NOT REPLY [Bug 42568] New: - Sometimes log to file an sometime don磘.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG路
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42568>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND路
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42568

           Summary: Sometimes log to file an sometime don麓t.
           Product: Log4j
           Version: unspecified
          Platform: Other
        OS/Version: Solaris
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Configurator
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: angelfloresp <at> gmail.com

My component uses many "logs files", i 麓m not sure how many logs files uses the 
other component.

 
For the moment i prefer not use the other logs but only one:

               Logger   logger     = Logger.getLogger(getClass().getName());
               //Logger  responselogger     = Logger.getLogger
( "responseLogger." + getClass().getName()); 
               //Logger  consultlogger       = Logger.getLogger
(Continue reading)

Permalink | Reply | 1 comment |
headers
bugzilla | 3 Jun 2007 03:14
Picon
Favicon

DO NOT REPLY [Bug 42568] - Sometimes log to file an sometime don磘.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG路
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42568>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND路
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42568

hoju <at> visi.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

------- Additional Comments From hoju <at> visi.com  2007-06-02 18:14 -------
You have not described a bug in Log4j.  You've asked a question.  Bugzilla is
not for questions.  That's what the log4j-user list is for.  Please subscribe to
it and ask your question there.  Marking invalid.

http://logging.apache.org/site/mailing-lists.html

Jake

--

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
Permalink | Reply | 0 comments |
headers
Paul Smith | 3 Jun 2007 05:30

Chainsaw & Maven

Hi all,

I've begin on a maven journey recently, and I'm convinced of it's  
value.  I would like to mavenize the Chainsaw project as  part of  
integrating it with log4j 1.2.15.

It would be nice to do a set of small directory changes to fit the  
standard maven project; we're not far off it, and it's not strictly  
necessary, but I think keeping the structure standard is probably  
worth the investment.

So, I'm proposing we do the following:

src/java -> src/main/java
mv *.properties into src/main/resources tree (there's only one)
test -> src/test/java
packaging/* -> src/jnlp/resources

I have found the appassembler and webstart maven plugins to be  
outstandingly useful.  Out of the box building .sh/.bat and webstart  
distributions.  Much simpler than my ant hack!

The zeroconf src tree is an interesting one.  The reason that it is  
in a separate source tree in the first place is to make it 'optional'  
during the build cycle because the jmdns  library is LGPL.  With  
maven, by declaring the dependency it just goes and gets it.  I'm not  
sure what it means for Gump though.  Does gump handle maven  
projects?  That is, are we required to provide a build.xml for Gump?

The maven-eclipse plugin (and assuming IDEA) are fantastic.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Scott Deboy | 3 Jun 2007 06:31

RE: Chainsaw & Maven

+1

Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR  97201

Telephone:      503.224.7496
Cell:           503.997.1367
Fax:            503.222.0185

sdeboy <at> comotivsystems.com

www.comotivsystems.com

-----Original Message-----
From: Paul Smith [mailto:psmith <at> aconex.com]
Sent: Sat 6/2/2007 8:30 PM
To: Log4J Developers List
Subject: Chainsaw & Maven

Hi all,

I've begin on a maven journey recently, and I'm convinced of it's  
value.  I would like to mavenize the Chainsaw project as  part of  
integrating it with log4j 1.2.15.

It would be nice to do a set of small directory changes to fit the  
standard maven project; we're not far off it, and it's not strictly  
necessary, but I think keeping the structure standard is probably
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jacob Kjome | 3 Jun 2007 08:26
Favicon

RE: Chainsaw & Maven


+1

Seems to be the way to go these days.  If it makes project management 
easier, it's worth doing.

Jake

At 11:31 PM 6/2/2007, you wrote:
 >+1
 >
 >
 >
 >Scott Deboy
 >COMOTIV SYSTEMS
 >111 SW Columbia Street Ste. 950
 >Portland, OR  97201
 >
 >Telephone:      503.224.7496
 >Cell:           503.997.1367
 >Fax:            503.222.0185
 >
 >sdeboy <at> comotivsystems.com
 >
 >www.comotivsystems.com
 >
 >
 >
 >-----Original Message-----
 >From: Paul Smith [mailto:psmith <at> aconex.com]
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul Smith | 4 Jun 2007 02:14

Chainsaw & Maven: completed (I think)

Ok gang, mavenization completed I think.

Please grab maven 2.0.4 and install it, and if you use Eclipse,  
install the Maven Eclipse plugin:

http://maven.apache.org/
http://m2eclipse.codehaus.org/

After installing the Maven Eclipse plugin, you can activate the  
project as a Maven project by doing this in Eclipse:

* Right click on the project
* Team->Maven->Enable (if it's not already enabled)
* Team->Maven->Update Source Folders (even if it is enabled, I've  
found you sometimes need to do this to 'nudge' the plugin to refresh  
it's view of things)

You will need to have installed into your local repository the  
snapshot releases of the log4j-* projects (component, receivers,  
expression-filter) as well as the log4j 1.2.15 snapshot.  The steps  
involve:

cd <sub-project>
mvn install

Once mvn install works well, you can try 'mvn package' and it will  
produce:

* target/appassembler/bin/chainsaw shell script and chainsaw.bat  
batch file which can be used to launch Chainsaw from the command line
(Continue reading)

Permalink | Reply | 5 comments |
headers
Scott Deboy | 4 Jun 2007 07:35

RE: Chainsaw & Maven: completed (I think)

Got it all working.  A few things:
- getting the log4j 1.2 branch to mvn install was a bit of a hassle because I needed to get
nteventappender.dll into my path (from 1.2.14) - the dll wasn't getting built via mvn install - should it
have been? maybe another maven target I should have looked into.
- I had to install each of the log4j snapshots into my local repo (the mvn install error info told me to do it - it
wasn't mentioned in the build instructions)
- Chainsaw wouldn't mvn install until I copied known.receivers to chainsaw/target/classes (was getting
an error on the receivershelpertest)

Will play around with things now and let you know how things go.

Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR  97201

Telephone:      503.224.7496
Cell:           503.997.1367
Fax:            503.222.0185

sdeboy <at> comotivsystems.com

www.comotivsystems.com

-----Original Message-----
From: Paul Smith [mailto:psmith <at> aconex.com]
Sent: Sun 6/3/2007 5:14 PM
To: Log4J Developers List
Subject: Chainsaw & Maven: completed (I think)
(Continue reading)

Permalink | Reply | 4 comments |
headers
bugzilla | 4 Jun 2007 08:08
Picon
Favicon

Bug report for Log4j [2007/06/03]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker     CRI=Critical    MAJ=Major             |
|     |   |           MIN=Minor       NOR=Normal      ENH=Enhancement       |
|     |   |   +-------------------------------------------------------------+
|     |   |   | Date Posted                                                 |
|     |   |   |          +--------------------------------------------------+
|     |   |   |          | Description                                      |
|     |   |   |          |                                                  |
|  569|Ver|Cri|2001-02-09|fully qualified class name used as category name c|
|13099|Opn|Nor|2002-09-27|DOMConfigurator ignores category factory setting  |
|14350|New|Enh|2002-11-07|Patch to substitute variables in the log4j.configu|
|15585|Ver|Maj|2002-12-20|log4j does not show Class Name, Method, or Line Nu|
|16280|Opn|Min|2003-01-21|Error Message always logged to log4j when calling |
|17498|New|Nor|2003-02-27|Logging inconsistencies using DailyRollingFileAppe|
|17531|Ass|Min|2003-02-28|PropertyConfigurator.configureAndWatch() don't res|
|17887|Opn|Maj|2003-03-11|RollingFileAppender does not work for 10 threads  |
|20395|New|Enh|2003-06-01|PreparedStatementAppender Enhancement             |
|22894|Opn|Nor|2003-09-02|Single backslash not accepted in File param value |
|22934|Opn|Nor|2003-09-04|org.apache.log4j.jmx is not compatible with JMX 1.|
|23329|Ass|Maj|2003-09-22|<logger> element in XML config should support reso|
|25106|Opn|Enh|2003-12-01|Support XInclude in XML configuration scripts     |
|25107|New|Enh|2003-12-01|OptionConverter.getSystemProperty() does not allow|
|25355|New|Enh|2003-12-09|allow to require "TLS/SSL only" for outgoing mails|
|25747|New|Enh|2003-12-24|more explanations when hitting "WARN No appenders |
|26084|New|Nor|2004-01-13|Log Event detail panel does not show special chara|
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul Smith | 4 Jun 2007 08:13

Re: Chainsaw & Maven: completed (I think)


> Got it all working.  A few things:
> - getting the log4j 1.2 branch to mvn install was a bit of a hassle  
> because I needed to get nteventappender.dll into my path (from  
> 1.2.14) - the dll wasn't getting built via mvn install - should it  
> have been? maybe another maven target I should have looked into.

Weird, I didn't need to do that (but then I'm not on Windows).

> - I had to install each of the log4j snapshots into my local repo  
> (the mvn install error info told me to do it - it wasn't mentioned  
> in the build instructions)

Hmm, I did update HOWTOBUILD.txt that mentioned that one needed to do  
a 'mvn install' in each repo.  Did you do that? If you did, did it  
still force you to do the manual install?)

> - Chainsaw wouldn't mvn install until I copied known.receivers to  
> chainsaw/target/classes (was getting an error on the  
> receivershelpertest)
>
Ahh, I understand now, but what's weird is that some timse the tests  
pass for me, but sometimes they don't.

You can work around this by doing:

  mvn package -Dmaven.test.skip=true

I'll look into it.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane