Hi Vincent,
Thanks for finding this issue. There have been a lot of changes
from Tomcat 3.2 to 3.3 with respect to classloaders and configuration,
most of them improvements. Documenting these changes is still on
the todo list.
At the current level of implementation, starting two instances of
ok, as no one is interested by the subject, I'll reply to my own question
:)
By looking at the source code, I have found a workaround to stop Tomcat 3.3
on a custom AJP12 port and with a ContextManager home different from
tomcat.home :
Instead of using java -classpath tomcat.jar
