Error: Creating a Connection Pool: issue with valid transaction levels

Server: SunOS 5.8 Generic_117350-27 sun4u sparc SUNW,UltraAX-MP
App Server: Sun Java System Application Server 8.2
Jar: ojdbc14.jar
Datasource Classname: oracle.jdbc.pool.OracleConnectionPoolDataSource
Resource Type: javax.sql.ConnectionPoolDataSource
[Issue]
Using /SUNWappserver/lib/ojdbc14.jar, when I create my connection pool in Sun Java System Application Server 8.2, I return the following error each time I try to start the domain:
[#|2006-07-28T14:53:56.169-0500|WARNING|sun-appserver-pe8.2|javax.enterprise.resource.resourceadapter|_ThreadID=11;|RAR5117 : Failed to obtain/create connection. Reason : The isolation level could not be set: READ_COMMITTED and SERIALIZABLE are the only valid transaction levels|#]
When I change the value to "SERIALIZABLE" in my domain.xml file, I receive the following error in my server.log:
Caused by: org.xml.sax.SAXParseException: Attribute "transaction-isolation-level" with value "SERIALIZABLE" must have a value from the list "read-uncommitted read-committed repeatable-read serializable ".
So, I'm stuck!
I can't use the values READ_COMMITTED or SERIALIZABLE since the valid values are "read-uncommitted read-committed repeatable-read serializable ".
Case sensitivity matters.
Any thoughts or help would be greatly appreciated.
Thanks,
--Todd                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

The Oracle JDBC accepts TRANSACTION_READ_COMMITTED and TRANSACTION_SERIALIZABLE isolation levels.
Example:
connAttr.setProperty(“TRANSACTION_ISOLATION”, “TRANSACTION_SERIALIZABLE”);
I'd check with the Apps server folks.
Kuassi - blog http://db360.blogspot.com/
------ book http://www.amazon.com/gp/product/1555583296/

Similar Messages

  • 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

  • Error creating a connection pool to DB2 with the weblogic 8.1 driver

    I am trying to create a new connection pool with using the weblogic 8.1 (non XA driver (weblogic.jdbc.db2.DB2Driver)). When I create the pool one of the steps is to test the driver configuration and it fails with this step.
    I get the following error:
    [BEA][DB2 JDBC Driver]The databaseName connection property is not valid when connecting to Host Operating Systems.
    We are going through IBM's DB2 connect gateway (version 8.x) to connect to a DB2 database running on Z/OS.
    Here are my connection parameters:
    Driver Classname: weblogic.jdbc.db2.DB2Driver
    url: jdbc:bea:db2://db2cont2.arrow.com:3700
    Database User Name: XXXXXX
    password xxxxx
    properties
    user=db2trce
    portNumber=3700
    databaseName=DB2T
    batchPerformanceWorkaround=true
    serverName=db2cont2.arrow.com
    Any ideas would be much appreciated.
    Thanks,
    Matt

    Matthew McHugh wrote:
    I am trying to create a new connection pool with using the weblogic 8.1 (non XA driver (weblogic.jdbc.db2.DB2Driver)). When I create the pool one of the steps is to test the driver configuration and it fails with this step.
    I get the following error:
    [BEA][DB2 JDBC Driver]The databaseName connection property is not valid when connecting to Host Operating Systems.
    We are going through IBM's DB2 connect gateway (version 8.x) to connect to a DB2 database running on Z/OS.
    Here are my connection parameters:
    Driver Classname: weblogic.jdbc.db2.DB2Driver
    url: jdbc:bea:db2://db2cont2.arrow.com:3700
    Database User Name: XXXXXX
    password xxxxx
    properties
    user=db2trce
    portNumber=3700
    databaseName=DB2T
    batchPerformanceWorkaround=true
    serverName=db2cont2.arrow.com
    Any ideas would be much appreciated.
    Thanks,
    MattHi Matt. Unfortunately DB2 is different on differnet OSes. For
    DB2 on OS/390, z/OS, iSeries, and AS/4001, the URL is like this:
    jdbc:bea:db2://db2_server_name:port;Location=db2_location;CollectionId=your_collectionname
    Try removing the serverName property and the databaseName, and
    change your URL to
    jdbc:bea:db2://db2cont2.arrow.com:3700;Location=db2_location;CollectionId=your_collectionname
    where you would change 'db2_location' and 'your_collectionname' as appropriate.
    Joe

  • Error creating a connection pool (No suitable driver)

    I have just installed WLS6.1 SP3
    I try to create a connection with the following parameters
    URL = jdbc:oracle:thin@myOracleServer:1521:myOracleSID
    DriverName = oracle.jdbc.driver.OracleDriver
    every thing else is left as the defaults,
    when I click create everything is OK.
    I then go to the "Targets" tab and select myserver,
    move it to the chosen column and click apply.
    I then get the error
    <Error> <JDBC> <Cannot startup connection pool "myCP" No suitable driver>
    I looked at the doc edocs.bea.com/wls/docs61/jdbc/thirdparty.html
    Under the section "Setting environment for your third party driver"
    it implys that if your using sybase jconnect or oracle thin drivers
    you do not need to do anything else.
    I looked in the weblogic.jar file and the OracleDriver.class file
    is there under oracle\jdbc\driver.
    the CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
    I would have thought that the driver class in the jar file
    would have be picked up given the path & classname match the
    driver name enter in the console.
    Any ideas on how to fix this problem?

    "Robert Towler" <[email protected]> wrote in message
    news:3dd3ea04$[email protected]..
    Thanks Slava, you were correct,
    I really appreciate it.Glad to help :)
    Regards,
    Slava Imeshev
    "Slava Imeshev" <[email protected]> wrote:
    Hi Robert,
    Looks like colon is missing after jdbc:oracle:thin. The url should be
    jdbc:oracle:thin:@myOracleServer:1521:myOracleSID
    Regards,
    Slava Imeshev
    "Robert Towler" <[email protected]> wrote in message
    news:3dd3e3c6$[email protected]..
    I have just installed WLS6.1 SP3
    I try to create a connection with the following parameters
    URL = jdbc:oracle:thin@myOracleServer:1521:myOracleSID
    DriverName = oracle.jdbc.driver.OracleDriver
    every thing else is left as the defaults,
    when I click create everything is OK.
    I then go to the "Targets" tab and select myserver,
    move it to the chosen column and click apply.
    I then get the error
    <Error> <JDBC> <Cannot startup connection pool "myCP" No suitable
    driver>
    >>>
    I looked at the doc edocs.bea.com/wls/docs61/jdbc/thirdparty.html
    Under the section "Setting environment for your third party driver"
    it implys that if your using sybase jconnect or oracle thin drivers
    you do not need to do anything else.
    I looked in the weblogic.jar file and the OracleDriver.class file
    is there under oracle\jdbc\driver.
    the CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
    I would have thought that the driver class in the jar file
    would have be picked up given the path & classname match the
    driver name enter in the console.
    Any ideas on how to fix this problem?

  • Java Connection Pooling issue with Oracle 10g Express Edition

    Hello
    I have a Java based web application that uses the Oracle 10g Express Edition database. I am using a connection pool to get connections to the database.
    I use the NetBeans IDE and run my web application on the bundled Tomcat server(5.5.7) that comes with the IDE. Though when I initially run the application from the IDE, the connection pool is set up fine, when I recompile my java code and try to run the application again, I get the following error each time:
    Listener refused the connection with the following error:
    ORA-12516, TNS:listener could not find available handler with the
    matching protocol stack.
    The logs before the error shows up, indicate that the connection pool object is fine and gives me the number of available connections and the number of active connections and so on, which I have printed from the constructor of the Connection Pool class:
    For e.g.:
    Cache size = 17
    Available Connections = 17
    Cache Limit = 1000
    Active size = 0
    However, if I kill my Tomcat server process and run the application again, it works fine with no error.
    I looked around for possible causes and solutions and all I could find
    was increasing the processes parameter value in the init.ora file. I have increased the parameter value to from 100 to 20000 now, in increments of 500/1000 each time but it hasnt worked so far.
    Someone else suggested that I increase the size of my connection pool; I initially had it set to a minimum limit of 5, an initial limit of 10 and a maximum limit of 1000. However if I set the Initial Limit to anything above 17 connections, I see the following log on the Bundled Tomcat log and my application doesn't run at all:
    Log: Loading JDBC Driver : class=oracle.jdbc.driver.OracleDriver ...
    Log: Loaded JDBC Driver
    Log: Connection with URL=jdbc:oracle:thin:@localhost:1521:xe as username/password
    Error code not handled : 0
    Exception Message :java.sql.SQLException: Listener refused the connection with the following error:
    ORA-12519, TNS: no appropriate service handler found
    The Connection descriptor used by the client was:
    localhost:1521:xe
    // End of log
    And the Bundled Tomcat server automatically shuts down.
    Again the System.out statements from the Connection Pool class constructor show that the cache has been initialized and that currently there are free connections available in the pool.
    E.g.
    Cache size = 18
    Available Connections = 18
    Cache Limit = 1000
    Active size = 0
    Has anyone faced anything similar? Could someone please suggest what I'm doing wrong here and what I should do to set right this problem?
    Swetha

    hello, please pardon me, my english is basic. i do of my best. i had the same problem until reading the pdf documentation 2 days for java devvelloper.it is simple, follow this way.
    try {OracleDataSource ds;
         Connection conn;
      ds = new OracleDataSource();
      ds.setURL("jdbc:oracle:thin:@localhost");
      conn = ds.getConnection("userid","password");
    Statement stmt = conn.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
    don't forget to Dowload the user client of oracle Express Edition. do the rest of your program and it will work. take a look to the documentation pdf for java develloper. all it is explained.  good look                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Connection pool issue with packaged application

    we are using 9.2 mp1 for a Oarcle packaged application which is talking to Oracle RAC. In production one
    of the RAC nodes went down and we see that the wbelogic connection pool is never able to reconnect
    This is a packaged application Bharosa which internally uses hibernate and in turn relies on weblogic connection pool
    See a few stuck threads in the logs indicating some prolem with the connection cleanup
    <Dec 16, 2008 12:11:03 PM PST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "626" seconds working on the request "Http Request: /fahost/econnect/IntegratedAuthRemoteServlet.svl;JSPSESSIONID=82W2JLLJ8vCB25G3jyc6cYdXVXLYc1G1GwTt91plpCpB9MY6yQP3!468271380!-864027599!1229457609639", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
         weblogic.common.resourcepool.ResourcePoolImpl.releaseResource(ResourcePoolImpl.java:521)
         weblogic.jdbc.common.internal.ConnectionPool.release(ConnectionPool.java:669)
         weblogic.jdbc.common.internal.ConnectionPoolManager.release(ConnectionPoolManager.java:113)
         weblogic.jdbc.wrapper.PoolConnection.doClose(PoolConnection.java:192)
         weblogic.jdbc.wrapper.PoolConnection.close(PoolConnection.java:117)
         org.hibernate.connection.DatasourceConnectionProvider.closeConnection(DatasourceConnectionProvider.java:74)
         org.hibernate.jdbc.ConnectionManager.closeConnection(ConnectionManager.java:388)
         org.hibernate.jdbc.ConnectionManager.aggressiveRelease(ConnectionManager.java:343)
         org.hibernate.jdbc.ConnectionManager.afterTransaction(ConnectionManager.java:230)
         org.hibernate.jdbc.JDBCContext.afterTransactionCompletion(JDBCContext.java:201)
         org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:127)
         com.bharosa.common.hibernate.HiberDBMgr.commitTransaction(HiberDBMgr.java:293)
         com.bharosa.common.db.BharosaDBMgr.endSession(BharosaDBMgr.java:243)
         com.bharosa.common.hibernate.HiberBaseDAO.executeQuery(HiberBaseDAO.java:596)
         com.bharosa.common.hibernate.HiberBaseDAO.executeDBQuery(HiberBaseDAO.java:543)
         com.bharosa.common.hibernate.HiberDBMgr.executeDBQuery(HiberDBMgr.java:351)
         com.bharosa.vcrypt.dataaccess.impl.VCryptUserDataAccessImpl.getVCryptUserByLoginId(VCryptUserDataAccessImpl.java:520)
         com.bharosa.vcrypt.auth.impl.VCryptAuthImpl.getUserByLoginId(VCryptAuthImpl.java:274)
         com.bharosa.client.BharosaHelper.getUser(BharosaHelper.java:116)
         com.bharosa.client.BharosaHelper.createPersonalizedAuthentiPad(BharosaHelper.java:308)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.getAuthpadHTML(IntegratedAuthDelegateSkeleton.java:672)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.createAuthPad(IntegratedAuthDelegateSkeleton.java:113)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.createAuthPad(IntegratedAuthDelegateSkeleton.java:103)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthRemoteServlet.invokeService(IntegratedAuthRemoteServlet.java:60)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthRemoteServlet.doPost(IntegratedAuthRemoteServlet.java:40)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
         weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
         weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
         weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
         weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
         weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    <Dec 16, 2008 12:11:03 PM PST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "616" seconds working on the request "weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl@ba063", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
         weblogic.common.resourcepool.ResourcePoolImpl.getCurrCapacity(ResourcePoolImpl.java:671)
         weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:1922)
         weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
         weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    <Dec 16, 2008 12:11:03 PM PST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "635" seconds working on the request "Http Request: /fahost/econnect/IntegratedAuthRemoteServlet.svl;JSPSESSIONID=Q3C6JLLV1lwjqmTWLQ4m5M02BqBKmQzcyt66wY925kykg2pQyB1t!1872529297!468271380!1229457621681", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
         java.net.SocketInputStream.socketRead0(Native Method)
         java.net.SocketInputStream.read(SocketInputStream.java:129)
         oracle.net.ns.Packet.receive(Unknown Source)
         oracle.net.ns.DataPacket.receive(Unknown Source)
         oracle.net.ns.NetInputStream.getNextPacket(Unknown Source)
         oracle.net.ns.NetInputStream.read(Unknown Source)
         oracle.net.ns.NetInputStream.read(Unknown Source)
         oracle.net.ns.NetInputStream.read(Unknown Source)
         oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1099)
         oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1070)
         oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:478)
         oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
         oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
         oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10622)
         weblogic.jdbc.wrapper.PreparedStatement.executeBatch(PreparedStatement.java:157)
         org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:58)
         org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:195)
         org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:230)
         org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:141)
         org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:296)
         org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
         org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1009)
         org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:356)
         org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106)
         com.bharosa.common.hibernate.HiberDBMgr.commitTransaction(HiberDBMgr.java:293)
         com.bharosa.common.db.BharosaDBMgr.endSession(BharosaDBMgr.java:243)
         com.bharosa.common.dataaccess.DataAccessMgr.endSession(DataAccessMgr.java:132)
         com.bharosa.vcrypt.tracker.impl.VCryptTrackerImpl.updateLog(VCryptTrackerImpl.java:1048)
         com.bharosa.vcrypt.tracker.impl.VCryptTrackerImpl.updateLog(VCryptTrackerImpl.java:622)
         com.bharosa.client.BharosaHelper.fingerPrintFlash(BharosaHelper.java:203)
         com.bharosa.client.BharosaHelper.fingerPrintBrowser(BharosaHelper.java:155)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.runPreAuthRules(IntegratedAuthDelegateSkeleton.java:239)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.runPreAuthRules(IntegratedAuthDelegateSkeleton.java:214)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthRemoteServlet.invokeService(IntegratedAuthRemoteServlet.java:83)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthRemoteServlet.doPost(IntegratedAuthRemoteServlet.java:40)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
         weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
         weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
         weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
         weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
         weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >

    Hi. Something is seriously ill there. I would ask that you post a full thread dump
    to see what's locking what. You may need an official support case...

  • URGENT: Tomcat, Connection Pool - Issue with web.xml & server.xml

    Folks,
    I am trying to connect to a MS SQL database using Tomcat/JSP but having issues. The code that I am using is as follows:
    Context ic = new InitialContext();
    DataSource ds = (DataSource) ic.lookup("java:comp/env/jdbc/test");
    Connection conn = ds.getConnection();
    Statement stmt = conn.createStatement();
    I have added the following code to my Server.xml:
    <Resource name="jdbc/test" auth="Container" type="javax.sql.DataSource"
    maxActive="100" maxIdle="30" maxWait="10000"
    username="DB_AW_DATA" password="tester" driverClassName="com.microsoft.jdbc.sqlserver.SQLServerDriver"
    url="jdbc:microsoft:sqlserver://192.168.0.1\\Newcastle"/>
    And the complete web.xml
    <?xml version="1.0" encoding="UTF-8" ?>
    <!DOCTYPE web-app (View Source for full doctype...)>
    - <web-app>
    - <resource-ref>
    <description>Resource reference to java.sql.Connection factory defined in server.xml</description>
    <res-ref-name>jdbc/test</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </web-app>
    The error message that I am getting is as follows:
    java.sql.SQLException: Cannot load JDBC driver class 'null'
    What confuses me is that I have placed the following files in Tomcat\common\lib...
    mssqlserver.jar
    msbase.jar
    msutil.jar
    I think this is purely an issue with how I configured server.xml and web.xml
    In the Tomcat documentation it states to put the code in the server.xml - but nested inside the Context element. This is something that I have not done as I am clear what the Context should be..
    Can someone assist...
    <Context path="" docBase="ROOT" debug="0"> ???
    what should be the path and the docBase.
    I have deployed the following application:
    http://localhost:8080/SCWAPP/index.jsp
    THANKS IN ADVANCE FOR ALL SUPPORRT

    you should put the code you typed in server.xml into context.xml
    in the META-INF folder and this will fix your problem.
    the latest tomcat docs detail what to do.

  • Connection pooling issue with compiling with jdk 1.5.0

    A
    javax.naming.NameNotFoundException: Name jdbc is not bound in this Context exception occurs when I run my web app in Tomcat 5 using jdk 1.5. However, I don't get this problem with I use jdk 1.6.0. The mysql connector version is 3.1.1.4 and my server.xml file has been configured correctly. Any suggestions as to why this exception is occurring - I'm assuming it's a version issue but not sure how to solve it!

    Use "java:comp/env/jdbc/DbUser" instead of just "jdbc/DbUser" for datasource config
    See http://www.tek-tips.com/viewthread.cfm?qid=431734
    The mysql connector version is 3.1.1.4Use a more recent jdbc driver
    http://dev.mysql.com/downloads/connector/j/5.0.html
    http://dev.mysql.com/doc/refman/5.0/en/connector-j-versions.html
    Message was edited by:
    java_2006

  • Error in creating a connection pool (No suitable driver)

    I try to create a connection pool in a Weblogic server 7.0 with the following config:
    URL:
    jdbc:oracle:oci9:@db_name
    Driver Classname:
    oracle.jdbc.driver.OracleDriver
    Properties(key=value):
    user=user_name
    password=user_password
    dll=ocijdbc9
    server=db_name
    protocol=oci
    my computer (windows 2000) has installed Oracle 9i client, and this connection
    pool will connect to Oracle 8i server. Besides, I have config classes12.zip in
    the "classpath" and ocijdbc9.dll in the "path" environment variables.
    Can Oracle 9i driver connect to a Oracle 8i server? Or there is other problems?
    Thanks in advance.

    Please try URL = jdbc:oracle:oci8:@db_name... that should be fine.
    Yes, you can connect to 8i oracle database using 9i driver.
    Also, make sure you have classes12.zip in classpath and ocijdbc9.dll in path.
    Thanks,
    Mitesh
    Jacky Ho wrote:
    I try to create a connection pool in a Weblogic server 7.0 with the following config:
    URL:
    jdbc:oracle:oci9:@db_name
    Driver Classname:
    oracle.jdbc.driver.OracleDriver
    Properties(key=value):
    user=user_name
    password=user_password
    dll=ocijdbc9
    server=db_name
    protocol=oci
    my computer (windows 2000) has installed Oracle 9i client, and this connection
    pool will connect to Oracle 8i server. Besides, I have config classes12.zip in
    the "classpath" and ocijdbc9.dll in the "path" environment variables.
    Can Oracle 9i driver connect to a Oracle 8i server? Or there is other problems?
    Thanks in advance.

  • Fatal error while filling connection pool

    I was not getting a connection to an Oracle database and I was getting the following error in cms.log: "FATAL  Connector - Unable to create connection pool for T_Orbis_Oracle: Fatal error while filling connection pool for jdbc:oracle:thin:@MESDB:1521:ASPENB21" where T_Orbis_Oracle is the xMII link name and the database ASPENB21 is on server MESDB. I changed the database username in the link to SYSTEM and I then got a connection and a Created Connection pool message in the log. I then changed back to the username which originally was giving the error and it now also gave me a successful connection. I am now worried that there is an issue in the background which is gradually building up and will begin to fail again as previously. Can anyone explain what is causing this problem and suggest how I can correct it? Thanks, John.

    John,
    Check you have installed the JDBC driver ojdbc14.jar (works for both 9 and 10).
    Also check the server package:
    MII 11.x--->ServerPackage com.lighthammer.Illuminator.connectors.IDBC
    MII 12.x--->com.sap.xmii.Illuminator.connectors.IDBC
    Carefull when you set up the string because some oracle databases have servicenames instead of SID, and the url was different if you use them instead of the SID.
    For services names the url is jdbc:oracle:thin@host:port:SID
    Also check your Network firewall between MII and DB and ports too.
    Oracle9i installs with a number of default accounts.You must unlock all other accounts before using them. Oracle recommends changing all user passwords immediately after installation.
    -Suresh
    Edited by: Suresh Hiremath on Jul 29, 2009 8:20 AM

  • A question about creating a Connection pool that uses Oracle JDBC

    Dear all,
    I have an issue with creating a connection pool within a web application in order to be used by several servlets. I appreciate if you could kindly give me a hand.
    I'm using:
    Web server: Apache-tomcat: 6.0.18
    Oracle Database 11g Enterprise: 11.1.0.6.0 - Production
    Operating system: Linux (ubuntu 8.10)
    IDE: Sun Netbeans
    Oralce JDBC Drivers: 11.1.0.7.0-Production (ojdbc6.jar and orai18n.jar)
    JDK 1.6
    Usually, just for creating a connection to my database (without using a connection pool), I proceed in the following way:
    String dbURL = "jdbc:oracle:thin:@localhost:1521:database01";
    String username = "scott";
    String user_password = "tiger";
    String userSqlQuery = "SELECT * FROM mytable";
    Connection connection = DriverManager.getConnection (dbURL, username, user_password);
    Statement statement = connection.createStatement();
    statement.executeUpdate(query_text);This works pretty well allowing to communicate with my oracle database. By this method I have run several projects
    with different queries (SELECT, INSERT, UPDATE, DELETE ,etc.) and each time it worked without any problem and
    returned the result of the query. Therefore I think that there is no problem with JDBC drivers
    However, when I want to create a connection pool, it seems that the lookup method cannot locate Oracle JDBC drivers. That is,
    try
         InitialContext ic = new InitialContext();
         Context envContext  = (Context)ic.lookup("java:/comp/env");
         dataSource = (DataSource)envContext.lookup("jdbc/oracle11gEnterprise");
           Connection connection = dataSource.getConnection();
    catch (Exception e)
         e.printStackTrace();
    }Just after calling dataSource.getConnection() the java.lang.NullPointerException is thrown.
    Any idea?
    Thanks in advance,
    And for your information, here are context.xml and web.xml files for my project
    Here is my context.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <Context antiJARLocking="true" path="/WebApplication1">
        <Resource name="jdbc/oracle11gEnterprise"
              scope="Shareable"
              type="javax.sql.DataSource"
              auth="Container"
              description="Oracle Database 11g Enterprise"
              maxActive="100"
              maxIdle="30"
              maxWait="10000"
              removeAbandoned="true"
              removeAbandonedTimeout="60"
              logAbandoned="true"
              url="jdbc:oracle:thin:@localhost:1521:database01"
              username="scott"
              password="tiger" />
    </Context>my web.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
        <ConsumeOutput>false</ConsumeOutput>
        <resource-ref>
            <res-ref-name>jdbc/oracle11gEnterprise</res-ref-name>
            <res-type>javax.sql.DataSource</res-type>
            <res-auth>Container</res-auth>
        </resource-ref>
        <!--
            .  And here as usual I write servlet definition and url mappings
        -->   

    nobody?

  • Problem creating a connection pool for mssql server

    Hi
    i downloaded the microsoft type 4 driver for JDBC and i have installed it. now i am trying to create a connection pool for MS Sql server but each time i ping i keep getting an error telling me
    Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection could not be allocated because: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket
    please can someone help out on this
    Ifeanyichukwu

    I assume that you installed the driver correctly. You did go into the app sever admin and set the JVM path? You do this by going to Application Server | JVM Settings | Path Settings and putting in an entry for Classpath Prefix.
    If that is done and it's not something basic like your database isn't turned on, then it must be your settings. To to Sun's site and search for dbping. http://developers.sun.com/prodtech/appserver/utilities/dbping/dbping_overview.html
    Deploy this program and run it. It is a very simple tool that lets you test different property settings. Play around with different settings until you get a ping.
    If that doesn't work post your connect pool settings.
    Good luck
    Mike

  • How to create a connection pooling in Netbeans 6.0 using the oracle driver

    hi all,
    I am using Netbeans 6.0. Apache Tomcat 6.0.14 server, oracle 9i.
    I tried to create a connection pooling using tomcat web server.
    I have included the following code in context.xml and web.xml.
    CONTEXT.XML:
    <?xml version="1.0" encoding="UTF-8"?>
    <Context path="/network1">
    <Resource name="jdbc/myoracle"
    auth="Container"
    type="javax.sql.DataSource"
    username="scott"
    password="tiger"
    factory="BasicDataSourceFactory"
    driverClassName="oracle.jdbc.OracleDriver"
    url="jdbc:odbc:thin:@127.0.0.1:1521:mydb"
    maxActive="20"
    maxIdle="10"
    maxwait="-1"/>
    </Context>
    WEB.XML:
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
    <session-config>
    <session-timeout>
    30
    </session-timeout>
    </session-config>
    <welcome-file-list>
    <welcome-file>index.jsp</welcome-file>
    </welcome-file-list>
    <resource-ref>
    <description>Oracle Datasource example</description>
    <res-ref-name>jdbc/myoracle</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </web-app>
    After that i have included the following JDBC driver's jar files in the $Catalina_Home/lib folder.
    classes 111.jar,
    classes 111_g.jar
    classes12.jar
    classes 12_g.jar
    classes12dms.jar
    classes12dms_g.jar
    nls_charset11.jar
    nls_charset12.jar
    ocrs12.jar
    ojdbc14.jar
    ojdbc14_g.jar
    Then i stop the tomcat web server and start it again.
    In jsp page i have included the following code:
    Context ctx=new InitialContext();
    Context envctx=(Context)ctx.lookup("java:comp:env");
    DataSource ds=(DataSource)envctx.lookup("jdbc/myoracle");
    Connection con=ds.getConnection(); ----->(In this line an error occured that Connection class cannot be found.)
    please help me how to create a connection pooling and rectify the error in conneciton.
    Thanks in advance

    Please refer
    http://www.netbeans.org/kb/60/web/customer-book.html

  • How to Create a connection pool in OSB java callout

    Dear Team,
    In our project, we need read some data from DB, and do corresponding operation. currently, we need setup the connection first, execute the SQL, and close the connection.
    But the concurrency of call is very high, is there a way to create a connection pool, then we can use the connection pool to get the connection and execute the SQL, then return the connection to the pool.
    if connection pool is not available, is there any way to create the connection outside the java callout, that we can just execute the SQL in java callout.
    The OSB version is 11.1.1.6.0
    Thanks.
    Best Regards,
    Raysen Jia
    Edited by: Raysen Jia on Oct 16, 2012 8:44 AM

    Hi Team,
    Thanks for your help.
    What I need is not only the db connection, may be other kind of things, such as read configuration from file...
    If I write the code in java callout with static java method to create and close the connection, each time when request come in, OSB will create a new connection (or read the file), I think it's not the best practice to do this kind of work.
    I think the weblogic is running in JVM, is there any way we can define variables or new object in the JVM directly?

  • Error using mySQL connection Pool

    I see the following error when my application uses the connection pool - can anyone explain this ?
    INFO: CORE3282: stdout: =======================>ERROR :com.sun.enterprise.repository.J2EEResourceException
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResourcePool.initPool(IASNonSharedResourcePool.java:416)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResourcePool.internalGetResource(IASNonSharedResourcePool.java:625)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource(IASNonSharedResourcePool.java:520)
    INFO: CORE3282: stdout: java.lang.NoSuchMethodException: setdataSourceName

    Hi,
    You have used dataSourceName property while creating a connection pool.This property is not required to be set while creating a connection pool for MySql
    Use the following properties:
    <property name="serverName" value="<name of server>"
    <property name="port" value="<port number>"
    <property name="DatabaseName" value="<your db name>"
    <property name="User" value="<user name>"
    <property name="Password" value="<passwd>"
    Get back in case of any issues

Maybe you are looking for

  • Airport Express shows green, no signal.

    So after finally moving into my new apartment, I decided to finally go wireless with my iMac G5 and my girlfriend's eMac G4. We practically skipped into the Apple store, purchased an Airport Express card and two airport extreme cards. And then it all

  • Oracle Linux 6.3 - restarts on shutdown

    Hi All, I installed Oracle Linux 6.3 on a standalone laptop. I updated it fully. Installed Oracle Database11gR2 and everything works perfect The OS reboots on shutdown command. There is no "wake up on LAN" or "Automatic Power Up". Checked BIOS - didn

  • Get informatin back?? Medical info was there  Please HELP ME thanks

    i have an itouch and I synced it incorrectly it appears since I erased my calendar for the last year and half along with all my contact. i had put medical notes on days in question and really could remember any of it Is there a way to get this inform

  • Cisco Unity 3/4 startup

    I am trying to settle a bet with this question.  Did Unity 3/4 have a sound that played over the PC Speaker on the server when the actually Unity service started up fully to the green checkmark?  I know this is silly so thanks in advance for answerin

  • Premiere Elemenents 13 frequent crashes

    Hi, I just moved to Premiere Elements 13. I am getting crashes all the time when trying to just view my timeline video. It is really unusable because almost everything makes it to crash. I used Premiere Elements 11 before and did not see this many pr