Oracle Connection Pool gives java.sql.SQLException: No suitable driver at WLS Startup..
Manoj
Hello All,
When I start Weblogic 7.0.SP2 with an Oracle Connection Pool, it gives the following
exception:
Any idea on what could be wrong?
Thanks in advance for the help.
rgds
MS
---- Weblogic Startup Console ----
H:\eFw\efwdomain>startWebLogic.cmd
H:\eFw\efwdomain>echo off
H:\eFw\efwdomain>set CLASSPATH=H:\eFw\jars\xerces.jar;H:\eFw\jars\framework.jar;
H:\eFw\jars\common.jar;H:\eFw\jars\configloader.jar;H:\eFw\jars\jlex.jar;H:\eFw\
jars\cup.jar;H:\eFw\jars\ruleengine.jar;H:\eFw\jars\server.jar;H:\plexus\FloWare
\Server\class\OB.jar;H:\plexus\FloWare\Server\class\fwpjava7.jar;H:\plexus\FloWa
re\Server\class\flowaresrv.jar;H:\oracle\ora9i\jdbc\lib\classes12.zip;\C:\oracle
\ora9i\jdk\jre\lib\jta.zip;H:\tibco\tibrv\LIB\tibrvj.jar;C:\Program Files\Proces
sAnalyzer\eFwJars\cup.jar;C:\Program Files\ProcessAnalyzer\eFwJars\jlex.jar;C:\P
rogram Files\ProcessAnalyzer\eFwJars\ruleengine.jar;C:\Program Files\ProcessAnal
yzer\eFwJars\framework.jar;C:\Program Files\ProcessAnalyzer\eFwJars\server.jar;C
:\Program Files\ProcessAnalyzer\eFwJars\common.jar;C:\Program Files\ProcessAnaly
zer\eFwJars\client.jar
H:\eFw\efwdomain>echo off
CLASSPATH=H:\bea\jdk131_06\lib\tools.jar;H:\bea\weblogic700\server\lib\weblogic_
sp.jar;H:\bea\weblogic700\server\lib\weblogic.jar;H:\eFw\jars\xerces.jar;H:\eFw\
jars\framework.jar;H:\eFw\jars\common.jar;H:\eFw\jars\configloader.jar;H:\eFw\ja
rs\jlex.jar;H:\eFw\jars\cup.jar;H:\eFw\jars\ruleengine.jar;H:\eFw\jars\server.ja
r;H:\plexus\FloWare\Server\class\OB.jar;H:\plexus\FloWare\Server\class\fwpjava7.
jar;H:\plexus\FloWare\Server\class\flowaresrv.jar;H:\oracle\ora9i\jdbc\lib\class
es12.zip;\C:\oracle\ora9i\jdk\jre\lib\jta.zip;H:\tibco\tibrv\LIB\tibrvj.jar;C:\P
rogram Files\ProcessAnalyzer\eFwJars\cup.jar;C:\Program Files\ProcessAnalyzer\eF
wJars\jlex.jar;C:\Program Files\ProcessAnalyzer\eFwJars\ruleengine.jar;C:\Progra
m Files\ProcessAnalyzer\eFwJars\framework.jar;C:\Program Files\ProcessAnalyzer\e
FwJars\server.jar;C:\Program Files\ProcessAnalyzer\eFwJars\common.jar;C:\Program
Files\ProcessAnalyzer\eFwJars\client.jar
PATH=.;H:\bea\weblogic700\server\bin;H:\bea\jdk131_06\bin;H:\plexus\FloWare\Serv
er\slib;H:\plexus\FloWare\Server\bin;H:\oracle\ora9i\bin;C:\Program Files\Oracle
\jre\1.3.1\bin;H:\Perl\bin\;H:\Tibco\tra\1.0\bin;H:\tibco\tra\1.0\bin;C:\Program
Files\Oracle\jre\1.1.8\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\
Wbem;H:\j2sdk1.4.1_02\bin;H:\apache-ant-1.5.4\bin;H:\jreversepro-1.4.1\bin;H:\ti
bco\tibrv\BIN
***************************************************
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
***************************************************
H:\eFw\efwdomain>"H:\bea\jdk131_06\bin\java" -hotspot -Xms32m -Xmx200m -Dweblogi
c.security.SSL.trustedCAKeyStore=H:\bea\weblogic700\server\lib\cacerts -Dweblogi
c.Name=efwserver -Dbea.home="H:\bea" -Dweblogic.management.username=system -Dweb
logic.management.password=manager123 -Dweblogic.ProductionModeEnabled= -Djava.se
curity.policy="H:\bea\weblogic700\server\lib\weblogic.policy" weblogic.Server
Starting WebLogic Server...
<Jan 15, 2004 4:19:59 PM EST> <Notice> <Management> <140005> <Loading configurat
ion H:\eFw\efwdomain\.\config.xml>
<Jan 15, 2004 4:20:04 PM EST> <Notice> <Security> <090082> <Security initializin
g using realm myrealm.>
<Jan 15, 2004 4:20:04 PM EST> <Notice> <WebLogicServer> <000327> <Starting WebLo
gic Admin Server "efwserver" for domain "efwdomain">
<Jan 15, 2004 4:20:13 PM EST> <Error> <JDBC> <001060> <Cannot startup connection
pool "efwPool" java.sql.SQLException: No suitable driver>
<Jan 15, 2004 4:20:13 PM EST> <Error> <JDBC> <001059> <Error during Data Source
creation: weblogic.common.ResourceException: DataSource(efwDataSource) can't be
created with non-existent Pool (connection or multi) (efwPool)
at weblogic.jdbc.common.internal.JdbcInfo.validateConnectionPool(JdbcInf
o.java:127)
at weblogic.jdbc.common.internal.JdbcInfo.startDataSource(JdbcInfo.java:
260)
at weblogic.jdbc.common.internal.JDBCService.addDeploymentx(JDBCService.
java:293)
at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.j
ava:270)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:375)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:303)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:256)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:207)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:732)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:714)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:417)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
57)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
25)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
ServerImpl.java:952)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
at $Proxy37.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:4114)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
s(SlaveDeployer.java:2257)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:373)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
65)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:832)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
at weblogic.Server.main(Server.java:32)
>
<Jan 15, 2004 4:20:13 PM EST> <Error> <JDBC> <001059> <Error during Data Source
creation: weblogic.common.ResourceException: DataSource(efwXADataSource) can't
b
e created with non-existent Pool (connection or multi) (efwPool)
at weblogic.jdbc.common.internal.JdbcInfo.validateConnectionPool(JdbcInf
o.java:127)
at weblogic.jdbc.common.internal.JdbcInfo.startDataSource(JdbcInfo.java:
189)
at weblogic.jdbc.common.internal.JDBCService.addDeploymentx(JDBCService.
java:293)
at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.j
ava:270)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:375)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:303)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:256)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:207)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:732)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:714)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:417)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
57)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
25)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
ServerImpl.java:952)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
at $Proxy37.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:4114)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
s(SlaveDeployer.java:2257)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:373)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
65)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:832)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
at weblogic.Server.main(Server.java:32)
>
<Jan 15, 2004 4:20:16 PM EST> <Error> <J2EE> <160001> <Error deploying applicati
on mapEntity.jar:
Deepak vohra
Manoj,
Is the driver class in the Classpath?
Is the target server set on the connection pool?
Joe Weinstein
Manoj wrote:
Hi Manoj. This exception is directly from java.sql.DriverManager. It typically
means the URL you specified for the driver is typed incorrectly so the oracle driver
doesn't recognise it. You should try the little online utility:
C:\> java utils.dbping ORACLE_THIN scott tiger DBHOSTMACHINE:PORT:SID
where DBHOSTMACHINE is the machine name the DBMS is running on, PORT is
the listener port for connections, and SID is the SID of the DBMS.
This will print out the url you want when it makes a successful connection.
Joe
Akilah McIntyre
2)Make sure you add your JDBC drivers to the beginning of CLASSPATH in either setDomainenv.cmd or setEnv.cmd
3)What really helped was BEA support and playing with BEA's JDBC example that shows how to create and deploy and use a data source.
Deepak Vohra
indicates the Connection Pool was not created.
1. Check the Driver class for the JDBC connection.
2. Check the Connection URL.
3. Set the target server for the Connection Pool.