I had the same problem with JBoss. If you're on JBoss 3 then you might want
to try changing this (in log4j.xml):
<!-- ============================== -->
<!-- Append messages to the console -->
<!-- ============================== -->
<appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
<param name="Threshold" value="INFO"/>
<param name="Target" value="System.out"/>
to this:
<!-- ============================== -->
<!-- Append messages to the console -->
<!-- ============================== -->
<appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
<param name="Threshold" value="TRACE"/>
<param name="Target" value="System.out"/>
Hope that helps, I had the same problem as you.
Matt.
-----Original Message-----
From: Erik Hatcher [mailto:jakarta-struts@;ehatchersolutions.com]
Sent: Monday, October 28, 2002 19:43
To: Struts Developers List
Subject: Re: Nightly build issue
Eddie Bush wrote:
> Can you verify your assumption with the logging output? It should say
> what the value of matchPath is. This would be a debug-level logging
> statment indicated by a line stating:
>
> Selecting module for path <matchPath>
>
> You may have to turn up the volume on your logging output to see it. I'd
> be most interested in what's going on here.
Unfortunately for some reason the interaction with JBoss and Log4j
doesn't like debug output and the lowest level I can get visible is
'INFO' level messages. *ugh* - why is logging so darn brittle and
troublesome?! :/ (and yes, I've fought with this in the past, but it
wasn't worth devoting much time to given other higher priority concerns)
> If there is a case where the first character of matchPath may not be a
> "/" then that condition needs to change to a > instead of !=. I was of
> the impression that the first element of that string would always be a
"/".
Perhaps its something related to how Cactus is invoking through
ActionServlet that the path does not begin with "/"?
Also, I'm not using modules, if that has any bearing on this.
I've noticed other fishy things with our application and the 20021028
build that I haven't had time to dig into yet.
Erik
--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
