File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

SQL Exception No suitable driver

Mandar Velankar
Ranch Hand
Posts: 32
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
can anybody help me for problem i am tackling,

I am using Tomcat 5.0.30 , oracle9i Release and j2sdk 1.4.2_04 for

my work.When I am trying to login to my system ,I got following exception,

Caught SQLException No suitable driver

I tried using ojdbc14.jar by adding to WEB-INF/lib folder, even

in WEB-INF/lib folder, but it cann't work. I am using oracle thin driver


What can I do?please help me and thanks a lot.

waiting for yor reply.



Paul Sturrock
Posts: 10336
Eclipse IDE Hibernate Java
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
UNless you are using an old version of the JDK you need the ojdbc14.jar in your classpath, not
Mandar Velankar
Ranch Hand
Posts: 32
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Paul ,
Thanks. I tried that one, I am using Windows Server 2003, i set classpath by adding environment varible 'classpath' using control panel - system properties.but it doesn't work.can we required to check for dll file for such driver. I doesn't have any idea but heard somewhere. can anybody help?
Thanks a lot.
Mandar Velankar
Paul Sturrock
Posts: 10336
Eclipse IDE Hibernate Java
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I tried that one, I am using Windows Server 2003, i set classpath by adding environment varible 'classpath' using control panel - system properties.but it doesn't work

No need to change the system classpath. Just put it in Tomcat's classpath (see the Tomcat documentation).

can we required to check for dll file for such driver

Not sure what you mean here, but if you are using the thin driver you don't need anything else installed on your machine. So no dll to look for.

Can you show us your server.xml?
Mandar Velankar
Ranch Hand
Posts: 32
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Paul,
Thanks a lot for your explnation.I removed classpath varible set earlier.I kept ojdbc14.jar in WEB-INF/lib of my web application.But still it is not working.I will list my login process page and server.xml page.


<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
parent-child relationships with each other -->

<!-- A "Server" is a singleton element that represents the entire JVM,
which may contain one or more "Service" instances. The Server
listens for a shutdown command on the indicated port.

Note: A "Server" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.

<Server port="8005" shutdown="SHUTDOWN" debug="0">

<!-- Comment these entries out to disable JMX MBeans support -->
<!-- You may also configure custom components (e.g. Valves/Realms) by
including your own mbean-descriptor file(s), and setting the
"descriptors" attribute to point to a ';' seperated list of paths
(in the ClassLoader sense) of files to add to the default list.
e.g. descriptors="/com/myfirm/mypackage/mbean-descriptor.xml"
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"

<!-- Global JNDI resources -->

<!-- Test entry for demonstration purposes -->
<Environment name="simpleValue" type="java.lang.Integer" value="30"/>

<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users -->
<Resource name="UserDatabase" auth="Container"
description="User database that can be updated and saved">
<ResourceParams name="UserDatabase">


<!-- A "Service" is a collection of one or more "Connectors" that share
a single "Container" (and therefore the web applications visible
within that Container). Normally, that Container is an "Engine",
but this is not required.

Note: A "Service" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.

<!-- Define the Tomcat Stand-Alone Service -->
<Service name="Catalina">

<!-- 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.

By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
You can also enable an SSL HTTP/1.1 Connector on port 8443 by
following the instructions below and uncommenting the second Connector
entry. SSL support requires the following steps (see the SSL Config
HOWTO in the Tomcat 5 documentation bundle for more detailed
* If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or
later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".
* Execute:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
with a password value of "changeit" for both the certificate and
the keystore itself.

By default, DNS lookups are enabled when a web application calls
request.getRemoteHost(). This can have an adverse impact on
performance, so you can disable it by setting the
"enableLookups" attribute to "false". When DNS lookups are disabled,
request.getRemoteHost() will return the String version of the
IP address of the remote client.

<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port specified
during installation -->
<Connector port="2020"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
debug="0" connectionTimeout="20000"
disableUploadTimeout="true" />
<!-- Note : To disable connection timeouts, set connectionTimeout value
to 0 -->

<!-- Note : To use gzip compression you could set the following properties :

noCompressionUserAgents="gozilla, traviata"

<!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
<Connector port="8443"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" debug="0" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" />

<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
<Connector port="8009"
enableLookups="false" redirectPort="8443" debug="0"
protocol="AJP/1.3" />

<!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
<!-- See proxy documentation for more information about using this. -->
<Connector port="8082"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
acceptCount="100" debug="0" connectionTimeout="20000"
proxyPort="80" disableUploadTimeout="true" />

<!-- 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). -->

<!-- You should set jvmRoute to support load-balancing via JK/JK2 ie :
<Engine name="Standalone" defaultHost="localhost" debug="0" jvmRoute="jvm1">

<!-- Define the top level container in our container hierarchy -->
<Engine name="Catalina" defaultHost="localhost" debug="0">

<!-- The request dumper valve dumps useful debugging information about
the request headers and cookies that were received, and the response
headers and cookies that were sent, for all requests received by
this instance of Tomcat. If you care only about requests to a
particular virtual host, or a particular application, nest this
element inside the corresponding <Host> or <Context> entry instead.

For a similar mechanism that is portable to all Servlet 2.4
containers, check out the "RequestDumperFilter" Filter in the
example application (the source for this filter may be found in

Request dumping is disabled by default. Uncomment the following
element to enable it. -->
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>

<!-- Global logger unless overridden at lower levels -->
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_log." suffix=".txt"

<!-- Because this Realm is here, an instance will be shared globally -->

<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/>

<!-- Comment out the old realm but leave here for now in case we
need to go back quickly -->
<Realm className="org.apache.catalina.realm.MemoryRealm" />

<!-- Replace the above Realm with one of the following to get a Realm
stored in a database and accessed via JDBC -->

<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
connectionName="test" connectionPassword="test"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />

<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
connectionName="scott" connectionPassword="tiger"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />

<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />

<!-- Define the default virtual host
Note: XML Schema validation will not work with Xerces 2.2.

<Host name="localhost" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">

<!-- Defines a cluster for this node,
By defining this element, means that every manager will be changed.
So when running a cluster, only make sure that you have webapps in there
that need to be clustered and remove the other ones.
A cluster has the following parameters:

className = the fully qualified name of the cluster class

name = a descriptive name for your cluster, can be anything

debug = the debug level, higher means more output

mcastAddr = the multicast address, has to be the same for all the nodes

mcastPort = the multicast port, has to be the same for all the nodes

mcastBindAddr = bind the multicast socket to a specific address

mcastTTL = the multicast TTL if you want to limit your broadcast

mcastSoTimeout = the multicast readtimeout

mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat

mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received

tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes

tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,
in case of multiple ethernet cards.
auto means that address becomes

tcpListenPort = the tcp listen port

tcpSelectorTimeout = the timeout (ms) for the method in case the OS
has a wakup bug in java.nio. Set to 0 for no timeout

printToScreen = true means that managers will also print to std.out

expireSessionsOnShutdown = true means that

useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.
false means to replicate the session after each request.
false means that replication would work for the following piece of code:
HashMap map = (HashMap)session.getAttribute("map");
replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
* Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.
* Synchronous means that the thread that executes the request, is also the
thread the replicates the data to the other nodes, and will not return until all
nodes have received the information.
* Asynchronous means that there is a specific 'sender' thread for each cluster node,
so the request thread will queue the replication request into a "smart" queue,
and then return to the client.
The "smart" queue is a queue where when a session is added to the queue, and the same session
already exists in the queue from a previous request, that session will be replaced
in the queue instead of replicating two requests. This almost never happens, unless there is a
large network delay.
When configuring for clustering, you also add in a valve to catch all the requests
coming in, at the end of the request, the session may or may not be replicated.
A session is replicated if and only if all the conditions are met:
1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
2. a session exists (has been created)
3. the request is not trapped by the "filter" attribute

The filter attribute is to filter out requests that could not modify the session,
hence we don't replicate the session after the end of this request.
The filter is negative, ie, anything you put in the filter, you mean to filter out,
ie, no replication will be done on requests that match one of the filters.
The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.

filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
ending with .gif and .js are intercepted.

The deployer element can be used to deploy apps cluster wide.
Currently the deployment only deploys/undeploys to working members in the cluster
so no WARs are copied upons startup of a broken node.
The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"
When a new war file is added the war gets deployed to the local instance,
and then deployed to the other instances in the cluster.
When a war file is deleted from the watchDir the war is undeployed locally
and cluster wide

<Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"




<Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"

<Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"

<!-- Normally, users must authenticate themselves to each web app
individually. Uncomment the following entry if you would like
a user to be authenticated the first time they encounter a
resource protected by a security constraint, and then have that
user identity maintained across *all* web applications contained
in this virtual host. -->
<Valve className="org.apache.catalina.authenticator.SingleSignOn"

<!-- Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory relative to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a relative
(to $CATALINA_HOME) or absolute path to the desired directory.
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="common" resolveHosts="false"/>

<!-- Logger shared by all Contexts related to this virtual host. By
default (when using FileLogger), log files are created in the "logs"
directory relative to $CATALINA_HOME. If you wish, you can specify
a different directory with the "directory" attribute. Specify either a
relative (to $CATALINA_HOME) or absolute path to the desired
<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="localhost_log." suffix=".txt"






<%Connection con=null;
String url="jdbcracle:thin:@localhost:1521:gj1";
String username="master";
String password="master";
verify1.jsp (page where authentication done)

<%@ page language="java" import="java.sql.Connection,java.sql.DriverManager,java.sql.Statement,java.sql.ResultSet,*,java.sql.SQLException"%>
<%@ include file="masterdatabase.jsp"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<TITLE> New Document </TITLE>
<META HTTP-EQUIV="Pragma" CONTENT="no-cache"/><META HTTP-EQUIV="Expires" CONTENT="-1"/>
<META NAME="Generator" CONTENT="EditPlus">
<META NAME="Keywords" CONTENT="">
<META NAME="Description" CONTENT="">
String usercode=request.getParameter("usercode");
String upassword=request.getParameter("password");
String logyear = "";
String location=null;
String emp_sql = "";
//String url="jdbcracle:thin:@localhost:1521:gj1";
//String username="master";
//String password = "master";
Statement stat1;
//String emp_sql="select vc_user_name, name,vc_user_code,OFFICESHORTNM,count(*) as no from v_users where vc_user_name like '"+usercode+"' and vc_user_password like '"+upassword+"' group by vc_user_name,name,vc_user_code,OFFICESHORTNM" ;
emp_sql="select vc_user_name, name,vc_user_code,loc,count(*) as no from v_users where vc_user_name like '"+usercode+"' and vc_user_password like '"+upassword+"' and vc_status ='A' group by vc_user_name,name,vc_user_code,loc" ;

ResultSet rs1=stat1.executeQuery(emp_sql);
int no=0;
String user=null;
String name=null;
String user_code=null;
//String vc_status=null;
String error=null;
while (
out.println("no " + no);
//String no=rs1.getString("vc_emp_name");
out.println(" Login Status" + no);
if (no!=1)
error="Not a valid user";
out.println("Not a valid user");
response.sendRedirect("verify.jsp?error="+error) ;
//out.println("old session = " +session.getAttribute("user"));

//if (session.getAttribute("user")!=null)

//out.println("first if condition");

//out.println("first if condition");

//error="You have already logged in the system";
//out.println("Invalid Username and Password");
//response.sendRedirect("verify.jsp?error="+error) ;

java.util.Date now= new java.util.Date();
int mnth = now.getMonth()+1;
int nextyr = 1900+now.getYear()+1;
int curryr = 1900+now.getYear();
int lastyr = 1900+now.getYear()-1;

String cyr = ""+curryr;
String nyr = "";
String lyr = ""+lastyr;

String fyr = "";

if(mnth >= 4 && mnth <= 12){
fyr = cyr.substring(2,4);
nyr = ""+nextyr;
fyr = lyr.substring(2,4);
nyr = ""+curryr;

logyear = fyr+nyr.substring(2,4);

session.setAttribute("name",name );
//response.sendRedirect("dmenu/iframetest.jsp?error="+error) ;

<script language="javascript">
//newWindow ="iframetest.jsp",'gjerp','width=790,height=480,scrollbars=yes,menubar=yes,status=yes,resizable=yes,directories=false,location=false,left=0,top=0');
//if (window.focus) {newWindow.focus()}

response.sendRedirect("iframetest.jsp") ;

//t.println("welcome " + usercode);
catch(ClassNotFoundException cnfe)
out.println("Caught ClassNotFoundException " + cnfe.getMessage());
catch(IOException ioe)
out.println("Caught IOException " + ioe.getMessage());

catch(SQLException sqle){
out.println("Caught SQLException " + sqle.getMessage());
if( con!=null)
catch(SQLException sqle)
out.println("Caught SQLException from final catch " +sqle.getMessage());

catch(Exception e)
out.println("Caught exception from final catch " + e.getMessage());




Thanks for your help , this might give you all idea about my application.

Thanks again.Waiting for your reply.

Paul Sturrock
Posts: 10336
Eclipse IDE Hibernate Java
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I kept ojdbc14.jar in WEB-INF/lib of my web application.But still it is not working

Normally in web applications you would not put your driver in your application's classpath, you would put it in Tomcat's classpath. However this is becasue normally you would probably use a DataSource rather than getting a connection manually.

A couple of pointers: you have JSP code and Java code mixed. Not a good idea. Its messy and difficult to maintain and it ties the application view and logic tightly together. You also probably should consider using a DataSource; this way you only need to have JDBC configuration details at one point in you application, rather than littered throughout.

Finally, your problem! The exception you are getting occurs because the DriverManager cannot find a suitable Driver for the URL you supplied at:

This happens for two reasons: either you have not registered the driver, or your URL syntax is wrong. The class oracle.jdbc.driver.OracleDriver is the correct class to register, and you know it is on the classpath because:

would throw a ClassNotFoundException if it could not find your driver. However, this method will not register the Driver, since it loaded the Driver but does not initialize it. Use Class.forName() instead.

There is also the problem of your URL. Looking though your code, I don't see where you assign a value to this. Is it ever anything other than null?
[ April 03, 2007: Message edited by: Paul Sturrock ]
Mandar Velankar
Ranch Hand
Posts: 32
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Paul,
Thanks a lot. Now everything is working.I followed all your instructions and learn a lot from such example. Now I learned how to use oracle thin dirver.
Thanks again for such great help.
Mandar Velankar
I agree. Here's the link:
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic