What jar contains weblogic.jdbc.pool.Driver connection pool class?

Hi all,
I am trying to use the JDeveloper IDE to generate code that I'll deploy on WebLogic
6.1.
I want to add the necessary files to the JDeveloper classpath so that during development
it can use my
weblogic connection pool. I've looked all over and can't seem to find it. It's
not in weblogic.jar. Anyone know
what file contains weblogic.jdbc.pool.Driver?
Thanks in advance,
Norm

Thanks. I don't know how I missed it in the first place.
"Sree Bodapati" <[email protected]> wrote:
weblogic.jar
sree
"Norm Heske" <[email protected]> wrote in message
news:3ba246c2$[email protected]..
Hi all,
I am trying to use the JDeveloper IDE to generate code that I'll deployon
WebLogic
6.1.
I want to add the necessary files to the JDeveloper classpath so thatduring development
it can use my
weblogic connection pool. I've looked all over and can't seem to findit.
It's
not in weblogic.jar. Anyone know
what file contains weblogic.jdbc.pool.Driver?
Thanks in advance,
Norm

Similar Messages

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

Jbuilder & weblogic.jdbc.mssqlserver4.Driver

I use jbuilder8 and jdbc driver " weblogic.jdbc.mssqlserver4.Driver " to connect mssql2000..
when I use database pilot of jbuilder8 to setup a datasource..
I got an error Error " connecting to database: java.lang.NoClassDefFoundError: weblogic/version "
what should I do now ?..

Do you have weblogic.jar in your CLASSPATH?
"owner" <[email protected]> wrote in message news:[email protected]..
I use jbuilder8 and jdbc driver " weblogic.jdbc.mssqlserver4.Driver " to connect mssql2000..
when I use database pilot of jbuilder8 to setup a datasource..
I got an error Error " connecting to database: java.lang.NoClassDefFoundError: weblogic/version "
what should I do now ?..

Java.lang.ClassNotFoundException: weblogic/jdbc/mssqlserver4/Driver

Hello,
I am moving my database from Sybase to SQL Server. I have a program that ran fine with JConnect driver (Sybase) on both unix and windows. But now when I try to use the weblogic driver to connect to SQL Server the program fails. I am 100% positive that the weblogic drive is in the classpath. Whether the weblogic drive is in the classpath or not I get the same error:
Unexpected error:java.lang.ClassNotFoundException: weblogic/jdbc/mssqlserver4/Driver
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:124)
at com.trilogy.tools.core.DBUtil.loadDriver(DBUtil.java:16)
at com.trilogy.loader.core.LoadInitUtil.<init>(Compiled Code)
at com.trilogy.loader.mass.MassInitUtil.<init>(MassInitUtil.java:15)
at com.trilogy.loader.mass.Loader2CLI.execute(Compiled Code)
at com.trilogy.tools.core.CLIBase.execute(CLIBase.java:45)
at com.trilogy.loader.mass.Loader2CLI.main(Loader2CLI.java:805)
java.lang.NullPointerException
at com.trilogy.loader.mass.Loader2CLI.execute(Compiled Code)
at com.trilogy.tools.core.CLIBase.execute(CLIBase.java:45)
at com.trilogy.loader.mass.Loader2CLI.main(Loader2CLI.java:805)
Pease help me fix this problem. I am not sure why the weblogic driver is not working. Thanks.

The error message says it can't find a class named "weblogic.jdbc.mssqlserver4.Driver". That looks rather odd to me.
Are you sure that you defined the connection information correctly in the configuration file?

Which jar Conains weblogic.jdbc.extensions.WLConnection in Weblogic 10.3

Hi,
Thank you in advance for your help.
I am upgrading my application from weblogic 9.2 to weblogic 10.3. My app uses weblogic.jdbc.extensions.WLConnection. This class is in weblogic.jar of weblogic 9.2. Which jar contains this class in weblogic 10.3?
Please advise,
Best Regards.
John

It's in the com.bea.core.datasource_1.4.0.0.jar in modules directory.

Can anyone tell me which jar contain weblogic.jws.WLJmsTransport class

Hi All,
Can anyone tell me which jar contain weblogic.jws.WLJmsTransport class
Thanks in advance?

Hi,
You can find that in the "*weblogic.jar*", "*wls-api.jar*" and "*wseeclient.jar*" which can be found in the below directory
Path:
wlserver_10.3/server/lib/
Also you can have a look at the below link which shows you how to find any CLASS present inside your file system.
Topic: Finding Classes using JAR SCANNER
http://middlewaremagic.com/weblogic/?page_id=241#comment-3621
Regards,
Ravish Mody

Weblogic Eclipselink Sequence Table Connection Pool Sequence Separate transaction while JTA on main transaction

Hi,
And thanks in advance for your support.
In weblogic 12, managing to get the eclipse link connection sequencing mechanism when one uses Tables for sequencing entity ids seems to be complicated.
QUICK REFERENCE:
http://www.eclipse.org/eclipselink/api/2.5/org/eclipse/persistence/config/PersistenceUnitProperties.html
The concept:
While having EJB, MDBs etc... run on a JEE container, be it glassfish or weblogic, it should be possible to have the main thread transaction be managed as part of JTA global transactions by the contianer.
Namely, pumping messages to JMS queues, persisting entities etc.
Meanwhile, it should be also possible to as the transaction is on going write and update entity ids from sequencing tables.
For this very purpose, eclipse link provides persistence.xml properties, such as the now deprecated eclipselink.jdbc.sequence-connection-pool" value="true", to fullfill this very purpose.
This option greatly avoids dead longs, by allowing eclipse link to fetch a non JTA managed connection, pseudo "two phase locking read table update table" go to the datbase and fetch a new sequence.
The same mechnism under JTA is a disaster. A transaction that creates ten different entities, might do ten reads and updates on this table, while mean while a competing transaction might be trying to do the same. It is guaranteed dead lock with minimal stress on the environment.
Under glassfish, for example, tagging a persistence.xml with :
<persistence-unit name="MY_PU" transaction-type="JTA">
        <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
        <jta-data-source>jdbc/DERBY_DS</jta-data-source>
        <non-jta-data-source>jdbc/DERBY_DS</non-jta-data-source>
        <properties>
            <property name="eclipselink.jdbc.sequence-connection-pool" value="true" />
        </properties>
</peristence-unit>
does miracles, when entities are using TABLE sequencing.
Under weblogic, say you are using the Derby embedded XA driver with two phase commit, deploying the applicaiton immediately leads to:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.3.v20120629-r11760): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Cannot call commit when using distributed transactions
Error Code: 0
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:324)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicCommitTransaction(DatabaseAccessor.java:426)
at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.commitTransaction(DatasourceAccessor.java:389)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.commitTransaction(DatabaseAccessor.java:409)
at org.eclipse.persistence.internal.sequencing.SequencingManager$Preallocation_Transaction_Accessor_State.getNextValue(SequencingManager.java:579)
at org.eclipse.persistence.internal.sequencing.SequencingManager.getNextValue(SequencingManager.java:1067)
at org.eclipse.persistence.internal.sequencing.ClientSessionSequencing.getNextValue(ClientSessionSequencing.java:70)
at org.eclipse.persi
While weblogic is right that their might be a distributed transaction ongoing, it is mistaken in the fact tha tthe connection requested by eclipse link for generating the ID should be part of the global transaciton.
Eclipse link provides other ways to attempt to configure the sequencing mechanism, by sating for example a non-jta transaction.
I have attempted also using these properties both withe original data DERBY_DS that uses the XA driver, and later with a new data source i created on purpose to try to work around the sequencing contengy.
For example:

            
This new DERBY_SEQUENCING_NON_JTA is explicitly configured to use a NON_XA driver with global transactions flag set to disabled.
Regardless, the only thing I get out of this is that the application is deployed and super fast, up to the point where i stress it with a system test that introduces some degreee of concurrency, and then I see the dead locks on the sequencing table.
Meaning that the ongoing transactions are holding tight to their locks on the sequencing table.
Is this a known issue?
Is there something I am missing in the configuration?
It really should not be this diffcult to get eclipse link to run its sequence reads and updates on a separate transaction of the main JTA transaction, but so far looks impossible.
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.3.v20120629-r11760): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested
Error Code: 30000
Call: UPDATE ID_GEN SET SEQ_VALUE = SEQ_VALUE + ? WHERE SEQ_NAME = ?
bind => [2 parameters bound]
Query: DataModifyQuery(name="MyEntity_Gen" sql="UPDATE ID_GEN SET SEQ_VALUE = SEQ_VALUE + ? WHERE SEQ_NAME = ?")
Many thanks for your help.

Are you calling the cmp bean code and your new Sql code under a same transactional context?
The following setting
"rollbackLocalTxUponConnClose=true"
will make the connectionpool to call the rollback method on the connection object before keeping it back in the pool. In your sql code if you are calling connection.close() , then your entire transaction will be rolled back.
CMP bean requires a transactional connection while communicating with the database.
What is the sequence of code execution?
I think you must be calling sql code first and then cmp bean code later.
You may avoid this problem in this way. This is my guess based on my understanding on your code execution.
1. set rollbackLocalTxUponConnClose=false
Execute the sql code and cmp code in a single transaction (in a single session bean method with cmt or bmt transaction ). Specify tx.rollback if it is bmt. or call tx.setRollbackOnly() if it is a cmt. In this way you will have control to roll back the transactions.
Hope this helps you.
bmt-> bean managed transaction
cmt-> container managed transaction.
Regards,
Seshi.

SUN IDM 7.1 - Weblogic 8.1 SP6 Connection Pooling error

Hi,
We have a POC environment and IDM is being moved onto the weblogic server.
I need to have the IDM use the weblogic connection pooling, however i am getting the following issue:
Oracle is 10g and wl oracle drivver is oracle.jdbc.driver.OracleDriver
/lh setRepo -v -tOracle -iweblogic.jndi.WLInitialContextFactory -fCIIDMDS -ut3://localhost:29003/" -U"weblogic" -P"password"
Defaulting administrator to 'configurator'.
Defaulting credentials to 'configurator'.
DB Server @ jdbc:hsqldb:hsql://127.0.0.1:53111/idm
Checking 'OracleDataStore:CIIDMDS'...
==> java.sql.SQLException: Internal error: Invalid NLS Conversion ratio
com.waveset.util.IOException:
==> java.sql.SQLException: Internal error: Invalid NLS Conversion ratio
at com.waveset.repository.RelationalDataStore.checkDatabaseMetaData(RelationalDataStore.java:4155)
at com.waveset.repository.RelationalDataStore.init(RelationalDataStore.java:3788)
at com.waveset.install.RepoMan.check(RepoMan.java:1194)
at com.waveset.install.RepoMan.setRepo(RepoMan.java:1082)
at com.waveset.install.RepoMan.main(RepoMan.java:1314)
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 com.waveset.util.CommandProcess.invokeMain(CommandProcess.java:212)
at com.waveset.util.CommandProcess.launch(CommandProcess.java:162)
at com.waveset.util.CommandProcess.run(CommandProcess.java:300)
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 com.waveset.util.Command.main(Command.java:117)
Caused by: java.sql.SQLException: Internal error: Invalid NLS Conversion ratio
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:164)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection_814_WLStub.getMetaData(Unknown Source)
at weblogic.jdbc.rmi.SerialConnection.getMetaData(SerialConnection.java:312)
at com.waveset.util.PooledConnection.getMetaData(PooledConnection.java:213)
at com.waveset.repository.RelationalDataStore.checkDatabaseMetaData(RelationalDataStore.java:3940)
... 16 more
Caused by: java.sql.SQLException: Internal error: Invalid NLS Conversion ratio
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227)
at oracle.jdbc.driver.PhysicalConnection.getMaxCharSize(PhysicalConnection.java:4485)
at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection.getMaxCharSize(Unknown Source)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection.getMaxCharSize(Unknown Source)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
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:415)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Wrapped exception:
java.sql.SQLException: Internal error: Invalid NLS Conversion ratio
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:164)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection_814_WLStub.getMetaData(Unknown Source)
at weblogic.jdbc.rmi.SerialConnection.getMetaData(SerialConnection.java:312)
at com.waveset.util.PooledConnection.getMetaData(PooledConnection.java:213)
at com.waveset.repository.RelationalDataStore.checkDatabaseMetaData(RelationalDataStore.java:3940)
at com.waveset.repository.RelationalDataStore.init(RelationalDataStore.java:3788)
at com.waveset.install.RepoMan.check(RepoMan.java:1194)
at com.waveset.install.RepoMan.setRepo(RepoMan.java:1082)
at com.waveset.install.RepoMan.main(RepoMan.java:1314)
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 com.waveset.util.CommandProcess.invokeMain(CommandProcess.java:212)
at com.waveset.util.CommandProcess.launch(CommandProcess.java:162)
at com.waveset.util.CommandProcess.run(CommandProcess.java:300)
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 com.waveset.util.Command.main(Command.java:117)
Caused by: java.sql.SQLException: Internal error: Invalid NLS Conversion ratio
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227)
at oracle.jdbc.driver.PhysicalConnection.getMaxCharSize(PhysicalConnection.java:4485)
at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection.getMaxCharSize(Unknown Source)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection.getMaxCharSize(Unknown Source)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
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:415)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Hi,
Are you getting any other Exception when performing basic operations other than ones you had mentioned like search,delete,report etc..?
What was your JDK version earlier and now?
Have you re-build the custom java classes if any?
Have you re-build the custom objects like Forms,WF,TDs etc..?
Regards,
Ferose

What's the difference between using a connection pool and a datasource

Howdy. I figure this is a newbie question, but I can't seem to find an
answer.
In the docs at bea, the datasource docs say
"DataSource objects provide a way for JDBC clients to obtain a DBMS
connection. A DataSource is an interface between the client program and the
connection pool. Each data source requires a separate DataSource object,
which may be implemented as a DataSource class that supports either
connection pooling or distributed transactions."
In there it says the datasource uses the connection pool, but other than
that, what is the difference between a connection pool and a datasource?

Thanks for the info. I think it makes some sense. But it's a bit greek.
I'm sure it'll make more sense the more I work with it. Thanks.
"Chuck Nelson" <[email protected]> wrote in message
news:3dcac1f5$[email protected]..
>
Peter,
Here is a more formal definition of a DataSource from the Sun site
"A factory for connections to the physical data source that thisDataSource object
represents. An alternative to the DriverManager facility, a DataSourceobject
is the preferred means of getting a connection. An object that implementsthe
DataSource interface will typically be registered with a naming servicebased
on the JavaTM Naming and Directory (JNDI) API.
The DataSource interface is implemented by a driver vendor. There arethree types
of implementations:
Basic implementation -- produces a standard Connection object
Connection pooling implementation -- produces a Connection object thatwill automatically
participate in connection pooling. This implementation works with amiddle-tier
connection pooling manager.
Distributed transaction implementation -- produces a Connection objectthat may
be used for distributed transactions and almost always participates inconnection
pooling. This implementation works with a middle-tier transaction managerand
almost always with a connection pooling manager.
Does that help clarify the distinction?
Chuck Nelson
DRE
BEA Technical Support

XI adapter polling issue & JDBC / DB2 driver connection timeout properties

Hello Group,
We have a long running issue with our XI 7.0 system running on iseries. (V5R3) The issue occuring is that our XI adapters stop polling and the only resolution is to restart the J2EE engine or to resart the adapter framework services.
We have had several OSS messages open on this subject for over a year and are going round in circles with the a number of different SAP consultants.
The one topic that we keep coming back to is that we are being asked to set DB2 driver connection timeout properties. We are using the toolbox driver and have upated to the latest JTopen driver, but have not managed to find any inofrmation on how to set the timeout parameter. Does anyone know where the timeout parameter set?
Has anyone experienced polling issue like this before and how did you resolve?
SAP referred to the SAP note 1078420 - XI/PI JDBC Adapter: Setting JDBC driver properties for DB which is for Oracle, but this will give an idea of what timeout parameters SAP are asking about.
Extract of the note is below:-
Symptom
This note gives an option to set JDBC driver properties while acquiring a DB connection. When connecting to DB using JDBC adapter there are instances
where DB connection take a long time to establish connection. Some times call made to Driver will hang permanently. Setting driver properties would resolve this problem.
More Terms
Connection timeout, time out, query timeout
Cause and Prerequisites
Solution
In the advanced mode table section of sender channel and receiver channel configurations, we can set driver properties for each DB connection. Any
such property would have to contain prefix 'driver:'(with out quotes) For example, for Oracle Database JDBC thin driver 10.2.0.3 version, the
property oracle.jdbc.ReadTimeout helps to set read timeout while reading from the socket. Also for setting login time out in Oracle, we use
oracle.net.CONNECT_TIMEOUT. To set these two properties use as follows:
driver:oracle.jdbc.ReadTimeout 1000
driver:oracle.net.CONNECT_TIMEOUT 1000
(The TimeOut Driver properties like ReadTimeout and CONNECT_TIMEOUT are in milliseconds)
Refer to your DB documentation/ JDBC driver documentation on this. Please note that properties can vary from each driver version. For instance, some
of properties of Oracle JDBC thin Driver 10.2.0.3 properties may not be present in older version drivers. Please contact DB vendor for the complete
list of driver properties. In addition to above, we also provide another parameter for query time out.
sqlquerytimeout (prefix 'driver:' is not required) is the parameter that is to be used for SQL query time out. This is case-sensitive and should be
configured as positive integer value in seconds(greater than 0).
Any help on this would be much appreciated.
With regards,
Steven

Hello,
I am not talking about the XI timeouts. But the timeouts which can be used to get the connection timeouts for DB2/AS400 databases.
So please provide that information.
THanks,
soorya

Jdbc-odbc-bridge connection pool

I got a problem with odbc connection pool in my Sun App Server 7.
When i try to connect to the odbc database (msaccess or conzept16), i got a SQLException : com.sun.enterprise.repository.J2EEResourceException
java.lang.NoSuchMethodException: setdatabaseName .....
It seems that i cant set any propertys like url, user or password. The exception throws every time NoSuchMethodException: setURL or ... NoSuchMethodException: setUser
I tried this with pointbase database and pointbase drivers and there was no problem. Also when i connect direct from jsp page to the odbc database without connection pool it works.
How can i set a propper connection pool with the jdbc-odbc-bridge? Please Help. There is no jdbc driver for that database available.
Is that right using sun.jdbc.odbc.JdbcOdbcDriver for that?
here my server.xml
<resources>
<jdbc-resource enabled="true" pool-name="access-pool" jndi-name="jdbc/AccessDB"/>
<jdbc-connection-pool steady-pool-size="2" max-pool-size="6" max-wait-time-in-millis="60000" pool-resize-quantity="2" idle-timeout-in-seconds="300" is-isolation-level-guaranteed="false" is-connection-validation-required="false" connection-validation-method="auto-commit" fail-all-connections="false" datasource-classname="sun.jdbc.odbc.JdbcOdbcDriver" name="access-pool" validation-table-name="TAB_NAME">
<property value="jdbc:odbc:testdb" name="databaseName"/>
</jdbc-connection-pool>
</resources>

AFAIK the bridge driver does not support multipleopen
connections (which is what connection pooling
requires).Wrong.
It might be the case that the bridge AND ms access
does not support that but I seriously doubt that as
well.
Yesterday I didn't want to test this. Today I did.
So I can state that it is completely wrong.
There might be some other reason preventing the usage in a pool, but it isn't the number of open connections.

WebLogic 6.1 losing connection pools and deployments on restart

Hi,
Has anyone else seen a problem where it appears that processing of
config.xml is incomplete, without any error message? For example, a
connection pool that is deployed fine through the console, shows as
undeployed (available) when the server is restarted, regardless of how the
server is shut down.
Most recently, this happened with a connection pool and tx data source I've
been using for weeks, when I added a RDBMSRealm going to the same database.
The EJB deployment that needs the tx data source fails on startup, but if I
redeploy the connection pool and tx data source through the console and then
deploy the EJBs everything works. Until I restart the server, when the
problem recurs.
If I go back to my backed up config.xml, without the RDBMSRealm, everything
works fine at startup.
I see no error message in any log file: it's as though config.xml entries
are being ignored.
I attach my config.xml file. The multiple targets are the result of
redeploying through the console: editing them out does't fix the problem.
Regards,
Rod Johnson
[config.xml]

hi.
Please post this question in weblogic.developer.interest.jdbc.
Thanks,
Michael
Rod Johnson wrote:
Hi,
Has anyone else seen a problem where it appears that processing of
config.xml is incomplete, without any error message? For example, a
connection pool that is deployed fine through the console, shows as
undeployed (available) when the server is restarted, regardless of how the
server is shut down.
Most recently, this happened with a connection pool and tx data source I've
been using for weeks, when I added a RDBMSRealm going to the same database.
The EJB deployment that needs the tx data source fails on startup, but if I
redeploy the connection pool and tx data source through the console and then
deploy the EJBs everything works. Until I restart the server, when the
problem recurs.
If I go back to my backed up config.xml, without the RDBMSRealm, everything
works fine at startup.
I see no error message in any log file: it's as though config.xml entries
are being ignored.
I attach my config.xml file. The multiple targets are the result of
redeploying through the console: editing them out does't fix the problem.
Regards,
Rod Johnson
<?xml version="1.0" encoding="UTF-8"?>

<Domain Name="rj">
<Log FileName="config/rj/logs/wl-domain.log" Name="rj"/>
<Application Deployed="true" Name="ticket-app" Path=".\config\rj\applications\ticket-app">
<EJBComponent Name="ticket-ejb/ticket-ejb"
Targets="rj,rj,rj,rj,rj,rj" URI="ticket-ejb/ticket-ejb.jar"/>
<WebAppComponent Name="ticket-war" Targets="rj,rj" URI="ticket-war"/>
</Application>
<Security GuestDisabled="false" Name="rj"
PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm"/>
<CustomRealm
ConfigurationData="server.host=ldapserver.example.com;membership.scope.depth=1;microsoft.membership.scope=sub;membership.filter=(|(&(memberobject=%M)(objectclass=memberof))(&(groupobject=%M)(objectclass=groupmemberof)));group.dn=ou=Groups, o=ExampleMembershipDir;group.filter=(&(cn=%g)(objectclass=mgroup));server.principal=cn=Administrator, ou=Members, o=ExampleMembershipDir;user.dn=ou=Members, o=ExampleMembershipDir;user.filter=(&(cn=%u)(objectclass=member))"
Name="defaultLDAPRealmForMicrosoftSiteServer"
Notes="This is provided as an example. Before enabling this Realm, you must edit the configuration parameters as appropriate for your environment."
Password="{3DES}aTzgEUdjzAqaEDs0MC2lBQ==" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<JDBCTxDataSource JNDIName="ticket-ds" Name="ticket-ds"
PoolName="ticket-pool" Targets="rj,rj,rj,rj"/>
<Application Deployed="true" Name="DefaultWebApp" Path=".\config\rj\applications">
<WebAppComponent Name="DefaultWebApp" Targets="rj" URI="DefaultWebApp"/>
</Application>
<PasswordPolicy Name="wl_default_password_policy"/>
<JTA Name="rj"/>
<Application Deployed="true" Name="certificate" Path=".\config\rj\applications">
<WebAppComponent Name="certificate" Targets="rj" URI="certificate.war"/>
</Application>
<Realm CachingRealm="ticketCaching Realm"
FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
<CachingRealm BasicRealm="ticketRDBMS Realm" Name="ticketCaching Realm"/>
<JDBCConnectionPool DriverName="COM.cloudscape.core.RmiJdbcDriver"
InitialCapacity="3" MaxCapacity="15" Name="ticket-pool"
Properties="user=portal;password=portal" Targets="rj,rj,rj,rj" URL="jdbc:cloudscape:rmi:d:\\book\\db\\csdb"/>
<DomainLogFilter Name="MyDomain Log Filter" SeverityLevel="64" SubsystemNames="JTA,EJB"/>
<Server DomainLogFilter="MyDomain Log Filter" ListenPort="7001"
Name="rj" NativeIOEnabled="true" StdoutDebugEnabled="true"
StdoutSeverityLevel="64" TransactionLogFilePrefix="config/rj/logs/">
<ExecuteQueue Name="default" ThreadCount="15"/>
<KernelDebug Name="rj"/>
<Log FileName="config/rj/logs/weblogic.log" Name="rj"/>
<ServerStart Name="rj"/>
<ServerDebug Name="rj"/>
<WebServer DefaultWebApp="DefaultWebApp"
LogFileName="./config/rj/logs/access.log"
LoggingEnabled="true" Name="rj"/>
<SSL Enabled="true" ListenPort="7002" Name="rj"
ServerCertificateChainFileName="config/rj/ca.pem"
ServerCertificateFileName="config/rj/democert.pem" ServerKeyFileName="config/rj/demokey.pem"/>
</Server>
<SNMPAgent Name="rj"/>
<ApplicationManager Name="rj"/>
<CustomRealm
ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));user.dn=ou=people, dc=example, dc=com;server.principal=cn=Manager, dc=example, dc=com;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;group.dn=ou=groups, dc=example, c=com"
Name="defaultLDAPRealmForOpenLDAPDirectoryServices"
Notes="This is provided as an example. Before enabling this Realm, you must edit the configuration parameters as appropriate for your environment."
Password="{3DES}aTzgEUdjzAqaEDs0MC2lBQ==" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<CustomRealm
ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));user.dn=ou=people, o=beasys.com;server.principal=uid=admin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;group.dn=ou=groups, o=beasys.com"
Name="defaultLDAPRealmForNetscapeDirectoryServer"
Notes="This is provided as an example. Before enabling this Realm, you must edit the configuration parameters as appropriate for your environment."
Password="{3DES}aTzgEUdjzAqaEDs0MC2lBQ==" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<FileRealm Name="wl_default_file_realm"/>
<CustomRealm
ConfigurationData="user.filter=(&(cn=%u)(objectclass=person));user.dn=ou=people, o=example.com;server.principal=cn=admin, o=example.com;membership.filter=(&(member=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;server.ssl=true;group.dn=ou=groups, o=example.com"
Name="defaultLDAPRealmForNovellDirectoryServices"
Notes="This is provided as an example. Before enabling this Realm, you must edit the configuration parameters as appropriate for your environment."
Password="{3DES}aTzgEUdjzAqaEDs0MC2lBQ==" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<RDBMSRealm DatabaseDriver="COM.cloudscape.core.RmiJdbcDriver"
DatabaseURL="jdbc:cloudscape:rmi:d:\\book\\db\\csdb"
DatabaseUserName="portal" Name="ticketRDBMS Realm" SchemaProperties="getGroupMembers=SELECT GM_GROUP, GM_MEMBER from groupmembers WHERE GM_GROUP = ?;deleteGroup2=DELETE FROM aclentries WHERE A_PRINCIPAL = ?;deleteGroup1=DELETE FROM groupmembers WHERE GM_GROUP = ?;addGroupMember=INSERT INTO groupmembers VALUES ( ? , ? );getUser=SELECT EMAIL, PASSWORD FROM LOGINS WHERE EMAIL = ?;getPermission=SELECT DISTINCT A_PERMISSION FROM aclentries WHERE A_PERMISSION = ?;deleteUser3=DELETE FROM aclentries WHERE A_PRINCIPAL = ?;getGroupNewStatement=true;deleteUser2=DELETE FROM groupmembers WHERE GM_MEMBER = ?;deleteUser1=DELETE FROM LOGINS WHERE EMAIL = ?;getAcls=SELECT A_NAME, A_PRINCIPAL, A_PERMISSION FROM aclentries ORDER BY A_NAME, A_PRINCIPAL;getUsers=SELECT EMAIL, PASSWORD FROM LOGINS;getGroups=SELECT GM_GROUP, GM_MEMBER FROM groupmembers;getPermissions=SELECT DISTINCT A_PERMISSION FROM aclentries;getAclEntries=SELECT A_NAME, A_PRINCIPAL, A_PERMISSION FROM aclentries WHERE A_NAME = ?
ORDER BY A_PRINCIPAL;newUser=INSERT INTO LOGINS VALUES ( ? , ? );removeGroupMember=DELETE FROM groupmembers WHERE GM_GROUP = ? AND GM_MEMBER = ?"/>
</Domain>--
Developer Relations Engineer
BEA Support

Jdbc:odbc driver connection issues

I need to use the jdbc:odbc driver to access a non-oracle db from a jsp. I am sure my dsn is fine as I can use a non JSP java app to connect to the odbc db. I have loaded the sun.jdbc.odbc classes in the schema I am working in as it is not loaded by default in 9.2.0.7 currently I am on a windows system. I have found the following:
public static void doTest()throws Exception{
// load the local Oracle Driver
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
connLocalOracle = new OracleDriver().defaultConnection();
// load the odbc driver
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
if I exit at this point the jsp does not through an exception
however if I include the line:
connODBC = DriverManager.getConnection(odbcURL,"XX","XX");
I get the error:
SQL> execute do_jdbc_odbc_test;
BEGIN do_jdbc_odbc_test; END;
ERROR at line 1:
ORA-29532: Java call terminated by uncaught Java exception:
java.lang.UnsatisfiedLinkError: sun.jdbc.odbc.JdbcOdbc.allocConnect
ORA-06512: at "TU1.DO_JDBC_ODBC_TEST", line 0
ORA-06512: at line 1
So I am assuming I am loading the driver but the driver is not talking to the odbc configuration in windows.
What permissions would I need to give to the user to allow this connection to occur?
How can I find out if this is indeed the case?
If not how can I make this connection happen using ODBC?

If by jsp you mean Java Stored Procedure, the hybrid JDbc-ODBC stack won't work. You can connect to non-Oracle RDBMS from within Java in the database by using a pure Java JDBC driver of the target RDBM. Fwiw, a complete example connecting to SQl Server from with JavaDB is described in my upcoming book. (See http://db360.blogspot.com/)
Kuassi

Which jar is weblogic.jdbc.sqlserver.SQLServerDriver located?

Hi,
I am just writing a test program in Eclipse and tried to connect to MS SQL Server. I added weblogic.jar to project lib. But it complaints ClassNotFound: weblogic.jdbc.sqlserver.SQLServerDriver. where is it?
Found out I have to have wlbase.jar wlclient.jar wlutil.jar wlsqlserver.jar.
Edited by Holy at 01/29/2007 12:05 PM

test test wrote:
Hi,
I am just writing a test program in Eclipse and tried to connect to MS SQL Server. I added weblogic.jar to project lib. But it complaints ClassNotFound: weblogic.jdbc.sqlserver.SQLServerDriver. where is it?
Found out I have to have wlbase.jar wlclient.jar wlutil.jar wlsqlserver.jar.You need wlbase, wlutil, wlsqlserver, and weblogic jars.
Joe

JDBC thin driver connection problems using cybersafe authentication

Hi
i am trying to use jdbc thin driver to connect to oracle 8.1.7 DB using ASO and cybersafe authentication.
Question:
Does the oracle jdbc thin driver in 8.1.7.0.0 support third-party authentication features supported by Oracle Advanced Security--such
as those provided by RADIUS, Kerberos, or SecurID
i am getting the following error.
Exception in thread "main" java.sql.SQLException: invalid arguments in call
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java)
at oracle.jdbc.dbaccess.DBError.check_error(DBError.java)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.ja
va)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:146)
at ASOJdbc.main(ASOJdbc.java:43)
Following is the program i am trying.
public class ASOJdbc {
     public static void main(String args[]) throws SQLException {
          String url = "jdbc:oracle:thin:@son1129:1521:sonias";
          Connection con;
          String query = "select EMPNO, ENAME from EMP";
          Statement stmt;
          // ASO Stuff
               Properties props = new Properties();
               try {
               props.put("oracle.net.authentication_services", "CYBERSAFE");
               props.put("oracle.net.authentication_gssapi_service", "oracle/[email protected]");
               props.put("oracle.net.encryption_types_client", "DES");
               props.put("oracle.net.encryption_types_server", "DES");
               props.put("oracle.net.crypto_seed", "4fhXXXX");
               } catch (Exception e) { e.printStackTrace();
               DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
               // ASO
               con = DriverManager.getConnection(url, props);
               stmt = con.createStatement();
               ResultSet rs = stmt.executeQuery(query);
               stmt.close();
               con.close();
jdk version: jdk 1.3.1
Oracle jdbc driver information, which i obtained as per Note 94091.1
=============
Database Product Name is Oracle
Database Product Version is Oracle8i Enterprise Edition Release 8.1.7.1.1 - Production With the Partitioning option
JServer Release 8.1.7.1.1 - Production
JDBC Driver Name is Oracle JDBC driver
JDBC Driver Version is 8.1.7.0.0
JDBC Driver Major Version is 8
JDBC Driver Minor Version is 1

1. What JDBC Thin client Driver are you using? (version) If you don't know, open up the Manifest.
2. the JDBC/OCI driver is a thick driver. It uses the oracle client, and therefore should read the tnsnames.ora
3. You have yet to give us any ORA- errors, which would help immensely in troubleshooting.

What jar contains weblogic.jdbc.pool.Driver connection pool class?

Similar Messages

Maybe you are looking for