Apache configured to run SSL creates two differente tomcat applications??

[Csongor Gyuricza <cs...@mandic.com.br>]

We are running Tomcat 4.1.12 under Apache 1.3.27. When we enable SSL on
Apache, it seems that Tomcat instances a new application, so we have one
application for the secure connection and another for the non-secure
connection. Is this correct?? Should it be this way?

We are using Java Exchange's DBConnectionBroker to manage our connections
(http://www.javaexchange.com/) and since we started using SSL, there are
always two instances of the connections pool (one for each application), and
this is causing some problems.

Any hint?

Csongor Gyuricza


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org