This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 76689 - Log files not written
Summary: Log files not written
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Sherold Dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-22 15:56 UTC by tkellerer
Modified: 2006-06-01 14:59 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tkellerer 2006-05-22 15:56:58 UTC
Using 5.5 dev build 200605190200 with JDK 1.5

When starting the built-in Tomcat, the two tabs in the output window do show the
log files from Tomcat. The tab labelled "Bundled Tomcat (5.5.16) shows the
contenst of the localhost.log file. When starting the server a file is created
in <userdir>/apache-tomcat-5.5.16_base/logs/localhost.2006-05-22.log but the
length of the file is zero bytes (even though I do see messages - especially my
own System.out.println() messages - in the output tab.

The log file is also not written when shutting down the internal Tomcat
Comment 1 Sherold Dev 2006-05-22 17:10:13 UTC
tm -> 5.5

the problem seems to be that the logging.properties file is not copied to the
tomcat base directory while the base directory is being generated
Comment 2 Sherold Dev 2006-05-23 10:50:37 UTC
F.

Checking in src/org/netbeans/modules/tomcat5/TomcatManager.java;
/cvs/tomcatint/tomcat5/src/org/netbeans/modules/tomcat5/TomcatManager.java,v 
<--  TomcatManager.java
new revision: 1.76.6.2.2.4; previous revision: 1.76.6.2.2.3
done
Comment 3 tkellerer 2006-05-31 10:33:39 UTC
Still happens with daily build 200605300200

Comment 4 Sherold Dev 2006-05-31 10:58:02 UTC
I've just rechecked it and it works.

Did you delete your catalina base directory (or the whole netbeans user
directory) so that the catalina base dir could get regenerated?

If you did and if you think that it still does not work you can try it out by
adding the following code in some jsp page, deploy it on Tomcat and then open it
up in a browser.

<%
  java.util.logging.Logger.getAnonymousLogger().warning("This goes to the server
output");
  log("This goes to the server log");
%>
Comment 5 tkellerer 2006-05-31 12:51:38 UTC
OK it works with a completely new project and an empty userdir. It works then.
But  it does not work with an empty userdir and an existing project. Is there
anything in the project definition that prevents this?

The project was created before this fix was available...
Comment 6 Sherold Dev 2006-05-31 13:00:21 UTC
No, nothing in the project definition should have anything to do with it. The
fix should work also for older projects.

The only thing that the fix of this issue does is copying the logging.properties
file to the catalina base directory.
Comment 7 tkellerer 2006-05-31 14:02:29 UTC
It seems to be related to the usage of log4j in the web application, because in
another web-appliction (i.e. NB Project) things are working fine. 

Gues I'll have to do the debuggin on our side ;)

Sorry for the confusion
Comment 8 Jaroslav Pospisil 2006-06-01 14:59:06 UTC
VERIFIED