Windows service and multiple instances

2004-12-01 Thread Wouter De Vaal 
Hi,

I've read enough about having multiple tomcat instances. 
However when using windows, the installer won't create a second
windows service for starting and stopping the second tomcat
installation.

Has anyone have a solution/suggestion for this?

Regards,
Wouter de Vaal

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat 5.5.4 and Log4j

2004-11-24 Thread Wouter De Vaal 
Hi,

I'm having difficulties to configure log4j with tomcat logging per context.
Here's what I have done:
1. I've added log4j.jar to the bin dir
2. I've created a log4j.xml in common/classes and added the log4j.dtd
This seems to work, because when I add a debug logger for org.apache,
I get a lot of extra logging lines in stdout.log.
But now I have a new webapp called advertisements and this is de
message that I get in de stdout.log:
log4j:WARN No appenders could be found for logger
(org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/advertisements]).
log4j:WARN Please initialize the log4j system properly.

But when I add the logger with this name I get the following error:
log4j:ERROR Parsing error on line 10 and column 100
log4j:ERROR Attribute value
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/advertisements]
of type ID must be a name.

So I guess log4j can't handle these names?

I've also tried to use a log4j.properties (which also works when I add
a debug logger for org.apache), but that doesn't work either, but this
time I only get the first warning.

My log4j.xml:
?xml version=1.0 encoding=UTF-8 ?
!DOCTYPE log4j:configuration SYSTEM log4j.dtd
log4j:configuration
   !-- STDOUT: Outputs log information to the standard output/console --
   appender name=STDOUT class=org.apache.log4j.ConsoleAppender
   layout class=org.apache.log4j.PatternLayout
   param name=ConversionPattern value=%d %-5p - %m%n/
   /layout
   /appender
   logger 
name=org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/advertisements]
   level value=DEBUG/
   appender-ref ref=STDOUT/
   /logger
   logger name=org.apache
   level value=INFO/
   appender-ref ref=STDOUT/
   /logger
   root
   level value=ERROR/
   /root
/log4j:configuration

alternative log4j.properties:
log4j.rootLogger=ERROR, A1
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout

# Print the date in ISO 8601 format
log4j.appender.A1.layout.ConversionPattern=%d [%t] %-5p %c - %m%n

#log4j.logger.org.apache=DEBUG,A1
log4j.logger.org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/advertisements]=INFO,A1

Regards,
Wouter de Vaal

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat Documentation Thoughts

2004-11-24 Thread Wouter De Vaal 
On Wed, 24 Nov 2004 09:44:00 -0500, Shapira, Yoav [EMAIL PROTECTED] wrote:
 
 Hi,
 
 But you know, I submitted a logging page doc patch over a week ago and
 it's
 still not there, and since then there have been many posts asking about
 this problem. I don't find that encouraging.
 
Is this about my problem that I posted earlier today (tomcat 5.5.4 and
log4j)? About the
...[host].[/] problem?
If so, could you please post your fix on this to me or this list?

Regards,
Wouter de Vaal

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

context/domain mapping issues

2004-04-16 Thread Wouter de Vaal 
Hi,

I was wondering if the following scenario is possible and how it should 
be accomplished, or maybe how I should handle it differently.

I'm using tomcat 5.0.19 and I'm also using apache webserver 2.0.49

I've got in my webapps directory two applications A and B and I have two 
domains registered a.mycom.com and b.mycom.com.
What I would like to happen is that request are routed by apache webserver accordingly,
like this:

http://a.mycom.com - http://localhost:8080/a

http://b.mycom.com - http://localhost:8080/b

I have tried the proxy settings describe in the manual pages, but that
way I can only get it working by using
http://a.mycom.com/a - http://localhost:8080/a


But then again, I guess there would be problems with generated links to the server 
(which include the context path).
Any thoughts on this, best practices?

Regards,
Wouter de Vaal