Unable to set-up sybase connection pool for wls6.1

Hi All,
I am trying to set-up sybase connection pool in wls6.1 using the supplied jConnect driver (don't know the version of the driver). In diff places I am seeing diff opinions about the settings. It is really frustrating because BEA doc shies away from documenting just the sybase details although it provides details about Oracle, informix and SQL Server.
I just want to know these
1. the xml string for the connection pool
2. which config file should have it (web.xml or config.xml or something else?)
thanks a ton in advance
~rakesh

Hi,
I've already solve the problem. I did the following:
set the Url to be: jdbc:oracle:thin:@hostname:port:SID
set username
set password
add oracle.jdbc.drivers.OracleDriver into the JVM options -Djdbc.drivers
restart the server
test the connection
it works :)

Similar Messages

  • Set up DB Connection Pool for Oracle DataBase Using Java App Server8

    Hi,
    In the Admin Console of Java App Server 8, I tried to create a connection pool for the oracle database. I chose Resource Type to be "javax.sql.ConnectionPoolDataSource" and the Vendor is Oracle. So the Data Source Class Name is filled by the system to be "oracle.jdbc.pool.OracleConnectionPoolDataSource". Now, I set up the class path to point to the database driver class "sun.jdbc.odbc.JdbcOdbcDriver" and also the to the Data Source Class Name. Also I set up the JVM options in the console. Restart the server, and then try to ping to the database, but get the error:
    Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection could not be allocated because: No suitable driver
    I don't understand what else I should do and why this error is coming?
    Please help me out.
    Thank you
    Regards,
    Sarah

    Hi,
    I've already solve the problem. I did the following:
    set the Url to be: jdbc:oracle:thin:@hostname:port:SID
    set username
    set password
    add oracle.jdbc.drivers.OracleDriver into the JVM options -Djdbc.drivers
    restart the server
    test the connection
    it works :)

  • Error creating connection pool for WLS6.1 for DB2 connect

    Hi,
    We have installed licensed copy of Weblogic 6.1 Applciation server on HPUX 11.0.
    Our backend system is DB2 on Mainframe (S/390). We have installed DB2Connect
    JDBC driver ver 7.1 on HPUX. While creating pool throught weblogic console with
    following parameters:
    Name: DB2Pool
    URL:jdbc:db2:INFOSYSG
    Driver Classname: COM.ibm.db2.jdbc.app.DB2Driver
    Properties:
    user=jargon
    password=jargon
    Then appropriate Target was selected.
    When server was started following error was recevied on console:
    "CLI0647E Error allocating DB2 environment handle, rc=db2jdbc"
    Any pointers to the solution are welcome.
    Regards,
    Punam Chordia
    Infosys Technologies Ltd, Pune
    Phone: 91-20-2932000 Ext. 5650
    Fax: 91-20-2932832

    Hi,
    thank you for your answer, but i already fixed my problem.
    i simply put the profile-script of the db2-instance into the start script of the
    weblogic server.
    i didn´t really figure out so far which variable was missing, but now it works.
    unfortunately i found that this driver supports only 2 connections at the same
    time when using jdk 1.3.0 :-(.
    Regards,
    Andreas Koch
    Netfidelity Consulting GmbH
    tel +49 211 6012330
    fax +49 211 6012320
    mail [email protected]
    Joseph Weinstein <[email protected]> wrote:
    If you can connect to DB2 on your own, using their
    driver and their JDBC examples, then show me the code
    that works, and show me the classpath and OS environment
    you're running in, and I'll show you what should be
    done for the server.
    Andreas Koch wrote:
    Hi,
    unfortunately i have the same problem and found no solution so far.
    you may check my start-script, but in my eyes all db/2 stuff shouldbe
    found.
    thanks for urgent help
    Andreas Koch
    NetFidelity Consulting Gmbh
    [email protected]
    "Slava Imeshev" <[email protected]> schrieb im Newsbeitrag
    news:[email protected]...
    Hi Punam,
    You need to make sure that all driver's native libraries are
    available to the Weblogic. Check if SQLLIB\bin is on the path
    and let us know if it helps.
    Regards,
    Slava Imeshev
    "Punam" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    We have installed licensed copy of Weblogic 6.1 Applciation server
    on
    HPUX
    11.0.
    Our backend system is DB2 on Mainframe (S/390). We have installedDB2Connect
    JDBC driver ver 7.1 on HPUX. While creating pool throught weblogic
    console
    with
    following parameters:
    Name: DB2Pool
    URL:jdbc:db2:INFOSYSG
    Driver Classname: COM.ibm.db2.jdbc.app.DB2Driver
    Properties:
    user=jargon
    password=jargon
    Then appropriate Target was selected.
    When server was started following error was recevied on console:
    "CLI0647E Error allocating DB2 environment handle, rc=db2jdbc"
    Any pointers to the solution are welcome.
    Regards,
    Punam Chordia
    Infosys Technologies Ltd, Pune
    Phone: 91-20-2932000 Ext. 5650
    Fax: 91-20-2932832
    Name: startWebLogic.sh
    startWebLogic.sh Type: Kornshell Script File (application/x-unknown-content-type-mks_shell)
    Encoding: x-uuencode

  • Setting up connection pool for cloudscape 10 embedded database

    I got problem with setting connection pool via admin console for cloudscape 10 embedded in j2ee 1.4 (Application server 8.1), what im doing is:
    -in resources/jdbc/ConnectionPools i add a new pool
    - datasource classname i set up as: "org.apache.derby.jdbc.EmbeddedXADataSource"
    -resource type: "javax.sql.XADataSource"
    -DatabaseName: "jdbc:derby:D:\\Programowanie\J2EE\domains\domain1\config\notesData"
    -set no password and user, becouse i havet set this in database
    and when i ping to that datebase i got error:"Operation 'pingConnectionPool' failed in 'resources' Config Mbean."
    when i change Datasource Classname to: "org.apache.derby.jdbc.EmbeddedDataSource", this error occur:
    Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection object cannot be null
    what im doing wrong? i look everywhere and i cant find solution to my problem...hope you can help me.
    Thanks,
    Krystian

    Amit wrote:
    >
    "whats are the settings (URL, driver, properties) required to set up a connection pool for DB2 on OS/390 ?I'm using "COM.ibm.db2.jdbc.app.DB2Driver" as DB2 driverHi. If you can successfully use that driver with one of it's simple
    JDBC example programs, then show me that example, at least the
    part that makes the connection, and I'll show you how to define a pool.
    Joe
    PS: Folks: BEA WebLogic is expanding rapidly, with both entry and advanced positions
    for people who want to work with Java, XML, SOAP and E-Commerce infrastructure products.
    We have jobs at Nashua NH, Liberty Corner NJ, San Francisco and San Jose CA.
    Send resumes to [email protected]

  • Setting up connection pool for DB2

    "whats are the settings (URL, driver, properties) required to set up a connection pool for DB2 on OS/390 ?I'm using "COM.ibm.db2.jdbc.app.DB2Driver" as DB2 driver

    Amit wrote:
    >
    "whats are the settings (URL, driver, properties) required to set up a connection pool for DB2 on OS/390 ?I'm using "COM.ibm.db2.jdbc.app.DB2Driver" as DB2 driverHi. If you can successfully use that driver with one of it's simple
    JDBC example programs, then show me that example, at least the
    part that makes the connection, and I'll show you how to define a pool.
    Joe
    PS: Folks: BEA WebLogic is expanding rapidly, with both entry and advanced positions
    for people who want to work with Java, XML, SOAP and E-Commerce infrastructure products.
    We have jobs at Nashua NH, Liberty Corner NJ, San Francisco and San Jose CA.
    Send resumes to [email protected]

  • Read data using 2 diff connection pool for same DB folder in physical layer

    Hi All,
    i am using two connection pool which have different dsn connection information (both are directed to different database name or database server)..
    so if i view the data of any table, a prompt will come asking for the connection pool, so how do i automize it....?
    how do i set the different connection pool for different tables?
    please let me know if u need further informtaion to understand my problem..
    thnx...

    thnx Stijn..
    yupe that i know...
    actually i have total of around 300 tables in physical layer (in both the schemas..) , around 12 fact and 100 dimension tables in bmm and same in the presentation layer...
    so i think u can guess how many joins and other stuff, i have made in my bmm layer..
    if now i will start modifying all this it will take lot of time...
    i am just wondering that there is no alternative for this...
    as when i check my data from the physical layer then a prompt ask for the connection pool (i have already made two connection pool..) so there could be some alternative way to automize the default connection pool setting for the tables/schemas folders in case if more than one connection pool exits under the same database in the physical layer...
    isn't it?
    thnx again..

  • Unable create Connection pool for Oracle apps Adapter.

    Hi All,
    We are trying to create a connection pool for Oracle Apps adapter in 11G SOA suite.
    However during the process getting the following error:
    An error occurred during activation of changes, please see the log for details.
    A <jndi-name> is specified for the resource adapter bean in weblogic-ra.xml, however no <resourceadapter-class> element is specified in ra.xml
    Can any one help us on this.
    Thanks
    Parker.

    Please refer section "Configuring Connection Information" at below link -
    http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10537/T430238T430340.htm#T464886
    Regards,
    Anuj

  • Cannot create a sybase connection pool

    I am trying to migrate from Orion app server to Sun One appserver. Here is how I define the connection pool for orion
         <data-source class="com.evermind.sql.DriverManagerDataSource"
                                       name="TestPool"
                                       location="jdbc/rumbaDataSource"
                                       xa-location="jdbc/xa/rumbaPool"
                                       ejb-location="jdbc/rumbaPool"
                                       connection-driver="com.sybase.jdbc2.jdbc.SybXADataSource"
                                       connection-retry-interval="60"
                                       username="test"
                                       password="test"
                                       url="jdbc:sybase:Tds:3.23.24.25:20000/abc?HOSTNAME=rumba"
                                       inactivity-timeout="300"
                                       min-connections="6"
                                       max-connections="75"
         />
    This is how my connection pool appears in Sun ONE
    <jdbc-connection-pool steady-pool-size="8" max-pool-size="32" max-wait-time-in-millis="60000" pool-resize-quantity="2" idle-timeout-in-seconds="300" is-isolation-level-guaranteed="false" is-connection-validation-required="false" connection-validation-method="auto-commit" fail-all-connections="false" datasource-classname="com.sybase.jdbc2.jdbc.SybXADataSource" name="TestPool">
    <property value="3.23.24.25" name="serverName"/>
    <property value="20000" name="portNumber"/>
    <property value="jdbc:sybase:Tds:" name="networkProtocol"/>
    <property value="test" name="user"/>
    <property value="test" name="password"/>
    <property value="abc" name="databaseName"/>
    </jdbc-connection-pool>
    But, I am unable to make a connection using this connection pool

    Here is the exception
    SEVERE: RAR5041:Cannot get jdbc connection
    com.sun.enterprise.repository.J2EEResourceException
    java.lang.NoSuchMethodException: seturl
    at com.sun.enterprise.repository.JdbcConnectionPool.createDataSource(Jdb
    cConnectionPool.java:243)
    at com.sun.enterprise.resource.JdbcUrlAllocator.createResource(JdbcUrlAl
    locator.java:80)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.createSteadyReso
    urces(IASNonSharedResourcePool.java:856)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.initPool(IASNonS
    haredResourcePool.java:416)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.internalGetResou
    rce(IASNonSharedResourcePool.java:625)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource(IASN
    onSharedResourcePool.java:520)
    at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolM
    anagerImpl.java:263)
    at com.sun.enterprise.resource.JdbcXAConnection.<init>(JdbcXAConnection.
    java:74)
    at com.sun.enterprise.resource.Jdbc10XaAllocator.createResource(Jdbc10Xa
    Allocator.java:94)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.createSteadyReso
    urces(IASNonSharedResourcePool.java:856)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.initPool(IASNonS
    haredResourcePool.java:416)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.internalGetResou
    rce(IASNonSharedResourcePool.java:625)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource(IASN
    onSharedResourcePool.java:520)
    at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolM
    anagerImpl.java:263)
    at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerIm
    pl.java:170)
    at com.sun.enterprise.resource.JdbcDataSource.internalGetConnection(Jdbc
    DataSource.java:241)
    at com.sun.enterprise.resource.JdbcDataSource.getConnection(JdbcDataSour
    ce.java:124)
    at samples.jdbc.simple.servlet.GreeterDBLogDisplayServlet.doGet(Unknown
    Source)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.apache.catalina.core.StandardWrapperValve.invokeServletService(St
    andardWrapperValve.java:720)
    at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrap
    perValve.java:118)
    at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperVa
    lve.java:278)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
    alve.java:274)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
    a:505)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
    alve.java:212)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
    a:505)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
    ava:203)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
    a:505)
    at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProce
    ssor.java:157)
    at com.iplanet.ias.web.WebContainer.service(WebContainer.java:598)
    INFO: CORE3282: stdout: - Could not interact with the database
    INFO: CORE3282: stdout: - Exception: java.sql.SQLException: com.sun.enterprise.r
    epository.J2EEResourceException
    WARNING: CORE3283: stderr: at com.sun.enterprise.repository.JdbcConnectionP
    ool.createDataSource(JdbcConnectionPool.java:238)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.JdbcUrlAllocator.
    createResource(JdbcUrlAllocator.java:80)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResou
    rcePool.createSteadyResources(IASNonSharedResourcePool.java:856)
    INFO: CORE3282: stdout: java.lang.NoSuchMethodException: seturl
    INFO: CORE3282: stdout: Closing statement...
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResou
    rcePool.initPool(IASNonSharedResourcePool.java:416)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResou
    rcePool.internalGetResource(IASNonSharedResourcePool.java:625)
    INFO: CORE3282: stdout: - Could not close the statement and connection
    INFO: CORE3282: stdout: GreeterDBLogDisplayServlet is all done
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResou
    rcePool.getResource(IASNonSharedResourcePool.java:520)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.PoolManagerImpl.g
    etResourceFromPool(PoolManagerImpl.java:263)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.JdbcXAConnection.
    <init>(JdbcXAConnection.java:74)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.Jdbc10XaAllocator
    .createResource(Jdbc10XaAllocator.java:94)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResou
    rcePool.createSteadyResources(IASNonSharedResourcePool.java:856)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResou
    rcePool.initPool(IASNonSharedResourcePool.java:416)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResou
    rcePool.internalGetResource(IASNonSharedResourcePool.java:625)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResou
    rcePool.getResource(IASNonSharedResourcePool.java:520)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.PoolManagerImpl.g
    etResourceFromPool(PoolManagerImpl.java:263)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.PoolManagerImpl.g
    etResource(PoolManagerImpl.java:170)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.JdbcDataSource.in
    ternalGetConnection(JdbcDataSource.java:241)
    WARNING: CORE3283: stderr: at com.sun.enterprise.resource.JdbcDataSource.ge
    tConnection(JdbcDataSource.java:124)
    WARNING: CORE3283: stderr: at samples.jdbc.simple.servlet.GreeterDBLogDispl
    ayServlet.doGet(Unknown Source)
    WARNING: CORE3283: stderr: at javax.servlet.http.HttpServlet.service(HttpSe
    rvlet.java:740)
    WARNING: CORE3283: stderr: at javax.servlet.http.HttpServlet.service(HttpSe
    rvlet.java:853)
    WARNING: CORE3283: stderr: at org.apache.catalina.core.StandardWrapperValve
    .invokeServletService(StandardWrapperValve.java:720)
    WARNING: CORE3283: stderr: at org.apache.catalina.core.StandardWrapperValve
    .access$000(StandardWrapperValve.java:118)
    WARNING: CORE3283: stderr: at org.apache.catalina.core.StandardWrapperValve
    $1.run(StandardWrapperValve.java:278)
    WARNING: CORE3283: stderr: at java.security.AccessController.doPrivileged(N
    ative Method)
    WARNING: CORE3283: stderr: at org.apache.catalina.core.StandardWrapperValve
    .invoke(StandardWrapperValve.java:274)
    WARNING: CORE3283: stderr: at org.apache.catalina.core.StandardPipeline.inv
    oke(StandardPipeline.java:505)
    WARNING: CORE3283: stderr: at org.apache.catalina.core.StandardContextValve
    .invoke(StandardContextValve.java:212)
    WARNING: CORE3283: stderr: at org.apache.catalina.core.StandardPipeline.inv
    oke(StandardPipeline.java:505)
    WARNING: CORE3283: stderr: at org.apache.catalina.core.StandardHostValve.in
    voke(StandardHostValve.java:203)
    WARNING: CORE3283: stderr: at org.apache.catalina.core.StandardPipeline.inv
    oke(StandardPipeline.java:505)
    WARNING: CORE3283: stderr: at com.iplanet.ias.web.connector.nsapi.NSAPIProc
    essor.process(NSAPIProcessor.java:157)
    WARNING: CORE3283: stderr: at com.iplanet.ias.web.WebContainer.service(WebC
    ontainer.java:598)

  • Unable to start the Universal Connection Pool error

    Hi,
    I am trying to deploy two instances of one and the same web application on Tomcat 6. I have application test.war, I have copied and renamed it to test2.war and moved both wars in Tomcat' webapps folder. One of those (which Tomcat decides to start first) correctly gets connection from PoolDataSourceFactory.getPoolDataSource() and works fine, but the second throws this exception while trying to get database connection.
    Please help,
    Thanks
    java.sql.SQLException: Unable to start the Universal Connection Pool: java.sql.SQLException: Unable to start the Universal Connection Pool: oracle.ucp.UniversalConnectionPoolException: MBean exception occurred while registering or unregistering the MBean
    at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:541)
    at oracle.ucp.jdbc.PoolDataSourceImpl.throwSQLException(PoolDataSourceImpl.java:587)
    at oracle.ucp.jdbc.PoolDataSourceImpl.startPool(PoolDataSourceImpl.java:276)
    at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:646)
    at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:613)
    at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:607)
    at com.avalonsql.core.db.connection.ConnectionWrapper.<init>(ConnectionWrapper.java:26)
    ... 31 more
    Caused by: java.sql.SQLException: Unable to start the Universal Connection Pool: oracle.ucp.UniversalConnectionPoolException: MBean exception occurred while registering or unregistering the MBean
    at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:541)
    at oracle.ucp.jdbc.PoolDataSourceImpl.throwSQLException(PoolDataSourceImpl.java:587)
    at oracle.ucp.jdbc.PoolDataSourceImpl.startPool(PoolDataSourceImpl.java:247)
    ... 35 more
    Caused by: oracle.ucp.UniversalConnectionPoolException: MBean exception occurred while registering or unregistering the MBean
    at oracle.ucp.util.UCPErrorHandler.newUniversalConnectionPoolException(UCPErrorHandler.java:421)
    at oracle.ucp.util.UCPErrorHandler.newUniversalConnectionPoolException(UCPErrorHandler.java:389)
    at oracle.ucp.admin.UniversalConnectionPoolManagerMBeanImpl.getUniversalConnectionPoolManagerMBean(UniversalConnectionPoolManagerMBeanImpl.java:149)
    at oracle.ucp.jdbc.PoolDataSourceImpl.startPool(PoolDataSourceImpl.java:242)
    ... 35 more
    Caused by: java.security.PrivilegedActionException: javax.management.InstanceAlreadyExistsException: oracle.ucp.admin:name=UniversalConnectionPoolManagerMBean
    at java.security.AccessController.doPrivileged(Native Method)
    at oracle.ucp.admin.UniversalConnectionPoolManagerMBeanImpl.getUniversalConnectionPoolManagerMBean(UniversalConnectionPoolManagerMBeanImpl.java:136)
    ... 36 more
    Caused by: javax.management.InstanceAlreadyExistsException: oracle.ucp.admin:name=UniversalConnectionPoolManagerMBean
    at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
    at oracle.ucp.admin.UniversalConnectionPoolManagerMBeanImpl$2.run(UniversalConnectionPoolManagerMBeanImpl.java:142)
    ... 38 more

    I was getting the following exception.. However after setting the property ConnectionFactoryClassName, it went off..
    Caused by: java.sql.SQLException: Invalid Universal Connection Pool configuration: java.sql.SQLException: Unable to create factory class instance with provided factory class name: java.lang.ClassNotFoundException:
         at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:541)
         at oracle.ucp.jdbc.PoolDataSourceImpl.throwSQLException(PoolDataSourceImpl.java:587)
         at oracle.ucp.jdbc.PoolDataSourceImpl.createUniversalConnectionPool(PoolDataSourceImpl.java:523)
         at oracle.ucp.admin.UniversalConnectionPoolManagerBase.createConnectionPool(UniversalConnectionPoolManagerBase.java:554)
         ... 92 more
    Caused by: java.sql.SQLException: Unable to create factory class instance with provided factory class name: java.lang.ClassNotFoundException:
         at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:541)
         at oracle.ucp.jdbc.PoolDataSourceImpl.throwSQLException(PoolDataSourceImpl.java:587)
         at oracle.ucp.jdbc.PoolDataSourceImpl.initConnectionFactory(PoolDataSourceImpl.java:2457)
         at oracle.ucp.jdbc.PoolDataSourceImpl.createUniversalConnectionPool(PoolDataSourceImpl.java:386)
         ... 93 more
    Caused by: java.lang.ClassNotFoundException:
         at java.lang.Class.forNameImpl(Native Method)
         at java.lang.Class.forName(Class.java:169)
         at oracle.ucp.jdbc.PoolDataSourceImpl.initConnectionFactory(PoolDataSourceImpl.java:2444)
         ... 94 more
    Edited by: user7953709 on Aug 26, 2011 1:08 AM

  • Issue in setting up a connection pool in Glassfish

    Hello,
    I'm having an issue in setting up a connection pool in Glassfish. Previously I did it succesfully when I installed Glassfish in a Windows Server machine, but now I'm trying to do the same thing on a Linux machine and it's not working.
    Glassfish version is: Glassfish server open source edition 3.1.1 (build 12)
    The machine is a AWS machine running Amazon Linux AMI
    Oracle Database is Oracle 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option
    The Oracle client installed on the machine is Release 11.2.0.3.0 Production
    Java version is: Java(TM) SE Runtime Environment (build 1.7.0_02-b13)
    I've created the pool with the following options:
    Resource Type: javax.sql.DataSource
    Datasource classname: oracle.jdbc.pool.OracleDataSource
    And as additional properties (apart from User and Password) I put as URL jdbc:oracle:oci8:@EVOREAD
    The TNS file is correct and I can connect without any problem using sqlplus. I already copied the ojdbc6.jar in the /opt/Glassfish3/Glassfish/lib folder and I already restarted Glassfish server. Basically I did all the same steps that I did in the Windows machine, but in the Linux machine I always receive the following error:
    java.lang.UnsatisfiedLinkError: no ocijdbc11 in java.library.path no ocijdbc11 in java.library.path
    I needed to create also a connection pool to a MySql Database and basically I did exactly the same steps (apart of course using all the parameters needed for MySql and the proper connector) and it worked immediately.
    Anyone can help me?

    You are using an OCI driver? You can either revert to using a thin client, or install the SQL client binaries and add its lib directory to the LD_LIBRARY_PATH.

  • Connection Pools for DB2 UDB 8.2 on a SUN AS 8.1

    Hi,
    has somebody experience or knows a place where I can get more information in setting up a connection pool to a DB2 UDB 8.2 database from a SUN AS 8.1 server?
    I'm struggling now for some weeks to get this working, but it doesn't work. I've tried the JDBC JAR's delivered with DB2 but get configuration errors. When I use the JDBC JAR's mentioned in the SUN AS documentation, it seems that the SUN AS 8.1 opens a connection, which is refused on the DB2 side.
    The setup of a connection pool to a Postgres DB worked directly. The connection pool is correctly setup in the SUN AS but the ping doesn't work.
    Hope somebody can help.
    Regards

    Hi Jagadish,
    added the finest to connector and resource-adapter. Here is the output:
    [#|2006-01-16T09:03:14.540+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
    [#|2006-01-16T09:05:38.556+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ConnectorServiceImpl :: checkAndLoadResource resolved to load Db2Pool|#]
    [#|2006-01-16T09:05:38.556+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|isReferenced in DASResourcesUtil:: Db2Pool|#]
    [#|2006-01-16T09:05:38.556+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getConnectionFromConnectorRuntime :: true|#]
    [#|2006-01-16T09:05:38.556+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|isReferenced in DASResourcesUtil:: Db2Pool|#]
    [#|2006-01-16T09:05:38.556+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getConnectionFromConnectorRuntime :: true|#]
    [#|2006-01-16T09:05:38.587+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|isReferenced in DASResourcesUtil:: Db2Pool|#]
    [#|2006-01-16T09:05:38.587+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getConnectionFromConnectorRuntime :: true|#]
    [#|2006-01-16T09:05:38.587+0100|WARNING|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|RAR6017 : Failed to get connection pool object via JNDI lookup : Db2Pool|#]
    [#|2006-01-16T09:05:38.587+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|
    com.sun.enterprise.connectors.ConnectorRuntimeException: This pool is not bound in JNDI :
         at com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.obtainManagedConnectionFactory(ConnectorConnectionPoolAdminServiceImpl.java:949)
         at com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.getUnpooledConnection(ConnectorConnectionPoolAdminServiceImpl.java:1089)
         at com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.testConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:507)
         at com.sun.enterprise.connectors.ConnectorRuntime.testConnectionPool(ConnectorRuntime.java:504)
         at com.sun.enterprise.admin.mbeans.ResourcesMBean.pingConnectionPool(ResourcesMBean.java:1908)
         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 com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:302)
         at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:357)
         at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
         at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
         at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
         at $Proxy1.invoke(Unknown Source)
         at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:272)
         at com.sun.enterprise.tools.admingui.util.MBeanUtil.invoke(MBeanUtil.java:148)
         at com.sun.enterprise.tools.admingui.util.MBeanUtil.invoke(MBeanUtil.java:46)
         at com.sun.enterprise.tools.admingui.handlers.CommonHandlers.invokeMBean(CommonHandlers.java:123)
         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 com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.invokeHandler(DescriptorViewHelper.java:863)
         at com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.invokeHandlers(DescriptorViewHelper.java:800)
         at com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.dispatchEvent(DescriptorViewHelper.java:775)
         at com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.execute(DescriptorViewHelper.java:291)
         at com.sun.enterprise.tools.guiframework.view.DescriptorViewBeanBase.execute(DescriptorViewBeanBase.java:192)
         at com.iplanet.jato.view.RequestHandlingViewBase.handleRequest(RequestHandlingViewBase.java:308)
         at com.iplanet.jato.view.ViewBeanBase.dispatchInvocation(ViewBeanBase.java:802)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:740)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:760)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandler(ViewBeanBase.java:571)
         at com.iplanet.jato.ApplicationServletBase.dispatchRequest(ApplicationServletBase.java:957)
         at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:615)
         at com.sun.enterprise.tools.guiframework.view.BaseServlet.processRequest(BaseServlet.java:186)
         at com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:473)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
         at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
         at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:185)
         at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:653)
         at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:534)
         at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doTask(ProcessorTask.java:403)
         at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:55)
    Caused by: javax.naming.NameNotFoundException: Db2Pool not found
    |#]
    [#|2006-01-16T09:05:38.587+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getUnpooledConnection :: obtainManagedConnectionFactory threw exception. SO doing checkAndLoadPoolResource|#]
    [#|2006-01-16T09:05:38.603+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|returning/found the resource adapter from connector registry|#]
    [#|2006-01-16T09:05:38.759+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourceAdapterAdminServiceImpl :: createActiveRA __ds at D:\appserver\sun02\lib\install\applications\__ds|#]
    [#|2006-01-16T09:05:38.759+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|returning/found the resource adapter from connector registry|#]
    [#|2006-01-16T09:05:38.759+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|No classloader available with connector descriptor|#]
    [#|2006-01-16T09:05:38.759+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourceAdapterAdminServiceImpl :: createActiveRA __ds at D:\appserver\sun02\lib\install\applications\__ds loader :: null|#]
    [#|2006-01-16T09:05:38.759+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|returning the connector registry|#]
    [#|2006-01-16T09:05:38.759+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Returing the resourceadapter Config from registry.|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|returning the connector registry|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Returing the resourceadapter Config from registry.|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourceAdapterAdminServiceImpl :: createActiveRA __ds at D:\appserver\sun02\lib\install\applications\__ds ADDING to registry [email protected]0|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Added the active resource adapter to connector registry|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourceAdapterAdminServiceImpl:: createActiveRA __ds at D:\appserver\sun02\lib\install\applications\__ds env =server ? true|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourceAdapterAdminServiceImpl :: createActiveRA __ds at D:\appserver\sun02\lib\install\applications\__ds publishing descriptor __SYSTEM/descriptors/__ds|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|returning the connector registry|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Returing the resourceadapter Config from registry.|#]
    [#|2006-01-16T09:05:38.774+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|current RAConfig In Descriptor []|#]
    [#|2006-01-16T09:05:38.790+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Found/returing Connector descriptor in connector registry.|#]
    [#|2006-01-16T09:05:38.790+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourcesUtil :: isEnabled|#]
    [#|2006-01-16T09:05:38.790+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|ResourcesUtil :: isEnabled JdbcConnectionPool is pool/config - enabled :true|#]
    [#|2006-01-16T09:05:38.790+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;| JdbcConnectionPoolDeployer - deployResource : JdbcConnectionPool calling actualDeploy|#]
    [#|2006-01-16T09:05:38.790+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;| JdbcConnectionPoolDeployer - actualDeployResource : JdbcConnectionPool|#]
    [#|2006-01-16T09:05:38.993+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|parseTransactionSupportString: passed in txSupport =>LocalTransaction|#]
    [#|2006-01-16T09:05:39.009+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|returning/found the resource adapter from connector registry|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setpassword(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , passwd ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setdelimiter(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , # ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setdriverProperties(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , setdriverType#2##setdeferPrepares#false## ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setvalidationMethod(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , table ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setdatabaseName(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , dataBaseName ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setvalidationTableName(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , TABLE_ADDRESS ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setconnectionValidationRequired(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , false ] |#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.024+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setguaranteeIsolationLevel(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , false ] |#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setuser(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , user ] |#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public boolean com.sun.gjc.spi.DSManagedConnectionFactory.equals(java.lang.Object)matches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public javax.resource.spi.ManagedConnection com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject,javax.resource.spi.ConnectionRequestInfo) throws javax.resource.ResourceExceptionmatches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Method public int com.sun.gjc.spi.ManagedConnectionFactory.hashCode()matches with the right arg type|#]
    [#|2006-01-16T09:05:39.040+0100|FINER|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Invokingpublic void com.sun.gjc.spi.ManagedConnectionFactory.setclassName(java.lang.String) on com.sun.gjc.spi.DSManagedConnectionFactorywith value [class java.lang.String  , com.ibm.db2.jcc.DB2SimpleDataSource ] |#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Created MCF object : |#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|poolName : Db2Pool : txSupport : 1|#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Added MCF to connector registry.|#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getUnpooledConnection:: checkAndLoadPoolResource is true|#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getUnpooledConnection :: Now calling obtainManagedConnectionFactory again|#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|Returning the MCF from connector registry.|#]
    [#|2006-01-16T09:05:39.040+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|getUnpooledConnection:: done obtainManagedConnectionFactory again|#]
    [#|2006-01-16T09:05:39.071+0100|FINE|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=11;|using subject: Betreff:
         Principal: user
         Private Authentisierung: javax.resource.spi.security.PasswordCredential@26702a03
    |#]
    I think the exception is thrown because the pool was never allocated. So this exception should be okay.
    Then comes a lot of reflection stuff (at least in my opinion) and finally there is a try to open the connection. What I don't understand is why there is
    [#|2006-01-16T09:05:39.071+0100|FINE| ... |[b]using subject: Betreff:
    'Betreff' is normally the start for a german mail???
    But nevertheless I think I will realize your second suggestion and write a java client which opens a datasource. This make take some time (one or two days).
    THX a lot for your help.
    PS: There is some kind of syntax highlighting error within the exception code. So the rest of the text is also bold. Don't know how to reset that, but I hope it is readable.

  • 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

  • Problem when creating connection pool for Informix

    Hi all,
    could you please help me to create a connection pool for informix?
    I use a com.informix.jdbcx.IfxXADataSource driver and here are the properties
    user=informix
    password=informix
    url=jdbc:informix-sqli://TW010766:1526/vka:informixserver=TW010766
    dataSourceName=TestEntityPool2
    portNumber=1526
    databaseName=vka
    ifxIFXHOST=TW010766
    serverName=vka
    Here is the error message :
    Error during Data Source creation: weblogic.common.ResourceException: DataSource(TestEntity)
    can't be created with non-existent Pool (connection or multi) (TestEntityPool2)
         at weblogic.jdbc.common.internal.JdbcInfo.validateConnectionPool(JdbcInfo.java:127)
         at weblogic.jdbc.common.internal.JdbcInfo.startDataSource(JdbcInfo.java:189)
         at weblogic.jdbc.common.internal.JDBCService.addDeploymentx(JDBCService.java:293)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:270)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:375)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:303)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:256)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:207)
    Could you please tell me what's wrong with the configuration?
    Many thanks in advance.
    Hoang

    Hoang Nguyen wrote:
    For JBuilder :
    URL : jdbc:informix-sqli://tra019746:1526/vka:informixserver=vka
    Driver : com.informix.jdbcx.IfxXADataSource
    username : informix; password : informix
    For WebLogic :
    URL : jdbc:informix-sqli://tra019746:1526/vka:informixserver=vka
    Driver : com.informix.jdbcx.IfxXADataSource
    Properties : password=informix
    user=informixOk. The problem may have to do with your reiterating all the properties below.
    url=jdbc:informix-sqli://tra019746:1526/vka:informixserver=vka
    portNumber=1526
    databaseName=vka
    serverName=vka
    ifxIFXHOST=tra019746All these above are implicit in the URL you give to jBuilder and weblogic.
    Try defining the pool with only the user and password as properties.
    >
    >
    Error:
    Error during Data Source creation: weblogic.common.ResourceException:
    DataSource(TestEntity)
    can't be created with non-existent Pool (connection or multi) (TestEntityPool2)
    at weblogic.jdbc.common.internal.JdbcInfo.validateConnectionPool(JdbcInfo.java:127)
    at weblogic.jdbc.common.internal.JdbcInfo.startDataSource(JdbcInfo.java:189)
    at weblogic.jdbc.common.internal.JDBCService.addDeploymentx(JDBCService.java:293)
    at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:270)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:375)
    Thanks Joe
    Hoang Nguyen wrote:
    Joseph,
    The driver that I use comes from informix.
    I've tried with JBuilder and no problem. JBuilder can connect to informixand
    I can see the tables from JBuilder.
    There's something wrong in the configuration with Weblogic.
    Many thanks for your help.I understand that there's something wrong with the configuration with
    weblogic,
    but the problem is due to a mistake in the input you gave to the pool
    definition,
    and I want to solve that. Please show me the URL, driver name and properties
    you give to JBuilder to make Informix connections. Also, show me the
    first few lines
    that get printend out when you run the weblogic start script. I want
    to see the
    line that prints out the classpath used in the script for starting the
    server.
    thanks,
    Joe
    Joseph Weinstein <[email protected]> wrote:
    Ok, I would like you to download Informix's driver from them, and
    run one of their example programs, just to prove you can connect to
    informix, using their driver, with no weblogic in the picture. We
    have
    to establish that, because that's all weblogic will be doing anyway.
    Once
    we know how to connect to informix via JDBC, we can do weblogic stuff.
    Joe
    Hoang Nguyen wrote:
    Hi,
    I forgot to mention that I'm working with Weblogic server 7 and
    Informix 2000 9.20.
    For the configuration, I followed the example given by Weblogic
    http://edocs.bea.com/wls/docs70/jdbc/thirdparty.html#thirdparty001,
    table 5.2
    Here is the example given by weblogic :
    user=username
    url=jdbc:informix-sqli://dbserver_name_or_ip:port_num/dbname:informixserver=dbserver_name_or_ip
    password=password
    portNumber =port_num;
    databaseName=dbname
    serverName=dbserver_name
    ifxIFXHOST=dbserver_name_or_ip
    If you take a look at the link, you'll see a note :
    "In the Properties string, there is a space between portNumber and=". I've tried
    that but it seems that this bug had been resolved. When I put the
    space,
    I've
    an number exception.
    Thanks for your help.
    Hoang
    Joseph Weinstein <[email protected]> wrote:
    Nguyen Hoang wrote:
    Hi all,
    could you please help me to create a connection pool for informix?
    I use a com.informix.jdbcx.IfxXADataSource driver and here are
    the
    properties
    user=informix
    password=informix
    url=jdbc:informix-sqli://TW010766:1526/vka:informixserver=TW010766
    dataSourceName=TestEntityPool2
    portNumber=1526
    databaseName=vka
    ifxIFXHOST=TW010766
    serverName=vka
    Here is the error message :
    Error during Data Source creation: weblogic.common.ResourceException:DataSource(TestEntity)
    can't be created with non-existent Pool (connection or multi)
    (TestEntityPool2)
    This means the pool was unable to make an informix connection withthe
    properties
    you gave. Please show me the few lines from an informix driver
    example
    program
    that makes a successful JDBC connection to the DBMS you want, andI will
    show
    you how to define a pool for weblogic to do the same.
    Joe
    at weblogic.jdbc.common.internal.JdbcInfo.validateConnectionPool(JdbcInfo.java:127)
    at weblogic.jdbc.common.internal.JdbcInfo.startDataSource(JdbcInfo.java:189)
    at weblogic.jdbc.common.internal.JDBCService.addDeploymentx(JDBCService.java:293)
    at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:270)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:375)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:303)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:256)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:207)
    Could you please tell me what's wrong with the configuration?
    Many thanks in advance.
    Hoang

  • WLS 5.1 with SP11 and Sybase connection pools

    I had posted back in January about an issue with WLS 6.1 and Sybase connection
    pools (see posts 12040 - 12043). This issue has now appeared in WLS 5.1 with
    SP 11. I have backed out SP11, but I'd take advantage of the clustering enhancements
    in this SP. Any suggestions? Would it be possible to get another one off patch
    for SP11?

    Could you fill me in as to what problem you were having. We are also using
    Sybase with WLS5.1 and experience intermittent truncating of resultsets.
    Regards,
    Garvin LeClaire
    [email protected]
    "Pete Auriemma" <[email protected]> wrote in message
    news:3c8669ee$[email protected]..
    >
    I had posted back in January about an issue with WLS 6.1 and Sybaseconnection
    pools (see posts 12040 - 12043). This issue has now appeared in WLS 5.1with
    SP 11. I have backed out SP11, but I'd take advantage of the clusteringenhancements
    in this SP. Any suggestions? Would it be possible to get another one offpatch
    for SP11?

  • Create a dedicated connection pool for initialization blocks

    Hi,
    I'm using OBIEE11.6, then I set a session initialization block in RPD, and this block is based on connection pool '"My_DB".
    "My_CP"'.
    when Consistency Checking it warning as follow:
    Initialization Block 'Authorization' uses Connection Pool '"My_DB".
    "My_CP"' which is used for report queries. This may impact query performance.
    but there is no table under the connection pool "My_CP",so I don't know why it say it's used for report queries? and how to remove the warning?
    any one know it?
    Thank you!

    Hi Leo,
    Generally, when there is only one connection pool for a database in physical layer, the BI Server understands this to be the only connection pool for queries (I do not think this really checks if there are underlying tables. I think this is because there is a way to add tables to a database by right clicking on connection pool and choosing import metadata.).
    As a good practise, when you have init block pointing to a specific database please make sure that you create another connection pool just for the use by init blocks. This would make sure that the report queries and init blocks do not go on a single pool.
    So, for your case, create a second connection pool and point your init blocks to the second one. Yes, you cannot point to the first one as it is kind of reserved by BI Server for reports. (Unless you change this in the Options menu of .rpd)
    Hope this helps.
    Thank you,
    Dhar

Maybe you are looking for