yes , my JDBC connectively does work well using Servlets/jsp.
I am running tomcat4 on debain linux. I also include the snippet of server.xml :
<!-- Define the Tomcat Stand-Alone Service --> <Service name="Tomcat-Standalone">
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Each Connector passes requests on to the
associated "Container" (normally an Engine) for processing.
-->
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8180 -->
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8180" minProcessors="5" maxProcessors="75"
enableLookups="true" acceptCount="10" debug="0"
connectionTimeout="20000" useURIValidationHack="false" />
<!-- Define an SSL HTTP/1.1 Connector on port 8443 -->
<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8443" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="10" debug="0" scheme="https" secure="true">
<Factory className="org.apache.catalina.net.SSLServerSocketFactory"
clientAuth="false" protocol="TLS"
keystoreFile="/usr/share/tomcat4/"
keystorePass="vision2003"/>
</Connector>
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8009" minProcessors="5" maxProcessors="75"
enableLookups="true" acceptCount="10" debug="0"
connectionTimeout="20000" useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
<!-- An Engine represents the entry point (within Catalina) that processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and passes them
on to the appropriate Host (virtual host). -->
<!-- Define the top level container in our container hierarchy -->
<Engine name="Standalone" defaultHost="localhost" debug="0"> <!-- Global logger unless overridden at lower levels -->
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_" suffix=".log" timestamp="true"/><!-- Because this Realm is here, an instance will be shared globally -->
<!-- <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/> -->
<Realm classname="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="com.informix.jdbc.IfxDriver"
connectionURL="jdbc:informix-sqli://"
userName="mubaraka"
userPassword="login"
userTable="users"
userNameCol="username"
userCredCol="password"
userRoleTable="roles"
roleNameCol="rolename"/>
<!-- Define the default virtual host --> <Host name="localhost" debug="0" appBase="webapps" unpackWARs="false" autoDeploy="true">
<!-- Logger shared by all Contexts related to this virtual host. -->
<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="localhost_" suffix=".log"
timestamp="true"/>
<Context path="/atrox" docBase="atrox" debug="0" reloadable="true">
</Context>
<Context path="/onjava" docBase="onjava" debug="0" reloadable="true">
</Context>
<Context path="/loginexample2" docBase="loginexample2" debug="0" reloadable="true">
</Context> </Host>
</Engine>
</Service>
pls suggest whether my placing of the Realm needs change to resolve the problem.
Thanks for all yr help
Mubaraka
On 2003.02.24 15:08 "Tam, Michael" wrote:
Hi Mubaraka,
Can you verify if your JDBC library does work? For example, use a simple jsp/servlet to call JDBC to connect to your db?? Once JDBC is working then we can narrow down where the problem is.
Michael
-----Original Message----- From: Mubaraka Arif [mailto:[EMAIL PROTECTED] Sent: Monday, February 24, 2003 11:51 AM To: Tomcat Users List Subject: Re: tomcat4 dies when JBDC Realm is configured
hi michael,
I had provided the ConnectionURL, connectionName and connectionPassword , its jsut for security reasons I did not have it along with other details. I tried it placing under host, context and Engine services but still it dies.
All help would be appreciated
Mubaraka
On 2003.02.24 12:34 "Tam, Michael" wrote:
> In your xml, if it is what you're using in your setup, then you
didn't
> provide any value to connectionURL, connectionName, and
> connectionPassword
> to establish connection to the database. If you need help on this,
> you
> should read the document that comes with tomcat where you will find
a
> section related to setting up JDBC REALM and the document of the
JDBC
> driver
> that you use.
>
> Hope this help.
>
> Michael
>
> -----Original Message-----
> From: Mubaraka Arif [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 24, 2003 9:16 AM
> To: Tomcat Users List
> Subject: tomcat4 dies when JBDC Realm is configured
>
>
> hello ,
>
> I have been trying to establish conainer amanaged security , so I
> tried
> to configure it using JDBC Realm.
> Steps what I follwed where :
>
> 1. created users table with fields username, password.
>
> 2. created roles tables with fields username, rolename.
>
> 3. In server.xml I added the JDBC Realm as follows :
> Snippet of server.xml
> > <!-- Define the default virtual host -->
> <Host name="localhost" debug="0" appBase="webapps"
> unpackWARs="false" autoDeploy="true">
>
> <!-- Logger shared by all Contexts related to this virtual
> host. -->
> <Logger className="org.apache.catalina.logger.FileLogger"
> directory="logs" prefix="localhost_" suffix=".log"
> timestamp="true"/>
>
> <Realm classname="org.apache.catalina.realm.JDBCRealm"
> debug="99"
> driverName="com.informix.jdbc.IfxDriver"
> connectionURL=" "
> connectionName=""
> connectionPassword=""
> userTable="users"
> userNameCol="username"
> userCredCol="password"
> userRoleTable="roles"
> roleNameCol="rolename:/>
>
> <Context path="/onjava" docBase="onjava" debug="0"
> reloadable="true">
> </Context>
>
>
>
> </Host>
>
> </Engine>
>
> </Service>
>
>
> When I start tomcat4 , it starts and dies in about 60sec.
>
> If any of you have encountered such situations , please provide
some
> light to this problem which would be greatly appreciated.
>
> Mubaraka Arif
> Data Management Software Developer
> St Mary's University, San Antonio, TX
> e-mail : [EMAIL PROTECTED]
> phone: 210-436-3647
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
