Cannot startup connection pool no suitable driver /WLS 6.1 SP4
hi all,
i got a problem in creating a ConnectionPool with weblogic 6.1 sp4.
my connection pool has following config data:
URL:jdbc:oracle:[email protected]:1521:ESECD7
Driver:oracle.jdbc.driver.OracleDriver
props
username=aaaa
password=bbbb
in my startWebLogic.cmd i have following classpath:
set PATH=.\bin;%PATH%;c:\bea\wlserver6.1\config\mydomain;c:\bea\wlserver6.1\bin\oci817_8;c:\oracle\ora92\bin;%PATH%
set CLASSPATH=C:\oracle\ora92\jdbc\lib\classes111.zip;C:\oracle\ora92\jdbc\lib\classes12.zip;.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;c:\bea\jolt.jar;c:\bea\joltwls.jar;c:\bea\joltjse.jar
but i keep on gettign the exception Cannot startup connection pool.. no suitable
driver
to me it looks like everything is in classpath...
any ideas?
regards
marco
Marco wrote:
hi all,
i got a problem in creating a ConnectionPool with weblogic 6.1 sp4.
my connection pool has following config data:
URL:jdbc:oracle:[email protected]:1521:ESECD7
Driver:oracle.jdbc.driver.OracleDriver
props
username=aaaa
password=bbbb
in my startWebLogic.cmd i have following classpath:
set PATH=.\bin;%PATH%;c:\bea\wlserver6.1\config\mydomain;c:\bea\wlserver6.1\bin\oci817_8;c:\oracle\ora92\bin;%PATH%
set CLASSPATH=C:\oracle\ora92\jdbc\lib\classes111.zip;C:\oracle\ora92\jdbc\lib\classes12.zip;.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;c:\bea\jolt.jar;c:\bea\joltwls.jar;c:\bea\joltjse.jar
but i keep on gettign the exception Cannot startup connection pool.. no suitable
driver
to me it looks like everything is in classpath...
any ideas?
regards
marcoHi. Read the weblogi startServer script, and the startWLS script it calls. These
scripts build up a string which is added to the java commandline that starts
the server, with an argument -classpath ....... Unless the driver shows up there,
the server doesn't see it.
However, we already include a version of the oracle thin driver. It may not be
the best (it's old), so you will want to make sure you version gets in to the classpath
argument ahead of our stuff, but the old driver would have been invoked...
Therefore, I suspect your URL is not exactly correct. Please verify that this exact URL
works in a simple standalone JDBC program using the driver you want, without any
weblogic code in the picture.
thanks,
Joe
Similar Messages
-
Error creating a connection pool (No suitable driver)
I have just installed WLS6.1 SP3
I try to create a connection with the following parameters
URL = jdbc:oracle:thin@myOracleServer:1521:myOracleSID
DriverName = oracle.jdbc.driver.OracleDriver
every thing else is left as the defaults,
when I click create everything is OK.
I then go to the "Targets" tab and select myserver,
move it to the chosen column and click apply.
I then get the error
<Error> <JDBC> <Cannot startup connection pool "myCP" No suitable driver>
I looked at the doc edocs.bea.com/wls/docs61/jdbc/thirdparty.html
Under the section "Setting environment for your third party driver"
it implys that if your using sybase jconnect or oracle thin drivers
you do not need to do anything else.
I looked in the weblogic.jar file and the OracleDriver.class file
is there under oracle\jdbc\driver.
the CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
I would have thought that the driver class in the jar file
would have be picked up given the path & classname match the
driver name enter in the console.
Any ideas on how to fix this problem?"Robert Towler" <[email protected]> wrote in message
news:3dd3ea04$[email protected]..
Thanks Slava, you were correct,
I really appreciate it.Glad to help :)
Regards,
Slava Imeshev
"Slava Imeshev" <[email protected]> wrote:
Hi Robert,
Looks like colon is missing after jdbc:oracle:thin. The url should be
jdbc:oracle:thin:@myOracleServer:1521:myOracleSID
Regards,
Slava Imeshev
"Robert Towler" <[email protected]> wrote in message
news:3dd3e3c6$[email protected]..
I have just installed WLS6.1 SP3
I try to create a connection with the following parameters
URL = jdbc:oracle:thin@myOracleServer:1521:myOracleSID
DriverName = oracle.jdbc.driver.OracleDriver
every thing else is left as the defaults,
when I click create everything is OK.
I then go to the "Targets" tab and select myserver,
move it to the chosen column and click apply.
I then get the error
<Error> <JDBC> <Cannot startup connection pool "myCP" No suitable
driver>
>>>
I looked at the doc edocs.bea.com/wls/docs61/jdbc/thirdparty.html
Under the section "Setting environment for your third party driver"
it implys that if your using sybase jconnect or oracle thin drivers
you do not need to do anything else.
I looked in the weblogic.jar file and the OracleDriver.class file
is there under oracle\jdbc\driver.
the CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
I would have thought that the driver class in the jar file
would have be picked up given the path & classname match the
driver name enter in the console.
Any ideas on how to fix this problem? -
Error in creating a connection pool (No suitable driver)
I try to create a connection pool in a Weblogic server 7.0 with the following config:
URL:
jdbc:oracle:oci9:@db_name
Driver Classname:
oracle.jdbc.driver.OracleDriver
Properties(key=value):
user=user_name
password=user_password
dll=ocijdbc9
server=db_name
protocol=oci
my computer (windows 2000) has installed Oracle 9i client, and this connection
pool will connect to Oracle 8i server. Besides, I have config classes12.zip in
the "classpath" and ocijdbc9.dll in the "path" environment variables.
Can Oracle 9i driver connect to a Oracle 8i server? Or there is other problems?
Thanks in advance.Please try URL = jdbc:oracle:oci8:@db_name... that should be fine.
Yes, you can connect to 8i oracle database using 9i driver.
Also, make sure you have classes12.zip in classpath and ocijdbc9.dll in path.
Thanks,
Mitesh
Jacky Ho wrote:
I try to create a connection pool in a Weblogic server 7.0 with the following config:
URL:
jdbc:oracle:oci9:@db_name
Driver Classname:
oracle.jdbc.driver.OracleDriver
Properties(key=value):
user=user_name
password=user_password
dll=ocijdbc9
server=db_name
protocol=oci
my computer (windows 2000) has installed Oracle 9i client, and this connection
pool will connect to Oracle 8i server. Besides, I have config classes12.zip in
the "classpath" and ocijdbc9.dll in the "path" environment variables.
Can Oracle 9i driver connect to a Oracle 8i server? Or there is other problems?
Thanks in advance. -
Startup problems with XA connection pools on Oracle and WLS 6.1
I am having starup problems trying to set up a WLS 6.1 connection pool using
XA. When I try to start the server, I get the following exception:
<Nov 19, 2001 3:06:28 PM EST> <Error> <JDBC> <Cannot startup connection pool
"dbdev1XAPool" weblogic.common.ResourceException: java.sql.SQLException:
open failed for XAResource 'dbdev1' with error XAER_RMERR : A resource
manager error has occured in the transaction branch. Check Oracle XA trace
file(s) (if any) for database errors. The Oracle XA trace file(s) are
located at the directory where yo
u start the Weblogic Server, and have names like
xa_<pool_name><MMDDYYYY>.trc.
at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
at
weblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:600)
at
weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnec
tionEnvFactory.java:194)
at
weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnec
tionEnvFactory.java:54)
at
weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:698)
at
weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
at
weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:620
at
weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:329)
The contents of the Oracle trace file:
ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
150627.1312:344.344.330727191:
xaoopen:
xa_info=Oracle_XA+Acc=P/cmauser/admin+SesTm=100+DB=dbdev1+Threads=true+LogDi
r=.+DbgFl=0x15,rmid=330727191,flags=0x0
150627.1312:344.344.330727191:
ORA-12560: TNS:protocol adapter error
150627.1312:344.344.330727191:
xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12560.
150627.1312:344.344.330727191:
xaoopen: return -3
I am running WLS 6.1 and Oracle 8.1.7 on windows (separate machines). The
connection pool settings are:
<JDBCConnectionPool CapacityIncrement="0"
DriverName="weblogic.jdbc.oci.xa.XADataSource" InitialCapacity="40"
MaxCapacity="40" Name="dbdev1XAPool"
Properties="user=cmauser;password=admin;dataSourceName=dbdev1"
RefreshMinutes="15" ShrinkingEnabled="false" SupportsLocalTransaction="true"
Targets="cmatest" TestTableName="hppcontentsource" />
I have not had any problems connecting to the same database through regular
JDBC connection pools or through the utils.dbping utility.
What am I doing wrong?This is a dup message. Add "DebugConfigInfo OFF" in httpd.conf.
Jong
[email protected] (Olaf Foellinger) wrote:
>
Hi,
we're trying to setup apache on linux so that it's forwarding all jsp
requests to Bea WLS 6.0 on Solaris. We've installed the mod_wl.so
modules according to the documentation. When apache starts it shows the
following warning:
[Tue Jan 9 13:22:55 2001] [warn] Loaded DSO
/usr/lib/apache/1.3/mod_wl.so uses plain Apache 1.3 +API, this module
might crash under EAPI! (please recompile it with -DEAPI)
and in fact, when we try to load a jsp page we get
[Tue Jan 9 13:29:14 2001] [notice] child pid 5780 exit signal
Segmentation fault (11)
Does anyone have a working solution ? Can bea provide us with a plugin
compiled with EAPI ?
Greetings Olaf -
Hi All,
I have defined a connection pool to Sybase ASE 12.0. On WLS startup, the connection
fails due to a login failure. Needless to say, the user and passwords are absolutely
the right ones. IN included the def for the pool (config.xml) and the log output
below. Any ideas?
From config.xml:
<JDBCConnectionPool
DriverName="com.sybase.jdbc.SybDriver"
Name="egate2-pool"
Password="none"
Properties="user=mfinn;password=mfi123"
URL="jdbc:sybase:Tds:egate2.dev.east.frontiercorp.com:4100"
CapacityIncrement="1"
InitialCapacity="1"
MaxCapacity="2"
RefreshMinutes="0"
ShrinkPeriodMinutes="15"
ShrinkingEnabled="true"
Targets="mjf375"
TestConnectionsOnRelease="false"
TestConnectionsOnReserve="false"
/>
<JDBCDataSource
JNDIName="egate2-jdbcds"
Name="egate2"
PoolName="egate2-pool"
RowPrefetchEnabled="false"
StreamChunkSize="256"
/>
From weblogic.log:
####<Jul 10, 2001 12:24:16 PM EDT> <Error> <JDBC> <egatedev1> <mjf375> <main>
<system> <> <001060> <Cannot startup connection pool "egate2-pool" weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to
this exception for the reason(s).
at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
at com.sybase.tds.Tds.processLoginAckToken(Tds.java)
at com.sybase.tds.Tds.doLogin(Tds.java)
at com.sybase.tds.Tds.login(Tds.java)
at com.sybase.jdbc.SybConnection.<init>(SybConnection.java)
at com.sybase.jdbc.SybDriver.connect(SybDriver.java)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:188)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:130)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.ja
TIA,
MikeHi Mike. Don't specify the password except
as you have done in the properties. Let me
know...
Joe
Mike wrote:
>
Just to add:
1) I can login to the same URL (same login and password) from a standalone app
using the com.sybase.jdbc.SybDriver in the weblogic.jar. This is with user/password
being set in a properties object, as I assume is happening in WLS when the connection
is attempted. IOW, I am using getConnection(url,props) as opposed to getConnection(url,user,passwd,props).
2) The problem stated below also applies against a ASE 11.9.2 server.
Mike
"Mike" <[email protected]> wrote:
Hi All,
I have defined a connection pool to Sybase ASE 12.0. On WLS startup,
the connection
fails due to a login failure. Needless to say, the user and passwords
are absolutely
the right ones. IN included the def for the pool (config.xml) and the
log output
below. Any ideas?
From config.xml:
<JDBCConnectionPool
DriverName="com.sybase.jdbc.SybDriver"
Name="egate2-pool"
Password="none"
Properties="user=mfinn;password=mfi123"
URL="jdbc:sybase:Tds:egate2.dev.east.frontiercorp.com:4100"
CapacityIncrement="1"
InitialCapacity="1"
MaxCapacity="2"
RefreshMinutes="0"
ShrinkPeriodMinutes="15"
ShrinkingEnabled="true"
Targets="mjf375"
TestConnectionsOnRelease="false"
TestConnectionsOnReserve="false"
/>
<JDBCDataSource
JNDIName="egate2-jdbcds"
Name="egate2"
PoolName="egate2-pool"
RowPrefetchEnabled="false"
StreamChunkSize="256"
/>
From weblogic.log:
####<Jul 10, 2001 12:24:16 PM EDT> <Error> <JDBC> <egatedev1> <mjf375>
<main>
<system> <> <001060> <Cannot startup connection pool "egate2-pool" weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings
chained to
this exception for the reason(s).
at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
at com.sybase.tds.Tds.processLoginAckToken(Tds.java)
at com.sybase.tds.Tds.doLogin(Tds.java)
at com.sybase.tds.Tds.login(Tds.java)
at com.sybase.jdbc.SybConnection.<init>(SybConnection.java)
at com.sybase.jdbc.SybDriver.connect(SybDriver.java)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:188)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:130)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.ja
TIA,
Mike
PS: Folks: BEA WebLogic is expanding rapidly, with both entry and advanced positions
for people who want to work with Java, XML, SOAP and E-Commerce infrastructure products.
We have jobs at Nashua NH, Liberty Corner NJ, San Francisco and San Jose CA.
Send resumes to [email protected] -
Cannot create connection pool with weblogic jDriver XA for oracle
Hi everybody,
we have serious problems configuring the weblogic jDriver for Oracle with support
for distributed transactions.
Everything works fine with the non-XA driver.
We tried the suggestions given here before like setting the environment variable
ORACLE_SID. However, this does not change the errors we get. We use Weblgic Server
6.1 SP2 with oracle 8.1.7 (client and server) under Windows NT.
When attempting to create the connection pool, we get the following exception:
Starting Loading jDriver/Oracle .....
<14.05.2002 15:48:30 CEST> <Error> <JDBC> <Cannot startup connection pool "DiplPool"
weblogic.common.ResourceException: java.sql.SQLException: open failed for XAResource
'DiplPool' with error XAER_RMERR : A resource manager error has occured in the transaction
branch. Check Oracle XA trace file(s) (if any) for database errors. The Oracle XA
trace file(s) are located at the directory where you start the Weblogic Server, and
have names like xa_<pool_name><MMDDYYYY>.trc.
at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
at weblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:601)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:200)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:57)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
The trace file looks like this:
ORACLE XA: Version 8.1.5.0.0. RM name = 'Oracle_XA'.
113105.161:160.160.-1344514975:
xaoopen: xa_info=Oracle_XA+Acc=P/schamper/schamper+SesTm=100+DB=DiplPool+Threads=true+LogDir=.+DbgFl=0x15,rmid=-1344514975,flags=0x0
113105.161:160.160.-1344514975:
ORA-12560: TNS: Fehler bei Protokolladapter
113105.161:160.160.-1344514975:
xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12560.
113105.161:160.160.-1344514975:
xaoopen: return -3
We suspect that we do not set the properties of the connection pool correctly. The
declaration of the pool in config.xml looks something like the following:
<JDBCConnectionPool CapacityIncrement="1" DriverName="weblogic.jdbc.oci.xa.XADataSource"
InitialCapacity="10" MaxCapacity="15" Name="DiplPool"
Properties="user=scott;password=tiger;url=jdbc:weblogic:oracle:srlaptop_aidenbach.muc.sdm-research.de;dataSourceName=DiplPool"
Targets="Marvin" TestTableName="privcust" URL="jdbc:weblogic:oracle:srlaptop_aidenbach.muc.sdm-research.de"/>
Are there any known issues with the XA driver and the versions of oracle and Weblogic
we use? Can someone tell us how exactly we have to define the connection pool or
provide an example?
Any help would be greatly appreciated.
Best regards,
MichaelHi Michael
Here is an example connection pool tag,
<JDBCConnectionPool
Name="oraXAPool"
Targets="myserver"
DriverName="weblogic.jdbc.oci.xa.XADataSource"
InitialCapacity="1"
MaxCapacity="10"
CapacityIncrement="2"
Properties="user=scott;password=tiger;server=ORCL"
/>
Ensure that the server=ORCL is replaced by server=<what ever the Alias is
defined in TNSNAMES.ORA file>
You dont have to specify the URL for this.
hth
sree
"Michael Wufka" <[email protected]> wrote in message
news:[email protected]...
>
Hi everybody,
we have serious problems configuring the weblogic jDriver for Oracle withsupport
for distributed transactions.
Everything works fine with the non-XA driver.
We tried the suggestions given here before like setting the environmentvariable
ORACLE_SID. However, this does not change the errors we get. We useWeblgic Server
6.1 SP2 with oracle 8.1.7 (client and server) under Windows NT.
When attempting to create the connection pool, we get the followingexception:
Starting Loading jDriver/Oracle .....
<14.05.2002 15:48:30 CEST> <Error> <JDBC> <Cannot startup connection pool"DiplPool"
weblogic.common.ResourceException: java.sql.SQLException: open failed forXAResource
'DiplPool' with error XAER_RMERR : A resource manager error has occured inthe transaction
branch. Check Oracle XA trace file(s) (if any) for database errors. TheOracle XA
trace file(s) are located at the directory where you start the WeblogicServer, and
have names like xa_<pool_name><MMDDYYYY>.trc.
at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
atweblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:601)
atweblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnec
tionEnvFactory.java:200)
atweblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnec
tionEnvFactory.java:57)
atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:698)
atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:329)
The trace file looks like this:
ORACLE XA: Version 8.1.5.0.0. RM name = 'Oracle_XA'.
113105.161:160.160.-1344514975:
xaoopen:xa_info=Oracle_XA+Acc=P/schamper/schamper+SesTm=100+DB=DiplPool+Threads=true
LogDir=.DbgFl=0x15,rmid=-1344514975,flags=0x0
113105.161:160.160.-1344514975:
ORA-12560: TNS: Fehler bei Protokolladapter
113105.161:160.160.-1344514975:
xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12560.
113105.161:160.160.-1344514975:
xaoopen: return -3
We suspect that we do not set the properties of the connection poolcorrectly. The
declaration of the pool in config.xml looks something like the following:
<JDBCConnectionPool CapacityIncrement="1"DriverName="weblogic.jdbc.oci.xa.XADataSource"
InitialCapacity="10" MaxCapacity="15" Name="DiplPool"
Properties="user=scott;password=tiger;url=jdbc:weblogic:oracle:srlaptop_aide
nbach.muc.sdm-research.de;dataSourceName=DiplPool"
Targets="Marvin" TestTableName="privcust"URL="jdbc:weblogic:oracle:srlaptop_aidenbach.muc.sdm-research.de"/>
>
Are there any known issues with the XA driver and the versions of oracleand Weblogic
we use? Can someone tell us how exactly we have to define the connectionpool or
provide an example?
Any help would be greatly appreciated.
Best regards,
Michael -
JDBC receiver error Cannot establish connection with the registered driver
Hi Expert,
I am constructing a proxy to JDBC scenario. And I am getting error saying "
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error when attempting to get processing resources: com.sap.aii.af.lib.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection with the registered driver. oracle.jdbc.driver.OracleDriver returns: The Network Adapter could not establish the connection. : SQLException: The Network Adapter could not establish the connection"
I can get into my Oracle database using TOAD with same IP address, user name and password. Could anybody tell me what should I do? Thanks a lot!
CharlesHi,
Check with your network team, network conenction between PI and Data base not working , Network team have to open Data base system ports inorder connect PI System.
check with Basis team about network connectivty,like they are bale to ping Data base server ip or not.
please go through below thread,
SQLException: Io exception: The Network Adapter could not establish the con
regards,
ganesh. -
Problem with creating Connection pool and JNDI, driver is not detected
Hi,
I have an issue with creating Connection Pool and JNDI.
I'm using:
- JDK 1.6
- OS: Linux(ubuntu 8.10)
- Netbeans IDE 6.5.1
- Java EE 5.0
- Apache Tomcat 6.0.18 Its lib directory contains all necessary jar files for Oracle database driver
- Oracle 11g Enterprise
My problem is that the Oracle database driver is not detected when I want to create a pool (it works pretty well and is detected without any problem when I create ordinary connection by DriverManager)
Therefore after running:
InitialContext ic = new InitialContext();
Context context = (Context)ic.lookup("java:comp/env");
DataSource dataSource = (DataSource)context.lookup("jdbc/oracle11g");
Connection connection = dataSource.getConnection();and right after dataSource.getConnection() I have the following exception:
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot load JDBC driver class 'oracle.jdbc.OracleDriver'
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1136)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at servlets.Servlet1.doPost(Servlet1.java:47)
at servlets.Servlet1.doGet(Servlet1.java:29)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at sun.misc.Launcher$ExtClassLoader.findClass(Launcher.java:229)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1130)
... 17 more
My application context file (context.xml) is:
<?xml version="1.0" encoding="UTF-8"?>
<Context path="/WebApplication3">
<Resource auth="Container"
driverClassName="oracle.jdbc.OracleDriver"
maxActive="8"
maxIdle="4"
name="jdbc/oracle11g"
username="scott"
password="tiger"
type="javax.sql.DataSource"
url="jdbc:oracle:thin:@localhost:1521:database01" />
</Context>and my web.xml is:
<resource-ref>
<description>Oracle Datasource example</description>
<res-ref-name>jdbc/oracle11g</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
...I found similar threads in different forums including sun, such as
http://forums.sun.com/thread.jspa?threadID=567630&start=0&tstart=0
http://forums.sun.com/thread.jspa?threadID=639243&tstart=0
http://forums.sun.com/thread.jspa?threadID=5312178&tstart=0
, but no solution.
As many suggest, I also tried to put context directly in the server.xml (instead of my application context) and referencing it by <ResourceLink /> inside my application context but it didn't work and instead it gave me the following message:
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver of class ' ' for connect URL 'null'
Has anyone succeeded in creating a connection pool with JNDI by using Tomcat 6 or higher ? If yes, could kindly explain about the applied method.
Regards,Hello again,
Finally I managed to run my application also with Tomcat 6.0.18. There was only two lines that had to be modified
in the context.xml file (the context of my application project and not server's)
Instead of writing
<Context antiJARLocking="true" path="/WebApplication2">
type="javax.sql.DataSource"
factory="org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory"
</Context>we had to write:
<Context antiJARLocking="true" path="/WebApplication2">
type="oracle.jdbc.pool.OracleDataSource"
factory="oracle.jdbc.pool.OracleDataSourceFactory"
</Context>- No modification was needed to be done at server level (niether server.xml nor server context.xml)
- I just added the ojdbc6.jar in $CATALINA_HOME/lib (I didn't even need to add it in WEB-INF/lib of my project)
- The servlet used to do the test was the same that I presented in my precedent post.
For those who have encountered my problem and are interested in the format of the web.xml and context.xml
with Tomcat 6.0, you can find them below:
Oracle server: Oracle 11g Enterprise
Tomcat server version: 6.0.18
Oracle driver: ojdbc.jar
IDE: Netbeans 6.5.1
The context.xml file of the web application
<?xml version="1.0" encoding="UTF-8"?>
<Context antiJARLocking="true" path="/WebApplication2">
<Resource name="jdbc/oracle11g"
type="oracle.jdbc.pool.OracleDataSource"
factory="oracle.jdbc.pool.OracleDataSourceFactory"
url="jdbc:oracle:thin:@localhost:1521:database01"
driverClassName="oracle.jdbc.OracleDriver"
userName="scott"
password="tiger"
auth="Container"
maxActive="100"
maxIdle="30"
maxWait="10000"
logAbandoned="true"
removeAbandoned="true"
removeAbandonedTimeout="60" />
</Context>The web.xml of my web application
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
<resource-ref>
<description>Oracle Database 11g DataSource</description>
<res-type>oracle.jdbc.pool.OracleDataSource</res-type>
<res-auth>Container</res-auth>
<res-ref-name>jdbc/oracle11g</res-ref-name>
</resource-ref>
<servlet>
<servlet-name>Servlet1</servlet-name>
<servlet-class>servlets.Servlet1</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>Servlet1</servlet-name>
<url-pattern>/Servlet1</url-pattern>
</servlet-mapping>
<session-config>
<session-timeout>
30
</session-timeout>
</session-config>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
</web-app>Ok, now I'm happy as the original problem is completely solved
Regards -
BEA-001156 - connection pool reset failed on WLS 8.1.6
Hi,
I run WLS 8.1.6 on Linux and JRockit 1.4.2_12. I got the following error when I tried to reset a connection pool manually from the console. This does not happen all the time, so it is hard to reproduce. There is no change to database login credential. Any suggestions are appreciated. Thanks in advance.
BEA-141132
Dynamic invocation while executing action reset on etg:Locat
ion=nyclrwp_14654_2,Name=testPool,ServerRuntime=mycluster,
Type=JDBCConnectionPoolRuntime MBean instance
failed. The method reset with signature [] was invoked with
parameters as [].
weblogic.common.ResourceException: Refresh operation was partially successful, (1)
out of (1) resources could not be refreshed.
at weblogic.common.resourcepool.ResourcePoolImpl.refresh(ResourcePoolImpl.java:669)
at weblogic.jdbc.common.internal.ConnectionPool.reset(ConnectionPool.java:789)
at weblogic.jdbc.common.internal.ConnectionPoolRuntimeMBeanImpl.reset(ConnectionPoolRuntimeMBeanImpl.java:420)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:491)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:429)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
BEA-001156
Stack trace associated with message 001129 follows:
java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to
this exception for the reason(s).
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:506)
at com.sybase.jdbc2.tds.Tds.processLoginAckToken(Tds.java:3224)
at com.sybase.jdbc2.tds.Tds.doLogin(Tds.java:483)
at com.sybase.jdbc2.tds.Tds.login(Tds.java:405)
at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:218)
at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:195)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:174)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:126)
at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:251)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:330)
at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1694)
at weblogic.common.resourcepool.ResourcePoolImpl.refreshAvlResources(ResourcePoolImpl.java:1982)
at weblogic.common.resourcepool.ResourcePoolImpl.refresh(ResourcePoolImpl.java:664)
at weblogic.jdbc.common.internal.ConnectionPool.reset(ConnectionPool.java:789)
at weblogic.jdbc.common.internal.ConnectionPoolRuntimeMBeanImpl.reset(ConnectionPoolRuntimeMBeanImpl.java:420)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
BEA-001129
Received exception while creating connection for pool "cpl1C
onnectionPool": JZ00L: Login failed. Examine the SQLWarnings
chained to this exception for the reason(s).
BEA-001128 Connection for pool "testPool" closed.
BEA-001099 Connection pool "testPool" reset by "system"lei wang wrote:
Hi,
I run WLS 8.1.6 on Linux and JRockit 1.4.2_12. I got the following error when I tried to reset a connection pool manually from the console. This does not happen all the time, so it is hard to reproduce. There is no change to database login credential. Any suggestions are appreciated. Thanks in advance.
Please tell me why you are resetting the pool. The reason may have something
to do with the failure messages below. The root cause of these messages is
that the pool is trying to make a new JDBC connection to Sybase, in exactly
the same way it does all the time, but for whatever reason, the DBMS is
refusing the connection request. The pool should be OK anyway, ongoing,
as long as/when the DBMS is back up and accepting connection requests.
Joe
>
BEA-141132
Dynamic invocation while executing action reset on etg:Locat
ion=nyclrwp_14654_2,Name=testPool,ServerRuntime=mycluster,
Type=JDBCConnectionPoolRuntime MBean instance
failed. The method reset with signature [] was invoked with
parameters as [].
weblogic.common.ResourceException: Refresh operation was partially successful, (1)
out of (1) resources could not be refreshed.
at weblogic.common.resourcepool.ResourcePoolImpl.refresh(ResourcePoolImpl.java:669)
at weblogic.jdbc.common.internal.ConnectionPool.reset(ConnectionPool.java:789)
at weblogic.jdbc.common.internal.ConnectionPoolRuntimeMBeanImpl.reset(ConnectionPoolRuntimeMBeanImpl.java:420)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:491)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:429)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
BEA-001156
Stack trace associated with message 001129 follows:
java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to
this exception for the reason(s).
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:506)
at com.sybase.jdbc2.tds.Tds.processLoginAckToken(Tds.java:3224)
at com.sybase.jdbc2.tds.Tds.doLogin(Tds.java:483)
at com.sybase.jdbc2.tds.Tds.login(Tds.java:405)
at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:218)
at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:195)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:174)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:126)
at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:251)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:330)
at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1694)
at weblogic.common.resourcepool.ResourcePoolImpl.refreshAvlResources(ResourcePoolImpl.java:1982)
at weblogic.common.resourcepool.ResourcePoolImpl.refresh(ResourcePoolImpl.java:664)
at weblogic.jdbc.common.internal.ConnectionPool.reset(ConnectionPool.java:789)
at weblogic.jdbc.common.internal.ConnectionPoolRuntimeMBeanImpl.reset(ConnectionPoolRuntimeMBeanImpl.java:420)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
BEA-001129
Received exception while creating connection for pool "cpl1C
onnectionPool": JZ00L: Login failed. Examine the SQLWarnings
chained to this exception for the reason(s).
BEA-001128 Connection for pool "testPool" closed.
BEA-001099 Connection pool "testPool" reset by "system" -
How to create the connection pool using jdbc20 driver?
Hi all,
My configuration is WL4.5 SP5 + jdk1.2.2+WinNT+ Oracle thin driver
8.1.6.
It is creating the connections with weblogic.jdbc.pool.Driver, whereas i
want the connections in the pool to be created with jdbc20 driver. This
how my pool definition is defined.
weblogic.jdbc.connectionPool.PoolName=\
url=jdbc:oracle:thin:@<IP address>:<Instance>,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=1,\
maxCapacity=40,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=5,\
refreshMinutes=10,\
testTable=dual,\
props=user=XXXX;password=XXXX
The reason is I want to use BLOB's. I have a message posted in jdbc news
group with the exception i got. But since this more of a environement
issue i am posting it here.
Any help is appreciated,
Thanks
JohnHere is the correct pool definition.
################JDBC20 Driver#########################
weblogic.jdbc.connectionPool.jdbc20Pool=\
url=jdbc20:weblogic:oracle,\
driver=weblogic.jdbc20.oci.Driver,\
loginDelaySecs=1,\
initialCapacity=1,\
maxCapacity=1,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshMinutes=10,\
testTable=dual,\
props=user=SCOTT;password=tiger;server=goldengate
weblogic.allow.reserve.weblogic.jdbc.connectionPool.jdbc20Pool=guest
Hope this helps,
--Kumar
Kuppuswamy Seshadhri wrote:
I think you are missing the port number.
A working example,
Ensuring
- TSNAMES is setup and the service is running
- set ORACLE_HOME variable in setenv.cmd
weblogic.jdbc.connectionPool.theOraclePool=\
url=jdbc:oracle:thin:@IPADRESS:1521:orcl,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=1,\
maxCapacity=10,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshMinutes=10,\
testTable=dual,\
props=user=XXXX;password=XXXX;
weblogic.allow.reserve.weblogic.jdbc.connectionPool.theOraclePool=everyone
Kuppu
"John Galt" <[email protected]> wrote in message
news:[email protected]..
Hi all,
My configuration is WL4.5 SP5 + jdk1.2.2+WinNT+ Oracle thin driver
8.1.6.
It is creating the connections with weblogic.jdbc.pool.Driver, whereas i
want the connections in the pool to be created with jdbc20 driver. This
how my pool definition is defined.
weblogic.jdbc.connectionPool.PoolName=\
url=jdbc:oracle:thin:@<IP address>:<Instance>,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=1,\
maxCapacity=40,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=5,\
refreshMinutes=10,\
testTable=dual,\
props=user=XXXX;password=XXXX
The reason is I want to use BLOB's. I have a message posted in jdbc news
group with the exception i got. But since this more of a environement
issue i am posting it here.
Any help is appreciated,
Thanks
John -
Connection Pool Failure: "No suitable driver"
Hi,
Upon server startup, I get the following result:
<Nov 7, 2001 4:18:32 PM CST> <Error> <JDBC> <Cannot startup connection pool "ora
cleTrufflePool" No suitable driver>
I assumed it was a path problem, but in the startWebLogic.cmd script I've set the PATH and CLASSPATH variables to the same as in a separate command window that can successfully dbping the Oracle db.
One thing I completely don't understand is what the URL value should be for the pool, and I can't see a pattern in the examples and docs I've found on this. Here are my pool settings, at any rate:
Name: oracleTrufflePool
URL: myOracleServerName
Driver Classname: weblogic.jdbc.oci.Driver
Properties:
user=user
password=password
server=myOracleServerName
ACLName: user
Password: password
As you can see, I also don't understand whether the Oracle user name and password must be duplicated in the Properties section, or should they really only be listed in the ACLName and Password fields (in the Server Console UI)?
TIA,
SteveHi. The issue is that the URL you give is not the URL the driver (weblogic.jdbc.oci.Driver)
wants. The URL should be "jdbc:webLogic:oci". The properties user, password and server
will be passed to the driver for conenction attempts. The ACL is for who gets to use the
pool, and the other password entry is only if you need the DBMS password to be encrypted
in the XML. If so, set that password value, and don't have it in the driver properties.
Joe
Steve Clark wrote:
>
Hi,
Upon server startup, I get the following result:
<Nov 7, 2001 4:18:32 PM CST> <Error> <JDBC> <Cannot startup connection pool "ora
cleTrufflePool" No suitable driver>
I assumed it was a path problem, but in the startWebLogic.cmd script I've set the PATH and CLASSPATH variables to the same as in a separate command window that can successfully dbping the Oracle db.
One thing I completely don't understand is what the URL value should be for the pool, and I can't see a pattern in the examples and docs I've found on this. Here are my pool settings, at any rate:
Name: oracleTrufflePool
URL: myOracleServerName
Driver Classname: weblogic.jdbc.oci.Driver
Properties:
user=user
password=password
server=myOracleServerName
ACLName: user
Password: password
As you can see, I also don't understand whether the Oracle user name and password must be duplicated in the Properties section, or should they really only be listed in the ACLName and Password fields (in the Server Console UI)?
TIA,
Steve -
Could not create pool connection.The DBMS driver exception was:java.sql.SQLException:
ORA-01017: invalid username/password
Even though I could able to connect to Oracle database using correct userid,password
and HostString using OracleClient, I couldnt able to do with connectionpool. Here
is the error message..
<Jan 21, 2003 2:27:50 AM PST> <Notice> <WebLogicServer> <Starting WebLogic Admin
Server "examplesServer" for domain "examples">
Starting Loading jDriver/Oracle .....
---------- LOGIN ERROR CODE: 1017
---------- LOGIN ERROR CODE: 1017
<Jan 21, 2003 2:28:06 AM PST> <Error> <JDBC> <Cannot startup connection pool "or
aclePool" weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: ORA-01017: invalid username/password; logon denied - (Obj
ectel/********@ora8i)
at weblogic.db.oci.OciConnection.getLDAException(OciConnection.java:164)
at weblogic.jdbc.oci.Driver.connect(Driver.java:112)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:193)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:209)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
>
<Jan 21, 2003 2:28:14 AM PST> <Notice> <Management> <Application Poller started
for development server.>
<Jan 21, 2003 2:28:19 AM PST> <Notice> <WebLogicServer> <ListenThread listening
on port 7001>
<Jan 21, 2003 2:28:19 AM PST> <Notice> <WebLogicServer> <SSLListenThread listeni
ng on port 7002>
<Jan 21, 2003 2:28:20 AM PST> <Notice> <Management> <Starting discovery of Manag
ed Server... This feature is on by default, you may turn this off by passing -Dw
eblogic.management.discover=false>
<Jan 21, 2003 2:28:20 AM PST> <Notice> <WebLogicServer> <Started WebLogic Admin
Server "examplesServer" for domain "examples" running in Development Mode>URL=jdbc:weblogic:oracle:oracle8i(server)
Driver Classname=weblogic.jdbc.oci.Driver
AClname=weblogic.jdbc.connectionPool.oraclePool
intialcapacity=1
MaximumCapacity=10
Capacity Increment=2
Login Delay Seconds=1sec
Refresh Period=15 Minutes
Supports Local Transaction=No
Allow Shrinking=No
Shrink Period=15
Prepared Statement Cache Size=10
TargetServer=ExamplesServer
Properties
user=Objectel
password=superman
Test table=yes
Test Reserved Connections=yes
Test Released Connections=Yes
I could able to connect to oracledataBase if I use
user=scott
password=tiger
with any other database user Iam getting the following error
Could not create pool connection. The DBMS driver exception was:java.sql.SQLException:
ORA-01017: invalid username/password
"Neo Gigs" <[email protected]> wrote:
By end of the error you shown:
<Jan 21, 2003 2:28:20 AM PST> <Notice> <WebLogicServer> <Started WebLogicAdmin
Server "examplesServer" for domain "examples" running in DevelopmentMode>
You are running the Examples application shipped with WLS, which I guest
the
correct DB to connect with is Cloudscape yet to Oracle, unless you make
changes to the original ConnectionPool in the examples. Anyhow, please
show
us your configuration of the ConnectionPool used when this error pops.
"Raj" <[email protected]> wrote in message
news:[email protected]...
Could not create pool connection.The DBMS driver exceptionwas:java.sql.SQLException:
ORA-01017: invalid username/password
Even though I could able to connect to Oracle database using correctuserid,password
and HostString using OracleClient, I couldnt able to do withconnectionpool. Here
is the error message..
<Jan 21, 2003 2:27:50 AM PST> <Notice> <WebLogicServer> <Starting WebLogicAdmin
Server "examplesServer" for domain "examples">
Starting Loading jDriver/Oracle .....
---------- LOGIN ERROR CODE: 1017
---------- LOGIN ERROR CODE: 1017
<Jan 21, 2003 2:28:06 AM PST> <Error> <JDBC> <Cannot startup connectionpool "or
aclePool" weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: ORA-01017: invalid username/password; logondenied - (Obj
ectel/********@ora8i)
atweblogic.db.oci.OciConnection.getLDAException(OciConnection.java:164)
at weblogic.jdbc.oci.Driver.connect(Driver.java:112)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:193)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)
atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:698)
atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:282)
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:623)
atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:279)
atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:233)
atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:621)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.updateDeployments(Unknown Source)
atweblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2761)
atweblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:370)
atweblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:621)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.start(Unknown Source)
atweblogic.management.configuration.ApplicationManagerMBean_CachingStub
start(ApplicationManagerMBean_CachingStub.java:480)
atweblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:209)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)
atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:698)
atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:282)
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:623)
atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:279)
atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:233)
atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:621)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.updateDeployments(Unknown Source)
atweblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2761)
atweblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:370)
atweblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:621)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.start(Unknown Source)
atweblogic.management.configuration.ApplicationManagerMBean_CachingStub
start(ApplicationManagerMBean_CachingStub.java:480)
atweblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
>
<Jan 21, 2003 2:28:14 AM PST> <Notice> <Management> <Application Pollerstarted
for development server.>
<Jan 21, 2003 2:28:19 AM PST> <Notice> <WebLogicServer> <ListenThreadlistening
on port 7001>
<Jan 21, 2003 2:28:19 AM PST> <Notice> <WebLogicServer> <SSLListenThreadlisteni
ng on port 7002>
<Jan 21, 2003 2:28:20 AM PST> <Notice> <Management> <Starting discoveryof
Manag
ed Server... This feature is on by default, you may turn this off bypassing -Dw
eblogic.management.discover=false>
<Jan 21, 2003 2:28:20 AM PST> <Notice> <WebLogicServer> <Started WebLogicAdmin
Server "examplesServer" for domain "examples" running in DevelopmentMode> -
Weblogic 6.1 sp2 Connection Pool will not connect to oci901 driver
ok, I am trying to get weblogic to connect to the connection pool in solaris. I created
the pool in the console with the following:
URL = jdbc:weblogic:oracle
Driver Class Name = weblogic.jdbc.oci.Driver
Properties = user=sa password=*****
I also set the LD_LIBRARY PATH as directed.
LD_LIBRARY_PATH=/usr/local/wlserver6.1/lib/solaris/oci901_8:ORACLE/lib
Oracle is on a seperate box then the box that Weblogic is installed on so I think
the problem is in my LD_LIBRARY_PATH. Here is the error I am getting. Any help
would be appreciated.
Starting Loading jDriver/Oracle .....
<Jun 7, 2002 9:04:25 AM CDT> <Error> <JDBC> <Cannot startup connection pool "FargoPool"
weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: System.loadLibrary(weblogicoci37) threw java.lang.UnsatisfiedLinkError:
/usr/local/wlserver6.1/lib/solaris/oci901_8/libweblogicoci37.so: ld.so.1: /home/bea/jdk131/jre/bin/../bin/sparc/native_threads/java:
fatal: libclntsh.so.9.0: open failed: No such file or directory
at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:226)
at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:193)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy8.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy17.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:209)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy8.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy17.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)"Tim" <[email protected]> wrote:
>
I have the following setup.
For QA, 1 IIS Server (using plug-in from 6.1 SP2) forwarding all request
to a
cluster on the backend. (2 Physical Servers, 4 JVM's). I do have a firewall
in
between the IIS Server & the backend servers.
According to the docs, the IIS plug-in is supposed to establish a connection
pool
to the backend. I do not see this behavior.
I see a connection created/close per request.
So , I have 2 questions:
1. Does the IIS Plug-in use connection Pooling, Do you have to enable
it ?
2. How do I control the pool size ?
Thanks in advance,
TimDoes anyone from BEA monitor this newsgroup ?
I have also opened up a case (1 week old) with tech support and still do not have
an answer. This is very frustrating considering the cost of owning this environment.
Tim -
JDBC20 connect pool issue using OCI driver
I tried to use:
url=jdbc20:weblogic:oracle.
driver=weblogic.jdbc20.oci.Driver
and got the following error:
<Jul 11, 2001 5:52:34 PM PDT> <Error> <JDBC Connection Pool> <Cannot
startup connection pool "ExrGlobalDbPool" Cannot load driver class:
weblogic.jdbc20.oci.Driver>
"Chuan Li" <[email protected]> wrote in message news:<[email protected]>...
If you use the driver provided by Oracle, then use the following:
url=jdbc:oracle:oci8:
driver=oracle.jdbc.driver.OracleDriver
"Jeff Guo" <[email protected]> wrote:
Hi,
What is the correct way to define the url in the jdbc connection pool
to
support jdbc20
features using Oracle OCI driver?
Thanks!
Jeff -
Connection Pooling in Weblogic Server6.1
Hi All..,
I want to implement Connection pooling in my EJB application.When i use a oci
driver i am getting the following error.Can anyone plz help me out?.
Thanks & Regards.,
B.Naveen Kumar
Starting Loading jDriver/Oracle .....
<Jul 2, 1999 12:57:04 PM IST> <Error> <JDBC> <Cannot startup connection pool "oraclePool"
weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: System.loadLibrary(weblogicoci37) threw java.lang.UnsatisfiedLinkError:
no weblogicoci37 in java.library.path
at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:226)
at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:131)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:620)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy45.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2706)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:360)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy66.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
at weblogic.management.Admin.finish(Admin.java:561)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
at weblogic.Server.main(Server.java:35)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:205)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:131)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:620)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy45.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2706)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:360)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy66.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
at weblogic.management.Admin.finish(Admin.java:561)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
at weblogic.Server.main(Server.java:35)
>This url will help you set the library path correctly:
(I am not sure which os you are seeing!!)
http://e-docs.bea.com/wls/docs61/oracle/install_jdbc.html
"Naveen Kumar" <[email protected]> wrote:
>
Hi All..,
I want to implement Connection pooling in my EJB application.When i use
a oci
driver i am getting the following error.Can anyone plz help me out?.
Thanks & Regards.,
B.Naveen Kumar
Starting Loading jDriver/Oracle .....
<Jul 2, 1999 12:57:04 PM IST> <Error> <JDBC> <Cannot startup connection
pool "oraclePool"
weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: System.loadLibrary(weblogicoci37) threw java.lang.UnsatisfiedLinkError:
no weblogicoci37 in java.library.path
at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:226)
at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:131)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:620)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy45.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2706)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:360)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy66.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
at weblogic.management.Admin.finish(Admin.java:561)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
at weblogic.Server.main(Server.java:35)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:205)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:131)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:620)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy45.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2706)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:360)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy66.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
at weblogic.management.Admin.finish(Admin.java:561)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
at weblogic.Server.main(Server.java:35)
>
Maybe you are looking for
-
Animated GIF won't animate or not even show at all
I have been using animated GIF with no problem so far but now with iWeb 08 sometimes it works with certain GIFs documents or sometimes won't with other GIFs documents. Why ? And what can I do about this ? What is the solution ? Message was edited by:
-
Mini-display == VGA
I was going to hop out and buy one of these new MacBook Pro's but unless I missed it, the Apple Store is not currently carrying any adapters for them (VGA, HDMI, or DVI). At work I use my MacBook exclusively with a 24" HP display with VGA. Any idea w
-
When .ai files are actually PDFs
So, in an earlier thread today, AI or EPS?, Wade questioned whether .AI files are really PDFs. I did a survey just now with Illustrator CS5 (15.0.2) on Mac OSX, on a document with a single letter 'p' (400pt Myriad Pro Regular). Saving in all current
-
Compressor 2.3 - Quicktime error:0
HI All This morning I wake up with this new thing. Im using FCP 5.1.1 and a 15minutes DV Pal sequence, already converted in the past. This morning I've tried to re-encode the sequence using DVD 90 min. High quality and I've got this new message : Qui
-
Hi I have updated my iPhone 4 but how do I update my iPad
How do update my ipad to the new ios5 my iPhone 4 is already done? And how do I use the imessage?