| How to enable logging when running Tomcat 5.5 under Eclipse 3.5? [message #515548] |
Fri, 19 February 2010 05:50  |
Eclipse User |
|
|
|
Hi, I'm running Tomcat 5.5 under Eclipse 3.5. I want to see some access logging because for instance it silently ignores imported style sheets it can't find. I saw a reference somewhere to org.apache.catalina.valves.AccessLogValve so I tried uncommenting that in server.xml but it makes no difference. Nothing extra to the console, nothing to any log file in the workspace.
This is all I get in the console window:
Created MBeanServer with ID: 635da44f:126e1e2f13c:-8000:Dylan:1
18-Feb-2010 16:22:13 org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [deleted]
18-Feb-2010 16:22:13 org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
18-Feb-2010 16:22:13 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1046 ms
18-Feb-2010 16:22:13 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
18-Feb-2010 16:22:13 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.28
18-Feb-2010 16:22:13 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
18-Feb-2010 16:22:18 org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
18-Feb-2010 16:22:18 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
18-Feb-2010 16:22:18 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/156 config=null
18-Feb-2010 16:22:18 org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
18-Feb-2010 16:22:18 org.apache.catalina.startup.Catalina start
INFO: Server startup in 5094 ms
Thanks!
Dave
|
|
|
|
|
| Re: How to enable logging when running Tomcat 5.5 under Eclipse 3.5? [message #515672 is a reply to message #515665] |
Fri, 19 February 2010 12:30  |
| Eclipse User |
|
|
|
Dave Griffiths wrote:
> Hi, thanks. I figured it out in the end. Like you say for a fresh
> project that works. What I did though was make the server.xml change
> after a few server start/restart iterations. What I had to do to fix it
> - which I think I found on the web somewhere - was right click on the
> server in the bottom pane and then do "Clean...". Odd really because you
> make a change to a servlet and it Just Works but make a change to
> server.xml and it's very obscure...
If it helps in the future, for "Clean..." to fix the behavior suggests
that something went wrong with the "delta" publishing. The "delta"
publishing that the Tomcat support uses relies on a cache of data
storing the files and their dates for what has been included in past
publishes. If during publishing, the project file to be published is
found in the cache and it's date hasn't changed, then that file is not
published again. If that file, for some unknown reason, is no longer
present in the published webapp, "delta" publishing won't make it
reappear. Using "Clean..." deletes this cache and forces a full
publish, fixing any such disappearances. So far, I haven't identified
any usage scenario, other than deliberately deleting the webapp's file,
that would account for the mysterious disappearance of published files.
Let us know if you happen to find one.
Cheers,
Larry
|
|
|
Powered by
FUDForum. Page generated in 0.04041 seconds
Home