Thanks for the information Jeff. Right now I'd just like to get it
working with the current log name tomcat. Sometime after that I'll try
to look into supporting various naming formats, multiple log files, etc...
I think something really strange is going on with my system (or perhaps
the G image itself) regarding the management interface. I build G
with tomcat as the default by running maven -o tomcat from
G\modules\assembly.
This seems to work because when I start the server I see that tomcat is
using port 8080.
8009 0.0.0.0 Tomcat Connector AJP
8080 0.0.0.0 Tomcat Connector HTTP
8090 0.0.0.0 Jetty Connector HTTP
However, then I try to interact with the management implementation the
JettyLogManagerImpl is what is being invoked rather than the
TomcatLogManagerImpl.
Am I doing something wrong when trying to configure for tomcat as the
default? I'll keep looking ....
Joe
Jeff Genender wrote:
Yes...the 0.0.0.0 is from line 208 of the j2ee-tomcat-plan.xml, which
uses the PlanServerHostname from maven.xml (which happens to be 0.0.0.0):
prefix=${PlanServerHostname}_access_log.
We can change this via configuration. However, keep in mind this can
change since its configurable. Especially when using virtual hosts,
people like to have multiple log files...so they may have one that says
0.0.0.0_access_log, and one that says foo_access_log, etc.
IMHO, I don't like the "0.0.0.0" in the access_log name. I prefer
"localhost".
Thanks for looking into this, Joe.
Jeff
Joe Bohn (JIRA) wrote:
[
http://issues.apache.org/jira/browse/GERONIMO-1029?page=comments#action_12330793
]
Joe Bohn commented on GERONIMO-1029:
------------------------------------
I created the jira because there are never any records displayed in
the web access log viewer when G is configured using tomcat.
I created it against both tomcat and management because I was not sure
where the problem existed. I thought tomcat might have a problem
because I expected the 0.0.0.0 to be the date in the file name.
However, based upon Jeff'scomments the problem may be in the
management implementation. I'll take a look.
Btw, I did not yet create the jira for multiple log file processing.
tomcat web log seems to be created with wrong name and isn't found by
the web log viewer portlet
------------------------------------------------------------------------------------------------
Key: GERONIMO-1029
URL: http://issues.apache.org/jira/browse/GERONIMO-1029
Project: Geronimo
Type: Bug
Components: management, Tomcat
Versions: 1.0-M5
Environment: all
Reporter: Joe Bohn
Assignee: Jeff Genender
It seems that the log file for the tomcat web container is being
created with an invalid date in the name. ex.
...geronimo\modules\assembly\target\geronimo-1.0-SNAPSHOT\var\catalina\logs\0.0.0.0_access_log.2005-09-28.txt
Possibly related (or possibly not) is that the management API cannot
find matches when performing a search.
--
Joe Bohn
[EMAIL PROTECTED]
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
