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

Similar Messages

  • Can I create connection pool by oracle oci driver?

    Can I create connection pool by oracle oci driver?My weblogic's version is 6.1 sp2 and oracle is 9.0.1.2.
    I have some trouble with connection pool created by weblogic jDriver.
    I try to read Timestamp from table and I always get the exception.It told me that ORA-00932: inconsistent datatypes.
    So I created another pool by oracle thin driver and everything was right.Then I created other pool by oracle oci driver,but something were wrong. 'Could not create pool connection. The DBMS driver exception was:java.sql.SQLException: ORA-06401: NETCMN:Invalid driver designator'
    The oci pool's parameters are below lines.
    url: jdbc:oracle:oci:@COCO
    Driver Classname: oracle.jdbc.driver.OracleDriver
    Properties: user=scott;password=tiger;protocol=oci
    If I get connection directly,don't use connection pool,I can get right connection.But why didn't I create pool by oci driver?Maybe weblogic7 or weblogic8 will work good?

    Venkat Amirineni wrote:
    Hi Joe,
    I am also trying to create a connection pool using Oracle Oci XA. Weblogic
    type 2 oci threads hanging on native calls and suggested to go for thin drivers.
    But we want to try with Oracle Oci drivers.. Can you please tell us how to
    create a conn pool using Oracle Oci.. Just the driverclass and url is enough
    or need any classpath settings etc..
    Thanks in advance for your quick reply.Hi. As far as driver properties, just use what Oracle says to. Any pool properties
    that we recommend for XA would still apply. Note that Oracle themselves recommends
    the thin driver over their OCI one:
    http://download-west.oracle.com/docs/cd/B14117_01/java.101/b10979.pdf
    Joe

  • Difference between using app server connection pooling and using the driver

    Hi all,
    How to get connection pooling with out application server and tomcat also?
    What is the difference between using app server connection pooling and using the driver supported connection pooling?
    Regards,
    Murali

    maybe the performance of App server pool is better than the JDBC pool,
    for you don't know wether the implementation of the JDBC interface is good or bad.

  • Problem JDBC Connection using OCI Driver on Weblogic Portal on Linux

    Hi Team,
    I want a JDBC connection using OCI Driver in Weblogic Portal 8.1 sp4 on Linux. When I had tested using JDBC connection using Plain Java Code it is working. Also when I create the OCI Connection Weblogic Connection Pool it is working.
    But My Requirement is to create the connection using Java Code in Portal Application
    But When I create OCI connection in the code it is throwing NO SUITABLE DRIVER Found.
    ---------- Code in Plain Java Code ------------ Same code is used in Weblogic Portal Application --------------------------------
         public static void main(String[] args) throws Exception{
              Class.forName("oracle.jdbc.driver.OracleDriver");
              DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
              String url="jdbc:oracle:oci8:@TESTDB";
              Properties props = new Properties();
         props.put("user","scott");
         props.put("password","tiger");
              conn=DriverManager.getConnection(url,props);
    When I am using the same code in Weblogic Portal and Deployed on Weblogic Portal Server 8.1 SP4 it is throwing following error.
    -------------- Exception on Server Log --------------------
    java.sql.SQLException: No suitable driver
    at java.sql.DriverManager.getConnection(Ljava.lang.String;Ljava.util.Properties;Ljava.lang.ClassLoader;)Ljava.sql.Connection;(Unknown Source)
    at java.sql.DriverManager.getConnection(Ljava.lang.String;Ljava.util.Properties;)Ljava.sql.Connection;(Unknown Source)
    My Environment is
    LINUX
    Weblogic 8.1 SP4
    Oracle 9i Client on Same Machine
    Oracle 10g Server on Different Machine
    My Environment Variables on the Linux Server also set properly as following
    PATH=/apps/pmaaum/ant/apache-ant-1.6.5/bin:.:/apps/beahomedev/jdk142_05/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/apps/oracle/ora9i/product/9.2.0/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/apps/oracle/ora9i/bin
    LD_LIBRARY_PATH=/usr/lib:/apps/oracle/ora9i/product/9.2.0/lib:/apps/oracle/ora9i/product/9.2.0/lib32:/apps/oracle/ora9i/product/9.2.0/rdbms/lib:/usr/openwin/lib:/apps/oracle/ora9i/product/9.2.0/jdbc/lib
    JAVA_HOME=/apps/beahomedev/jdk142_05
    JDBC_LIB=/apps/oracle/ora9i/product/9.2.0/jdbc/lib
    CLASSPATH=:.:/apps/beahomedev/jdk142_05/lib/rt.jar:/apps/oracle/ora9i/product/9.2.0/jdbc/lib/classes12.jar
    Please help me, Let me know if you required anything.
    Thanks in Advance
    Vishnu
    Edited by: vishnuk on Oct 23, 2009 4:07 AM
    Edited by: vishnuk on Oct 23, 2009 4:10 AM

    Hi Vishnu
    Looks like a classloader issue. BEA class loader is very tricky. Any jar added manually in classpath, will end up loading only those classes. Any imports that we have in any of those classes do not get loaded. Anyhow, coming to your point, add classes12.jar inside your portal web project Web-Inf/lib folder and see if that helps. Usually thats where we put all the JARs for 8.1 SPxx applications. If this still breaks, then remove the jar from web-inf/lib folder and add under your portal app App-Inf/lib folder. First try with app-inf/lib folder having this jar. If not then with web-inf/lib. Basically web-inf is specific to that web app only. If you have a different app having this jdbc code, then put under app-inf/lib folder. Make sure that you remove the classes12.jar that you added in classpath either in env variable or in setdomainenv.cmd file.
    When weblogic uses native OCI Drivers, it refers to jars at this location: ....\beawlp814\weblogic81\server\ext\jdbc\oracle\10g or 9g. Try using one of these jars and see if that works. Most of the times I used these jars only for oracle specific native drivers.
    Word of caution. Try to use Connection Pool and a DataSource created in weblogic console for your jdbc code. This Datasource can still use the Oracle drivers that you want (instead of BEA Weblogic wrapper oci drivers) located in above location. Use JNDI Lookup and get Datasource and then connection. This is more recommended approach with many advantages then using DriverManager approach..
    Goud

  • Oracle database Connectivity using OCI driver

    I am getting the error only when ever I am using oci driver
    oracle.url=jdbc:oracle:oci:@(description=(address=(host=url.name.com)(protocol=tcp)(port=1521))(connect_data=(sid=user)))
    04:52:55,093 ERROR [STDERR] java.sql.SQLException: ???S???Y??x??
    04:52:55,094 ERROR [STDERR] at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
    04:52:55,094 ERROR [STDERR] at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:131)
    04:52:55,095 ERROR [STDERR] at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:204)
    04:52:55,095 ERROR [STDERR] at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:650)
    04:52:55,095 ERROR [STDERR] at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:338)
    04:52:55,095 ERROR [STDERR] at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:508)
    04:52:55,095 ERROR [STDERR] at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:133)
    04:52:55,096 ERROR [STDERR] at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:53)
    04:52:55,096 ERROR [STDERR] at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:510)
    04:52:55,096 ERROR [STDERR] at java.sql.DriverManager.getConnection(DriverManager.java:582)
    04:52:55,096 ERROR [STDERR] at java.sql.DriverManager.getConnection(DriverManager.java:185)
    04:52:55,097 ERROR [STDERR] at org.apache.jsp.index_jsp._jspService(index_jsp.java:68)
    04:52:55,097 ERROR [STDERR] at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    04:52:55,097 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    04:52:55,097 ERROR [STDERR] at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
    04:52:55,097 ERROR [STDERR] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
    04:52:55,098 ERROR [STDERR] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
    04:52:55,098 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    04:52:55,098 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324)
    04:52:55,098 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
    04:52:55,099 ERROR [STDERR] at org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.doFilter(FilterDispatcher.java:63)
    04:52:55,099 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274)
    04:52:55,099 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
    04:52:55,099 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
    04:52:55,099 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    04:52:55,100 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181)
    04:52:55,100 ERROR [STDERR] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285)
    04:52:55,100 ERROR [STDERR] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261)
    04:52:55,100 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88)
    04:52:55,101 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100)
    04:52:55,101 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    04:52:55,101 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    04:52:55,101 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
    04:52:55,101 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    04:52:55,102 ERROR [STDERR] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53)
    04:52:55,102 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
    04:52:55,102 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
    04:52:55,102 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
    04:52:55,102 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
    04:52:55,103 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619)
    04:52:55,105 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[Test].[jsp]] Servlet.service() for servlet jsp threw exception: java.sql.SQLException: ???S???Y??x??
    at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
    at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:131) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:204) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
    at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:650) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
    at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:338) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:508) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
    at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:133) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
    at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:53) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:510) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
    at java.sql.DriverManager.getConnection(DriverManager.java:582) [:1.6.0_13]
    at java.sql.DriverManager.getConnection(DriverManager.java:185) [:1.6.0_13]
    at org.apache.jsp.index_jsp._jspService(index_jsp.java:68)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) [:6.0.0.20100911-M5]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Beta2]
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369) [:6.0.0.20100911-M5]
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) [:6.0.0.20100911-M5]
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253) [:6.0.0.20100911-M5]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Beta2]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.20100911-M5]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.20100911-M5]
    at org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.doFilter(FilterDispatcher.java:63) [:6.0.0.20100911-M5]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.20100911-M5]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.20100911-M5]
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.20100911-M5]
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.20100911-M5]
    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.0.20100911-M5]
    at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.CR3]
    at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.CR3]
    at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.0.0.20100911-M5]
    at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.20100911-M5]
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.20100911-M5]
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.20100911-M5]
    at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.20100911-M5]
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.20100911-M5]
    at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.20100911-M5]
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.20100911-M5]
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.20100911-M5]
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [:6.0.0.20100911-M5]
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.20100911-M5]
    at java.lang.Thread.run(Thread.java:619) [:1.6.0_13]
    When I am using thin driver, I am successful in connecting to the database
    oracle.url=jdbc:oracle:thin:@(description=(address=(host=url.name.com)(protocol=tcp)(port=1521))(connect_data=(sid=user)))
    I am using JBOSS 1.6 with oracle 11.1.0 and jdk 1.6
    Please help me resolve the problem
    Thanks,
    Kumar

    You should confirm that you can connect to the DB with a simple Java class using the url that the code you posted is using.
    This will show that the OCI client is installed and executing properly. If you can't connect externally you will need to fix that first.
    Is the Oracle client installed on the same machine the JDBC code is running on?

  • Probem with databse connection using OCI driver

    hai folks,
    Iam using OCI driver to connect to the database.
    the program is compiling successfully but during runtime it is showing invalid url
    my code follows and my SID value is "mohan"
    import java.sql.*;
    import oracle.sql.*;
    import oracle.jdbc.oracore.Util;
    import oracle.jdbc.*;
    import java.math.BigDecimal;
    public class ArrayExample
         ResultSet rs;
    public static void main (String args[])
    throws Exception
         String driver="oracle.jdbc.driver.OracleDriver";
    DriverManager.registerDriver(new oracle.jdbc.OracleDriver());
    String url="jdbc:oracle://oci8:/@mohan";
    Class.forName(driver);
    Connection conn=DriverManager.getConnection(url,"SCOTT","TIGER");
    DriverManager.getConnection("jdbc:oracle://oci8:/@","scott","tiger") ;
    Statement stmt = conn.createStatement ();
    try
    stmt.execute ("DROP TABLE varray_table");
    stmt.execute ("DROP TYPE num_varray");
    System.out.println("mohan");
    catch (SQLException e)
    System.out.println(e);
    stmt.execute ("CREATE TYPE num_varray AS VARRAY(10) OF NUMBER(12, 2)");
    stmt.execute ("CREATE TABLE varray_table (col1 num_varray)");
    stmt.execute ("INSERT INTO varray_table VALUES (num_varray(100, 200))");
    ResultSet rs = stmt.executeQuery("SELECT * FROM varray_table");
    showResultSet (rs);
    int elements[] = { 300, 400, 500, 600 };
    ArrayDescriptor desc = ArrayDescriptor.createDescriptor("NUM_VARRAY", conn);
    ARRAY newArray = new ARRAY(desc, conn, elements);
    PreparedStatement ps =
    conn.prepareStatement ("insert into varray_table values (?)");
    ((OraclePreparedStatement)ps).setARRAY(1, newArray);
    ps.execute ();
    ResultSet rs = stmt.executeQuery("SELECT * FROM varray_table");
    showResultSet (rs);
    rs.close();
    ps.close();
    stmt.close();
    conn.close();
    public static void showResultSet (ResultSet rs)
    throws SQLException
    int line = 0;
    while (rs.next())
    line++;
    System.out.println("Row "+line+" : ");
    ARRAY array = ((OracleResultSet)rs).getARRAY (1);
    System.out.println ("Array is of type "+array.getSQLTypeName());
    System.out.println
    ("Array element is of typecode "+array.getBaseType());
    System.out.println ("Array is of length "+array.length());
    BigDecimal[] values = (BigDecimal[]) array.getArray();
    for (int i=0; i<values.length; i++)
    BigDecimal value = (BigDecimal) values;
    System.out.println(">> index "+i+" = "+value.intValue());
    please help me in sloving this problem
    my global database name and SID value in mohan
    Thanking u

    Bathina,
    Your problem is in your URL:
    String url="jdbc:oracle://oci8:/@mohan";As far as I know, you can't use the forward-slash character ("/"), by itself, as your database login name -- you must supply a "login/password". I don't know why, and if you don't like it, I suggest you create a TAR (Technical Assistance Request) via the MetaLink Web site.
    I recall similar questions being asked in this forum -- have you tried searching the forum archives?
    Good Luck,
    Avi.

  • Can't use oci driver

    I am now tring to access database use oci8 driver in solaris2.5/oracle816/jdk 1.1.6/classes111.zip, I got a error message "Invalid driver designator" but I am now running the code in a local machine so may be it is not sql*net issue.
    who knows the reason, thanks in advance.

    Please check the way you are trying to make the connection to the database from Java.
    I have just received the same error message (ORA-06401, isn`t it?) and checking my DriverManager.getConnection I have realised that I am using the syntax for the use of the THIN Driver not the OCI. I have not still test it, but I am sure that is the problem.
    You can consult the Oracle8i JDBC Developer's Guide and Reference (http://technet.oracle.com/doc/java.815/a64685/basic1.htm) to see how to create an OCI and Thin connection.
    Anyway, I transcribe you what it says :
    Opening a Connection for the JDBC OCI Driver
    For the JDBC OCI driver, you can specify the database by a TNSNAMES entry. You can find the available TNSNAMES entries listed in the file tnsnames.ora on the client computer from which you are connecting. On Windows NT this file is located in [ORACLE_HOME]\NETWORK\ADMIN. On UNIX systems, you can find it in /var/opt/oracle.
    For example, if you want to connect to the database on host myhost as user scott with password tiger that has a TNSNAMES entry of MyHostString, enter:
    Connection conn =
    DriverManager.getConnection ("jdbc:oracle:oci8:@MyHostString",
    "scott", "tiger");
    Note that both the ":" and "@" characters are necessary.
    For the JDBC OCI driver (as with the Thin driver), you can also specify the database with a Net8 keyword-value pair. This is less readable than a TNSNAMES entry but does not depend on the accuracy of the TNSNAMES.ORA file. The Net8 keyword-value pair also works with other JDBC drivers.
    For example, if you want to connect to the database on host myhost that has a TCP/IP listener up on port 1521, and the SID (system identifier) is orcl, use a statement such as:
    Connection conn =
    DriverManager.getConnection("jdbc:oracle:oci8:@(description=(address=(host= myhost)(protocol=tcp)(port=1521))(connect_data=(sid=orcl)))",
    "scott", "tiger");
    null

  • Connection pool issues with Mysql

    Hi,
    I have defined sufficient read connections (50) in the toplink configuration, I am finding toplink is not releasing the connections in Mysql, this is when run from Jboss App server.
    Is anyone aware of toplink connection pool issues with MySql?
    thanks

    TopLink always closes connections, I cannot see how this could occur.
    Please include your persistence.xml or sessions.xml. Also ensure you are closing your EntityManager or ClientSession, especially if using exclusive connections.
    Also include the exception you are getting.
    James : http://www.eclipselink.org

  • Am trying to connect to database using thin driver am getting an erro

    Hi,
    Am trying to connect to database using thin driver am getting an error.may i know the exact problem. If any one provide the solution in steps wise better.The following is the error.
    Exception in thread "main" java.lang.ClassNotFoundException: oracle.jdbc.oracledriver
         at java.net.URLClassLoader$1.run(Unknown Source)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.net.URLClassLoader.findClass(Unknown Source)
         at java.lang.ClassLoader.loadClass(Unknown Source)
         at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
         at java.lang.ClassLoader.loadClass(Unknown Source)
         at java.lang.ClassLoader.loadClassInternal(Unknown Source)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Unknown Source)
         at JdbcEx.main(JdbcEx.java:15)
    Thanks
    sreekanth

    Am trying to connect to database using thin driver am getting an error.may i know the exact problem. If any one provide the solution in steps wise better.The following is the error.
    Exception in thread "main" java.lang.ClassNotFoundException: oracle.jdbc.oracledriverThe JAR file is not in your classpath. Depends on what JAR you are using (ojdbc14.jar, ojdbc5.jar, etc). Bottom line, it can't find the class for the driver due to the JAR not being in the classpath.

  • Error to connect to oracle 10.2.0.4 using oci driver in solaris

    Urgent Please help me.
    This is the error i am getting when connecting to oracle10.2.0.4 version using oracle oci driver.
    09/10/05 13:52:47 java.lang.UnsatisfiedLinkError: t2cGetCharSet
    09/10/05 13:52:47 at oracle.jdbc.driver.T2CConnection.t2cGetCharSet(Native Method)
    09/10/05 13:52:47 at oracle.jdbc.driver.T2CConnection.getCharSetIds(T2CConnection.java:2954)
    09/10/05 13:52:47 at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:318)
    09/10/05 13:52:47 at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:433)
    09/10/05 13:52:47 at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:141)
    09/10/05 13:52:47 at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:78)
    09/10/05 13:52:47 at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:571)
    09/10/05 13:52:47 at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:217)
    09/10/05 13:52:47 at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:108)
    09/10/05 13:52:47 at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:76)
    09/10/05 13:52:47 at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:58)
    09/10/05 13:52:47 at com.evermind.sql.OrionPooledDataSource.getPooledConnection(OrionPooledDataSource.java:542)
    09/10/05 13:52:47 at com.evermind.sql.PooledConnectionUsage.getPooledConnection(PooledConnectionUsage.java:39)
    09/10/05 13:52:47 at com.evermind.sql.OrionPooledDataSource.checkAndGetMinConnections(OrionPooledDataSource.java:376)
    09/10/05 13:52:47 at com.evermind.sql.OrionPooledDataSource.getTheConnection(OrionPooledDataSource.java:251)
    09/10/05 13:52:47 at com.evermind.sql.OrionPooledDataSource.getTheConnection(OrionPooledDataSource.java:345)
    09/10/05 13:52:47 at com.evermind.sql.OrionPooledDataSource.getConnection(OrionPooledDataSource.java:339)
    09/10/05 13:52:47 at uk.gov.fsa.elms.persistence.base.BaseDataAccess.getValidConnection(BaseDataAccess.java:67)
    09/10/05 13:52:47 at uk.gov.fsa.elms.persistence.base.BaseDataAccess.getConnection(BaseDataAccess.java:125)
    09/10/05 13:52:47 at uk.gov.fsa.elms.persistence.base.dao.BaseDAOImpl.getConnection(BaseDAOImpl.java:76)
    09/10/05 13:52:47 at uk.gov.fsa.elms.processes.batch.ProcessHandler.getProcessId(ProcessHandler.java:48)
    09/10/05 13:52:47 at uk.gov.fsa.elms.processes.batch.ProcessHandler.startProcess(ProcessHandler.java:87)
    09/10/05 13:52:47 at uk.gov.fsa.elms.processes.batch.ProcessManager.startProcess(ProcessManager.java:43)
    09/10/05 13:52:47 at uk.gov.fsa.elms.processes.batch.EventDispatcherServlet$JMSRunner.handleMessage(EventDispatcherServlet.java:306)
    09/10/05 13:52:47 at uk.gov.fsa.elms.processes.batch.EventDispatcherServlet$JMSRunner.run(EventDispatcherServlet.java:355)
    09/10/05 13:52:47 at java.lang.Thread.run(Thread.java:534)

    # This file is actually generated by netca. But if customers choose to
    # install "Software Only", this file wont exist and without the native
    # authentication, they will not be able to connect to the database on NT.
    #SQLNET.AUTHENTICATION_SERVICES = (NTS)I have configured the listener by using NETCA.
    However the TNS connection failed with SQLNET.AUTHENTICATION_SERVICES = (NTS)
    , so I had to disable this parameter

  • Not able to connect to Database By Using OCI Driver

    Hi All,
    I am trying to connect my application to Database using Type 2 OCI driver..
    I am getting this exception:
    {color:#ff0000}*Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory, cause: java.sql.SQLException: ORA-12154: TNS:could not resolve the connect identifier specified*
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
    at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:672)
    at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:346)
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:414)
    at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:132)
    at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:78)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
    at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:82)
    at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:300)
    at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:838)
    at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:821)
    at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:518)
    at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:112)
    at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77)
    at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:513)
    at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:767)
    at com.uprr.app.csl.dao.EventDAOImpl.insertEvent(EventDAOImpl.java:62)
    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:585)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:280)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
    at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:69)
    at com.uprr.app.csl.common.util.LatPerformanceLogInterceptor.aroundAdvice(LatPerformanceLogInterceptor.java:143)
    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:585)
    at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:553)
    at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:542)
    at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:56)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
    at $Proxy2.insertEvent(Unknown Source)
    at Test.getData(Test.java:19)
    at Test.main(Test.java:30)
    {color:#000000}My JDBC URL IS jdbc:oracle:oci
    {color}
    {color:#000000}Thanx a lot in advance
    Samit{color}
    {color}

    {color:#000000}My JDBC URL IS jdbc:oracle:oci {color}That url is not complete, check out [http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm#05_03].

  • Can I use OCI driver to test database connection in JDeveloper9.0.3

    When using JDeveloper 3.2.3, I can use oci8 driver to test the databse connection.
    Then I want oci8 driver work in JDeveloper9.0.2 or JDeveloper 9.0.3. However, it cannot work.
    (Note: but thin driver works fine)
    First, I read the help file and setup ORACLE_HOME environment variable and install
    OCI client driver ocijdbc9.dll on my compuetr. Then some exception is happening when I test again.
    So I want to know, does anyone succeed in testing the connection via oci driver
    and how to fix this problem.
    Thanks a lot.

    Hi !
    You MUST use jdbc library supplied with Oracle client ( so classes12.zip from $ORACLE_HOME/jdbc/lib ), not with JDeveloper - this one might be incopatible with oci native libraries.
    I hope , this helps.
    Michal

  • 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,
    Steve

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

  • Unable to connect to Oracle using OCI Drivers on Linux

    Hi Everyone!
    I am facing a peculiar issue while using Instant Client on Linux ( 64Bit ) running on Red Hat 4.1.
    I have downloaded the instant client version 10.2.0.3(.zip) .so files from the below URL
    http://www.oracle.com/technology/software/tech/oci/instantclient/htdocs/linuxx86_64soft.html
    UPloaded all the files to a directory under /opt and changed the .bash_profile file, the latest content looks like
    ORACLE_HOME=/opt/instantclient_10_2
    export ORACLE_HOME
    PATH=$PATH:$ORACLE_HOME
    export PATH
    TNS_ADMIN=/opt/instantclient_10_2
    export TNS_ADMIN
    LD_LIBRARY_PATH=/opt/instantclient_10_2
    export LD_LIBRARY_PATH
    PATH=$PATH:$LD_LIBRARY_PATH
    export PATH
    CLASSPATH=/opt/instantclient_10_2:/opt/instantclient_10_2/ojdbc.jar
    export CLASSPATH
    Java.library.path=/opt/instantclient_10_2
    export Java.library.path
    As i have downloaded the Sqlplus utility as well, i am able to connect to the Oracle FARM via sqlplus.
    On the other hand, i am unable to connect to the same database via the application. It constantly gives me the following exception,
    java.lang.UnsatisfiedLinkError: no ocijdbc10 in java.library.path
    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682)
    at java.lang.Runtime.loadLibrary0(Runtime.java:823)
    at java.lang.System.loadLibrary(System.java:1030)
    at oracle.jdbc.driver.T2CConnection$1.run(T2CConnection.java:3138)
    at java.security.AccessController.doPrivileged(Native Method)
    at oracle.jdbc.driver.T2CConnection.loadNativeLibrary(T2CConnection.java:3134)
    at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:220)
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:438)
    at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:131)
    at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:77)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:752)
    at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:296)
    at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:220)
    at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:164)
    at com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(DSManagedConnectionFactory.java:105)
    at com.sun.enterprise.resource.LocalTxConnectorAllocator.createResource(LocalTxConnectorAllocator.java:68)
    at com.sun.enterprise.resource.AbstractResourcePool.createSingleResource(AbstractResourcePool.java:891)
    at com.sun.enterprise.resource.AbstractResourcePool.createResourceAndAddToPool(AbstractResourcePool.java:1752)
    at com.sun.enterprise.resource.AbstractResourcePool.createResources(AbstractResourcePool.java:917)
    at com.sun.enterprise.resource.AbstractResourcePool.initPool(AbstractResourcePool.java:225)
    at com.sun.enterprise.resource.AbstractResourcePool.internalGetResource(AbstractResourcePool.java:516)
    at com.sun.enterprise.resource.AbstractResourcePool.getResource(AbstractResourcePool.java:443)
    at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:248)
    at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:176)
    at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:327)
    at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:235)
    at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165)
    at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:158)
    at com.sun.gjc.spi.base.DataSource.getConnection(DataSource.java:108)
    at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:113)
    at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:79)
    at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:922)
    at org.springframework.jdbc.core.JdbcTemplate.call(JdbcTemplate.java:984)
    at org.springframework.jdbc.object.StoredProcedure.execute(StoredProcedure.java:117)
    at com.gecf.uk.pca.dcs.util.SystemParametersDAO$SysParamsStoredProcedure.execute(SystemParametersDAO.java:150)
    at com.gecf.uk.pca.dcs.util.SystemParametersDAO.getSystemParametersList(SystemParametersDAO.java:67)
    at com.gecf.uk.pca.dcs.util.SystemParametersDAO.getSystemParametersMap(SystemParametersDAO.java:94)
    at com.gecf.uk.pca.dcs.util.SystemParameters.loadParameters(SystemParameters.java:44)
    at com.gecf.uk.pca.dcs.util.SystemParameters.<init>(SystemParameters.java:33)
    at com.gecf.uk.pca.dcs.util.SystemParameters.getInstance(SystemParameters.java:72)
    at org.apache.jsp.common.secure.mypayment_jsp._jspService(mypayment_jsp.java from :86)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:93)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:317)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:198)
    at com.gecf.uk.pca.dcs.web.util.SessionFilter.doFilter(SessionFilter.java:97)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:198)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:288)
    at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
    |#]
    I have used the classes12.jar and ojdbc.jar which came with the download and nothing seems to work. A bit surprising when sqlplus works and not the application. I suspect there could be an issue with the driver class. I have been struggling to figure this out for days now...
    Can anyone please share their thoughts if something similar was observed earlier please.
    Any quick help will highly be appreciated.

    ORACLE_HOME=/opt/instantclient_10_2
    export ORACLE_HOMEYou don't set ORACLE_HOME with Instant Client.
    PATH=$PATH:$LD_LIBRARY_PATH
    export PATHThis is unnecessary.
    CLASSPATH=/opt/instantclient_10_2:/opt/instantclient_10_2/ojdbc.jar
    export CLASSPATHThis is wrong.
    It should be:
    CLASSPATH=/opt/instantclient_10_2/ojdbc14.jar:<whatever else you need there>
    Java.library.path=/opt/instantclient_10_2
    export Java.library.pathThis is useless; java.library.path is not an environment variable.
    java.lang.UnsatisfiedLinkError: no ocijdbc10 in java.library.pathThe case is pretty clear. You want to use the OCI driver (your URL starts with "jdbc:oracle:oci:"), so the Java Virtual Machine is looking for libocijdbc10.so in the Java library path but cannot find it.
    What is also clear is that the program does not use the CLASSPATH environment variable you set, because then it would never have found the Oracle Driver.
    So it seems that your program is ignoring the environment you set (which would explain why it also ignores LD_LIBRARY_PATH which you set correctly).
    You must have the environment variables set and exported in the shell that starts the "java" executable.
    Also, check that there is no other ojdbc14.jar on this machine (use "find").
    To help you debug your problem, let me explain how Sun Java sets Java library path on Linux:
    - If you start java with "java -Djava.library.path=/some/dir:/other/dir ...", the Java library path is set to exactly that value.
    - If you do not specify -Djava.library.path, the Java library path is taken from the environment variable LD_LIBRARY_PATH.
    - Directories listed in /etc/ld.so.conf have no influence on the Java library path (which gave me quite a headache in the beginning).
    Do you really need the OCI Driver? If you can do with the Thin Driver (i.e., use an URL that starts with "jdbc:oracle:thin:") you don't need any shared libraries at all.
    Yours,
    Laurenz Albe

  • Poor performance caused by using OCI driver?

    [Sorry for the multipost]
    I'm working on a medium-sized Apache / Tomcat / WLS 5.10 / Oracle
    system hosted on some 4-processor Suns. The Apache / Tomcat tier
    uses one box, the WebLogic tier uses another, and the Oracle tier
    uses a third.
    We've found that the performance, measured as the time it takes user
    operations like loading a page that displays database data, gets
    unacceptably bad at suspiciously low loads. When the system is in
    this state, none of the machines appears to be pushed very hard.
    There's no significant paging going on, the disk and network I/O
    isn't out of line, and the CPU load just isn't high enough to
    explain what's going on. Only the WebLogic tier shows a load over
    10%. When the system is perceived as too slow by the users, the
    CPU load on this tier is only 30-40%.
    To try to find out what's going on, I did a series of thread dumps.
    When the system is heavily loaded, I only see about three Oracle
    statements currently being processed (runnable threads with call
    stacks inside weblogic.db.oci.*). What I do see lots of is blocked
    (and one runnable) threads inside
    weblogic.rjvm.RJVMImpl.removePeerGoneListener or
    weblogic.rjvm.RJVMImpl.addPeerGoneListener. These threads appear to
    be attempting to obtain or release database connections.
    I don't know why, but the site is configured to use the WebLogic OCI
    driver for Oracle, instead of the Oracle-supplied thin driver. Is what I'm
    seeing what Sun is describing in this paragraph
    (excerpted from http://java.sun.com/docs/hotspot/PerformanceFAQ.html#24):
    Oracle provides two types of database drivers: a type-2
    driver, called the OCI (Oracle Call Interface) driver
    that utilizes native code, and a type-4 pure Java driver
    called the thin driver. In single processor environments,
    the thin driver works somewhat better than the OCI driver
    because of the JNI overhead associated with the OCI
    driver. On multi-processor configuations, synchronization
    points within Solaris used by the OCI driver become big
    bottlenecks and prevent scaling. We recommend using the
    thin driver in all cases.
    -- Erik

    Hi. I'll chip in here too. Yes, you are wasting JVM cycles having all those
    wasted threads. Threads aren't free, inexhaustable sources of compute power
    that some people assume (I'm not saying you're one). All these threads do
    share a single OS process and CPU. The JVM has to check all these all the
    time to see if they have something to do. I recommend configuring the
    server to run about 15 or 20 execute-threads.
    I see only one thread waiting on Oracle to return data, so I don't think this
    is a JDBC issue necessarily. What I do see is lots of threads trying to operate
    on a Vector, all being blocked, or at least serialized by the lock this thread has, below.
    Is the server hung at this point, or just slow?
    "ExecuteThread-109" daemon prio=5 tid=0x311fb8 nid=0x78 runnable [0xcf9ff000..0xcf9ffc68]
    at java.util.Vector.removeElementAt(Vector.java:509)
    at java.util.Vector.removeElement(Vector.java:598)
    at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
    at weblogic.time.server.ScheduledTrigger.destroy(ScheduledTrigger.java:112)
    at weblogic.time.server.ScheduledTrigger.cancel(ScheduledTrigger.java:100)
    at weblogic.jts.internal.CoordinatorImpl.cancelCurrentTimer(CoordinatorImpl.java:199)
    at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:404)
    at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
    at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:103
    at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:849)
    at com.xxx.yyy.as.TaskSessionEJBEOImpl.findTaskByFilter(TaskSessionEJBEOImpl.java:784)
    at
    com.xxx.yyy.as.TaskSessionEJBEOImpl_WLSkel.invoke(TaskSessionEJBEOImpl_WLSkel.java:101)
    at
    weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at
    weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    Erik Horstkotte wrote:
    "Rob Woollen" <[email protected]> wrote in message
    news:[email protected]...
    You generally need a lot of data to find the performance problem in
    a distributed system like this.Understood, but I was hoping that someone would recognize my description
    as the "signature" of the locking problem with the OCI driver that Sun
    describes.
    It's very easy to switch to the Thin driver so you might as well
    try it.I had hoped so, and in most cases, you're likely correct. Unfortunately,
    the OCI driver is a touch more permissive than the thin driver. Some
    errors (too many bind parameters) have crept in to our code that don't
    cause problems for the OCI driver, but cause exceptions to be thrown by
    the thin driver. In this particular case, I'm trying to solve a problem on
    a production system - fixing the code there isn't an option (we are
    switching to thin driver in our next release, so we are fixing these
    problems).
    If that doesn't help, I would suggest inserting some timing logic
    in your code. In particular, I'd want to know the time a request
    entered apache/tomcat, left apache/tomcat, entered WLS, left WLS
    (to go to the database), returned from the database, left WLS, got
    back to apache/tomcat, and finally left apache/tomcat to return the
    response. With information like that, you should be able to narrow
    down the problem a bit.In the next release, this is a good idea, and we'll probably do something
    much like this. Unfortunately I can't make changes to the code on the
    production site, so I have to rely on more passive methods of data
    collection for the moment.
    "Slava Imeshev" <[email protected]> wrote in message
    news:[email protected]...
    There can be other reasons for bad performance ranging from
    serialized access to singletons to inefficient queries to
    server mis-configuration. I have some doubts that oci driver
    would affect performance at low loads.I don't see any evidence of serialization blocking, except for the
    interesting locking issue that I mentioned in the original message (a
    PeerGoneListener table maintained somewhere down inside WLS).
    I'm certain that inefficient queries play a large role in our
    performance problems.
    Service mis-configuration could very well play a role here. Note for
    example the large number of blocked idle execute threads in the thread
    dump below. Clearly this instance has way too many execute threads. Not
    knowing the internal architecture of WebLogic Server, nor the
    implementation method Sun used for monitors in Solaris JVM 1.4.2, I don't
    know how much of an impact an excess of execute threads has on
    performance. Anyone?
    Could you post a questionable thread dump here?See the bottom of this message. The dump has been "blinded" to remove some
    customer-specific information.
    Also, what's the load in terms of number of concurrent users
    and requests per second?At peak load, there are about 60 users logged in, of whom only about 4-12
    actually do much. The number of requests per second is very peaky, and
    varies from about 1-10 per second. The complexity of requests also varies
    wildly.
    I've attached a thread dump from a point in time when the WebLogic Server
    instance was taking about 30% of the CPU.
    Any and all ideas are appreciated.
    -- Erik
    Full thread dump:
    "HighPriority TimeEventGenerator" daemon prio=9 tid=0x4223ed0 nid=0xa7 waiting on monitor [0xcceff000..0xcceffc68]
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:141)
    at java.lang.Thread.run(Thread.java:484)
    "ListenThread" prio=5 tid=0x423f7a0 nid=0xa6 runnable [0xccbff000..0xccbffc68]
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
    at java.net.ServerSocket.implAccept(ServerSocket.java:243)
    at java.net.ServerSocket.accept(ServerSocket.java:222)
    at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:325)
    "NBExecuteThread-1" daemon prio=5 tid=0x331ea0 nid=0xa2 waiting on monitor [0xccfff000..0xccfffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "NBExecuteThread-0" daemon prio=5 tid=0x3317b8 nid=0xa1 waiting on monitor [0xcd0ff000..0xcd0ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-149" daemon prio=5 tid=0x330228 nid=0xa0 runnable [0xcd1ff000..0xcd1ffc68]
    at weblogic.socket.PosixSocketMuxer.poll(Native Method)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-148" daemon prio=5 tid=0x32f740 nid=0x9f waiting on monitor [0xcd2ff000..0xcd2ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-147" daemon prio=5 tid=0x32ec58 nid=0x9e waiting for monitor entry [0xcd3ff000..0xcd3ffc68]
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:289)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-146" daemon prio=5 tid=0x32e170 nid=0x9d waiting for monitor entry [0xcd4ff000..0xcd4ffc68]
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:289)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-145" daemon prio=5 tid=0x32ce80 nid=0x9c waiting on monitor [0xcd5ff000..0xcd5ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-144" daemon prio=5 tid=0x32c398 nid=0x9b waiting for monitor entry [0xcd6ff000..0xcd6ffc68]
    at java.util.Vector.removeElement(Vector.java:595)
    at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
    at weblogic.jts.internal.CoordinatorImpl.unregisterClientDeathNotification(CoordinatorImpl.java:101)
    at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:347)
    at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
    at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:103)
    at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:849)
    at com.xxx.yyy.as.ProfileSessionEJBEOImpl.getContactNumbers(ProfileSessionEJBEOImpl.java:5687)
    at com.xxx.yyy.as.ProfileSessionEJBEOImpl_WLSkel.invoke(ProfileSessionEJBEOImpl_WLSkel.java:222)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-143" daemon prio=5 tid=0x32b8b0 nid=0x9a waiting on monitor [0xcd7ff000..0xcd7ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-142" daemon prio=5 tid=0x32adc8 nid=0x99 waiting on monitor [0xcd8ff000..0xcd8ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-141" daemon prio=5 tid=0x32a2e0 nid=0x98 waiting on monitor [0xcd9ff000..0xcd9ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-140" daemon prio=5 tid=0x3297f8 nid=0x97 waiting on monitor [0xcdaff000..0xcdaffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-139" daemon prio=5 tid=0x328d10 nid=0x96 waiting for monitor entry [0xcdbff000..0xcdbffc68]
    at java.util.Vector.addElement(Vector.java:573)
    at weblogic.rjvm.RJVMImpl.addPeerGoneListener(RJVMImpl.java:348)
    at weblogic.time.server.ScheduledTrigger.setExecCon(ScheduledTrigger.java:46)
    at weblogic.t3.srvr.T3ServerServices.getScheduledTrigger(T3ServerServices.java:177)
    at weblogic.jts.internal.CoordinatorImpl.resetTimer(CoordinatorImpl.java:210)
    at weblogic.jts.internal.CoordinatorImpl.<init>(CoordinatorImpl.java:83)
    at weblogic.jts.internal.CoordinatorFactoryImpl.createCoordinator(CoordinatorFactoryImpl.java:95)
    at weblogic.jts.internal.CoordinatorFactoryImpl_ServiceStub.createCoordinator(CoordinatorFactoryImpl_ServiceStub.java:69)
    at weblogic.jts.internal.TxContext.getCoordinator(TxContext.java:139)
    at weblogic.jts.internal.TxContext.begin(TxContext.java:93)
    at weblogic.jts.internal.CurrentImpl.begin(CurrentImpl.java:48)
    at weblogic.jts.internal.TransactionManagerImpl.begin(TransactionManagerImpl.java:56)
    at weblogic.ejb.internal.EJBHomeImpl.setupTransaction(EJBHomeImpl.java:838)
    at weblogic.ejb.internal.BaseEJBObject.setupTransaction(BaseEJBObject.java:281)
    at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:471)
    at com.xxx.yyy.as.SecuritySessionEJBEOImpl.getClientConfigurationSiteSpecific(SecuritySessionEJBEOImpl.java:143)
    at com.xxx.yyy.as.SecuritySessionEJBEOImpl_WLSkel.invoke(SecuritySessionEJBEOImpl_WLSkel.java:254)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-138" daemon prio=5 tid=0x328228 nid=0x95 waiting on monitor [0xcdcff000..0xcdcffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-137" daemon prio=5 tid=0x326d38 nid=0x94 waiting on monitor [0xcddff000..0xcddffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-136" daemon prio=5 tid=0x326250 nid=0x93 waiting on monitor [0xcdeff000..0xcdeffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-135" daemon prio=5 tid=0x325768 nid=0x92 waiting on monitor [0xcdfff000..0xcdfffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-134" daemon prio=5 tid=0x324c80 nid=0x91 waiting on monitor [0xce0ff000..0xce0ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-133" daemon prio=5 tid=0x324198 nid=0x90 waiting on monitor [0xce1ff000..0xce1ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-132" daemon prio=5 tid=0x3236b0 nid=0x8f waiting on monitor [0xce2ff000..0xce2ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-131" daemon prio=5 tid=0x322bc8 nid=0x8e waiting on monitor [0xce3ff000..0xce3ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-130" daemon prio=5 tid=0x3220e0 nid=0x8d waiting on monitor [0xce4ff000..0xce4ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-129" daemon prio=5 tid=0x3215f8 nid=0x8c waiting on monitor [0xce5ff000..0xce5ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-128" daemon prio=5 tid=0x320b10 nid=0x8b waiting on monitor [0xce6ff000..0xce6ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-127" daemon prio=5 tid=0x320028 nid=0x8a waiting on monitor [0xce7ff000..0xce7ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-126" daemon prio=5 tid=0x31f540 nid=0x89 waiting on monitor [0xce8ff000..0xce8ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-125" daemon prio=5 tid=0x31ea58 nid=0x88 waiting on monitor [0xce9ff000..0xce9ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-124" daemon prio=5 tid=0x31df70 nid=0x87 waiting on monitor [0xceaff000..0xceaffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-123" daemon prio=5 tid=0x31d488 nid=0x86 waiting on monitor [0xcebff000..0xcebffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-122" daemon prio=5 tid=0x31bb90 nid=0x85 waiting on monitor [0xcecff000..0xcecffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-121" daemon prio=5 tid=0x31b0a8 nid=0x84 waiting on monitor [0xcedff000..0xcedffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-120" daemon prio=5 tid=0x31a5c0 nid=0x83 waiting for monitor entry [0xceeff000..0xceeffc68]
    at java.util.Vector.addElement(Vector.java:573)
    at weblogic.rjvm.RJVMImpl.addPeerGoneListener(RJVMImpl.java:348)
    at weblogic.jdbc20.rmi.internal.ConnectionImpl.<init>(ConnectionImpl.java:39)
    at weblogic.jdbc20.common.internal.RmiDataSource.getConnection(RmiDataSource.java:65)
    at weblogic.jdbc20.common.internal.RmiDataSource_ServiceStub.getConnection(RmiDataSource_ServiceStub.java:179)
    at com.xxx.yyy.asutil.DataAccessManager.getConnection(DataAccessManager.java:113)
    at com.xxx.yyy.as.MetricsSessionEJB.logEvent(MetricsSessionEJB.java:222)
    at com.xxx.yyy.as.MetricsSessionEJBEOImpl.logEvent(MetricsSessionEJBEOImpl.java:324)
    at com.xxx.yyy.as.MetricsSessionEJBEOImpl_WLSkel.invoke(MetricsSessionEJBEOImpl_WLSkel.java:242)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-119" daemon prio=5 tid=0x319ad8 nid=0x82 waiting on monitor [0xcefff000..0xcefffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-118" daemon prio=5 tid=0x318ff0 nid=0x81 runnable [0xcf0fe000..0xcf0ffc68]
    at weblogic.db.oci.OciCursor.execAndFetch(Native Method)
    at weblogic.db.oci.OciCursor.oci_execAndFetch(OciCursor.java:1890)
    at weblogic.jdbcbase.oci.Statement.executeQuery(Statement.java:905)
    at weblogic.jdbcbase.jts.Statement.executeQuery(Statement.java:58)
    at weblogic.jdbc20.rmi.internal.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:46)
    at weblogic.jdbc20.rmi.SerialPreparedStatement.executeQuery(SerialPreparedStatement.java:40)
    at com.xxx.yyy.as.SecuritySessionEJB.getClientConfiguration(SecuritySessionEJB.java:1669)
    at com.xxx.yyy.as.SecuritySessionEJBEOImpl.getClientConfiguration(SecuritySessionEJBEOImpl.java:985)
    at com.xxx.yyy.as.SecuritySessionEJBEOImpl_WLSkel.invoke(SecuritySessionEJBEOImpl_WLSkel.java:234)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.extensions.BasicRequestDispatcher.dispatch(BasicRequestDispatcher.java:82)
    at weblogic.rmi.internal.ServerRequest.sendOneWay(ServerRequest.java:73)
    at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:77)
    at com.xxx.yyy.as.SecuritySessionEJBEOImpl_WLStub.getClientConfiguration(SecuritySessionEJBEOImpl_WLStub.java:703)
    at com.xxx.yyy.as.QuestionnaireSessionEJB.getQuestionnaireBatches(QuestionnaireSessionEJB.java:3479)
    at com.xxx.yyy.as.QuestionnaireSessionEJBEOImpl.getQuestionnaireBatches(QuestionnaireSessionEJBEOImpl.java:631)
    at com.xxx.yyy.as.QuestionnaireSessionEJBEOImpl_WLSkel.invoke(QuestionnaireSessionEJBEOImpl_WLSkel.java:237)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-117" daemon prio=5 tid=0x317f00 nid=0x80 waiting on monitor [0xcf1ff000..0xcf1ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-116" daemon prio=5 tid=0x317418 nid=0x7f waiting on monitor [0xcf2ff000..0xcf2ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-115" daemon prio=5 tid=0x316930 nid=0x7e waiting on monitor [0xcf3ff000..0xcf3ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-114" daemon prio=5 tid=0x315e48 nid=0x7d waiting on monitor [0xcf4ff000..0xcf4ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-113" daemon prio=5 tid=0x314b58 nid=0x7c waiting on monitor [0xcf5ff000..0xcf5ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-112" daemon prio=5 tid=0x314070 nid=0x7b waiting on monitor [0xcf6ff000..0xcf6ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-111" daemon prio=5 tid=0x313588 nid=0x7a waiting on monitor [0xcf7ff000..0xcf7ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-110" daemon prio=5 tid=0x312aa0 nid=0x79 waiting on monitor [0xcf8ff000..0xcf8ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-109" daemon prio=5 tid=0x311fb8 nid=0x78 runnable [0xcf9ff000..0xcf9ffc68]
    at java.util.Vector.removeElementAt(Vector.java:509)
    at java.util.Vector.removeElement(Vector.java:598)
    at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
    at weblogic.time.server.ScheduledTrigger.destroy(ScheduledTrigger.java:112)
    at weblogic.time.server.ScheduledTrigger.cancel(ScheduledTrigger.java:100)
    at weblogic.jts.internal.CoordinatorImpl.cancelCurrentTimer(CoordinatorImpl.java:199)
    at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:404)
    at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
    at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:103)
    at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:849)
    at com.xxx.yyy.as.TaskSessionEJBEOImpl.findTaskByFilter(TaskSessionEJBEOImpl.java:784)
    at com.xxx.yyy.as.TaskSessionEJBEOImpl_WLSkel.invoke(TaskSessionEJBEOImpl_WLSkel.java:101)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-108" daemon prio=5 tid=0x3114d0 nid=0x77 waiting on monitor [0xcfaff000..0xcfaffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-107" daemon prio=5 tid=0x3109e8 nid=0x76 waiting on monitor [0xcfbff000..0xcfbffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-106" daemon prio=5 tid=0x30ff00 nid=0x75 waiting on monitor [0xcfcff000..0xcfcffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-105" daemon prio=5 tid=0x30f418 nid=0x74 waiting for monitor entry [0xcfdff000..0xcfdffc68]
    at java.util.Vector.removeElement(Vector.java:595)
    at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
    at weblogic.jdbc20.rmi.internal.ConnectionImpl.close(ConnectionImpl.java:161)
    at weblogic.jdbc20.rmi.SerialConnection.close(SerialConnection.java:162)
    at com.xxx.yyy.asutil.Util

Maybe you are looking for