geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bohn (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1029) tomcat web log seems to be created with wrong name and isn't found by the web log viewer portlet
Date Mon, 03 Oct 2005 18:03:53 GMT
    [ ] 

Joe Bohn commented on GERONIMO-1029:

It turns out this isn't a problem with tomcat, the web log viewer portlet, or even really
the management interface.  However, it is a bit related to running multiple containers concurrently.

The problem is that when we query the kernel get the WebManagerNames from within the portlet(s)
we get back an array of 2 (tomcat and jetty).  In several places in the console we assume
that the container that we need to reference to provide appropriate management information
(ie. the container in which the console is currently running) will always be the first entry
in the array.  Bad assumption.  In my case the console is running in the tomcat container
but we're attempting to manage the jetty container.

So now we just have to come up with a way to detect which WebManager is the one for the "default"
container (assuming that we continue to support multiple concurrent containers.... in which
case not only console web log viewers but other components also have problems that must be

> tomcat web log seems to be created with wrong name and isn't found by the web log viewer
> ------------------------------------------------------------------------------------------------
>          Key: GERONIMO-1029
>          URL:
>      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\
> Possibly related (or possibly not) is that the management API cannot find matches when
performing a search.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message