I believe it's a bug. You can get around it by defining the port in
conf/jk2.properties ...
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/configtcex.html
On Wednesday, November 20, 2002, at 08:26 PM, Filip Hanik wrote:
Did anyone notice that Tomcat 4.1.12 does not respect the port
a
On Wednesday, November 20, 2002, at 05:01 PM, Nick Wesselman wrote:
Using 4.0.6 I'm getting a lot of exceptions (for every jar in
/WEB-INF/lib/) on startup like this one:
ContextConfig[]: tldConfigJar(/WEB-INF/lib/xerces.jar):
java.io.IOException: No such file or directory
Whi
Using 4.0.6 I'm getting a lot of exceptions (for every jar in
/WEB-INF/lib/) on startup like this one:
ContextConfig[]: tldConfigJar(/WEB-INF/lib/xerces.jar):
java.io.IOException: No such file or directory
Which is problematic because if an exception happens in tldConfigJar(),
ContextConfi
tor binary might be a bit old. The name of the precompiled binary
we're using is "mod_jk-3.3-ap13-eapi.so".
Any ideas? Should we be using the mod_jk-01.so binary from the 4.0.3 build?
Thanks,
Nick Wesselman
Digital Visions, Inc.
--
To unsubscribe, e-mail: <mailto:[EMAI
[nick@odyssey conf]$ /usr/java/j2sdk1.4.0/bin/javap
java.util.logging.Logger | grep setUseParentHandlers
[nick@odyssey conf]$
Something added in 1.4.0_01 maybe?
Nick
On Friday, June 7, 2002, at 02:49 PM, [EMAIL PROTECTED] wrote:
>
>> OK, How about this? From the catalina.out when I try using
That helps me? Some pointers on what to try next maybe
Could using a conf file from 4.0.x (modified to use Coyote http/1.1
connector) be the culprit? Should I not be using
org.apache.catalina.logger.FileLogger anymore?
Nick
On Friday, June 7, 2002, at 02:23 PM, Remy Maucherat wrote:
>> O
OK, How about this? From the catalina.out when I try using jdk 1.4...
org.apache.commons.logging.LogConfigurationException:
java.lang.reflect.InvocationTargetException
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance
(LogFactoryImpl.java:494)
at
org.apache.common
OK, I gave the IBM jdk a shot, and it crashes on me as well. Interesting
that it also happens related to opening a zip:
"main" (TID:0x100519D8, sys_thread_t:0x8059108, state:R, native
ID:0x400) prio=5
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(
True enough, VM bug, but we use this JVM w/ 4.0.1 and 4.0.3 in
production no problem. I won't argue with you about it though--I'm not a
TC developer :-)
Thanks for the quick reply.
Nick
On Friday, June 7, 2002, at 10:28 AM, Remy Maucherat wrote:
>> Greetings,
>>
>> I was trying out 4.1.3b1 a
/development/NWESSELMAN/webhome/webapps/ROOT/WEB-
INF/lib/jce1_2-do.jar
I hope there's a fix, I really want to check out the admin app :-)
Nick Wesselman
Digital Visions, Inc.
---
Starting service Tomcat-Apache
Apache Tomcat/4.1.3
An unexpected exception has been detected in native
i Nick,
>
>I don't have anything in my web.xml, so I don't hope this is going to be the
>default at some time (or should at least be configurable as it always was
>with all the connectors).
>
>Mvgr,
>Martin
>
>
>-Original Message-
>From: Nick W
hello all,
I don't know if this is really needed or appreciated, but for my own
satisfaction I made some modifications to mod_webapp to make Tomcat only
handle URIs mapped in web.xml, as the connector is intended to do. This
way, Apache itself can serve all your static content. The hooks were
12 matches
Mail list logo
