Mine looks like this, but, I cannot connect ...
Thanks!
Oracle 8.1.7 on Solaris
Mark wrote:
If the pool shows up in the console, the definition is fine. The question is how you
are trying to connect...
Joe
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
conn = java.sql.DriverManager.getConnection("jdbc:oracle:oci8:@xxx", "xxx",
"xxx");
Pool name will be WrapPool
Thanks!
"Joseph Weinstein" <joe.rem...@bea.com.remove_this> wrote in message
news:3EB00632...@bea.com.remove_this...
Mark wrote:
> Joe, my code currecntly uses:
>
> DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
> conn = java.sql.DriverManager.getConnection("jdbc:oracle:oci8:@xxx", "xxx",
> "xxx");
>
> Pool name will be WrapPool
Ok, that's the problem. The pool that you showed was using our oracle driver,
but the code above is trying to make a direct (non-pooled) connection using
oracle's own driver. I'll assume you do want to use the pool, and that the pool
is using the correct oracle driver (the one you want, if you have any preference).
You should review our documentation on defining DataSources for our pools,
and using them to get connections. However, if you will describe how you want
to use JDBC connections, in what sort of application code, I will be able to
give you more advice.
Joe
Joe, also, still getting a problem in defining the pool. For example, I get
the following error:
- remote server: weblogic.management.internal.RemoteMBeanServerImpl@429498
weblogic.common.ResourceException: weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: Pool connect failed: java.sql.SQLException:
Connection Pool aaa does not exist.
at weblogic.jdbc.pool.Driver.connect(Driver.java:163)
When I use:
<JDBCConnectionPool DriverName="weblogic.jdbc.pool.Driver"
Name="aaa" Password="{3DES}LWiZDkOqmcDnqzXsrfqanw=="
Properties="user=system;server=helios" Targets=""
TestTableName="wrap_user" URL="jdbc:weblogic:pool:aaa"/>
<Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
Do you see anything wrong with this?
Mark
"Joseph Weinstein" <joe.rem...@bea.com.remove_this> wrote in message
news:3EB01A41...@bea.com.remove_this...
<JDBCConnectionPool ACLName="dynaPool"
DriverName="weblogic.jdbc.oci.Driver" Name="nukpool"
Password="{3DES}/f+HiF8wF1RNyibrHAoU7Q=="
Properties="user=xxxx;server=helios" Targets="myserver"
URL="jdbc:weblogic:oracle"
XAPassword="{3DES}/f+HiF8wF1RNyibrHAoU7Q=="/>
"Joseph Weinstein" <joe.rem...@bea.com.remove_this> wrote in message
news:3EB01A41...@bea.com.remove_this...
Mark wrote:
> Joe, also, still getting a problem in defining the pool. For example, I get
> the following error:
>
> - remote server: weblogic.management.internal.RemoteMBeanServerImpl@429498
> weblogic.common.ResourceException: weblogic.common.ResourceException:
> Could not create pool connection. The DBMS driver exception was:
> java.sql.SQLException: Pool connect failed: java.sql.SQLException:
> Connection Pool aaa does not exist.
> at weblogic.jdbc.pool.Driver.connect(Driver.java:163)
>
> When I use:
>
> <JDBCConnectionPool DriverName="weblogic.jdbc.pool.Driver"
> Name="aaa" Password="{3DES}LWiZDkOqmcDnqzXsrfqanw=="
> Properties="user=system;server=helios" Targets=""
> TestTableName="wrap_user" URL="jdbc:weblogic:pool:aaa"/>
> <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
>
> Do you see anything wrong with this?
>
Yes. a pool needs to use a DBMS-specific jdbc driver. The pool driver is
for application code to get access to a pool.
Joe
(I'm new to the java side)
Regards,
Mark
"Joseph Weinstein" <joe.rem...@bea.com.remove_this> wrote in message
news:3EB05D99...@bea.com.remove_this...
Mark wrote:
> Joe, I did get the pool created and a data source created and defined to the
> pool. Can you provide me with a sample code snipet to access the data source
> from a bean?
>
> (I'm new to the java side)
>
> Regards,
> Mark
http://edocs.bea.com/wls/docs70/jdbc/programming.html#1031899
Search for "Obtaining a Client Connection Using a DataSource"
Joe