In the meanwhile, I found a way to work around the problem. Just for the record:
Tomcat uses plain JDK logging, so one can obtain a logger with
Logger#getLogger() and change its settings before Tomcat obtains a
reference. As loggers are held in WeakReferences, you only need to
make sure that they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To whom it may concern,
On 6/24/2011 12:18 PM, jjgtx wrote:
> Christopher Schultz-2 wrote:
>> Where did you put your log4j.properties file and what does it contain?
>> Can you just post the whole thing?
>
> [I put log4j.properties in] $CATALINA_HOME/l
On 6/24/2011 5:48 AM, Rainer Jung wrote:
On 24.06.2011 14:08, Tim Funk wrote:Looks like this is the root cause from
DefaultServlet ...
While the ISE is caught ... since the mimetype for js was changed - it
doesn't match the fallback method
try {
ostream = r
Where did you put your log4j.properties file and what does it contain?
Can you just post the whole thing?
$CATALINA_HOME/lib
I hate to post the whole thing, its a bit long would it be better to send
it?
One thing I was curious about is that should be the value of the
$LOGGING_CONFIG propert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To whom it may concern,
On 6/23/2011 5:44 PM, jjgtx wrote:
> Followed the
> instructions at http://tomcat.apache.org/tomcat-6.0-doc/logging.html
> replacing the tomcat-juli.jar file in $CATALINA_HOME/bin with the one from
> extras and placing the log4
I double checked. The version of Tomcat and the versions of Java are all the
same.
Ronald.
Op vrijdag, 24 juni 2011 03:25 schreef Filip Hanik - Dev Lists
:
are there other versions of Apache Tomcat running in the same cluster?
Check the logs for what members are joining the cluster, t
Hi all,
I'm currently using Tomcat's embedded feature for unit testing of a web
service. This web service displays different behaviour depending on the
contents of the web.xml file. I therefore want to exercise different web.xml
configurations in my unit tests. Currently the setup code I'm using i
On 24.06.2011 14:08, Tim Funk wrote:
> Looks like this is the root cause from DefaultServlet ...
>
> While the ISE is caught ... since the mimetype for js was changed - it
> doesn't match the fallback method
>
> try {
> ostream = response.getOutputStream();
>
Looks like this is the root cause from DefaultServlet ...
While the ISE is caught ... since the mimetype for js was changed - it
doesn't match the fallback method
try {
ostream = response.getOutputStream();
} catch (IllegalStateException e) {
2011/6/24 David Wall :
>
>>
>>> out.write("\n");
>>> pageContext.include("/static/esf/esf.js",true);
>>> out.write("\n");
>>>
>>> But the exception IllegalStateException is thrown on the include of the
>>> esf.js file. The reason is null, so there's no more details. I find it odd
>>> in that the
10 matches
Mail list logo
