UCCX 8.5.1 Datasource Config

Hey guys,
Currently our UCCX system is connecting to the test database server, but we would like to move this to production.
During testing we are successfully connected using the following JDBC URL:
jdbc:jtds:sqlserver://sw-sqlcorpts02:1433/Cisco_VRU
Now when we plan to move to production, the database guys have given me the following info to use.
Cluster name: SW-CLPR01SQL
Instance:CLPR01SQL1
I've tried the following JDBC URLs but they both have failed:
jdbc:jtds:sqlserver://SW-CLPR01SQL;instanceName=CLPR01SQL1:1433/Cisco_VRU
jdbc:jtds:sqlserver://SW-CLPR01SQL\CLPR01SQL1:1433/Cisco_VRU
My question is: How can we connect to a clustered instance of a database? I'm sure it must be supported since I can't imagine other comapnies aren't using it. I just need to figure out the correct format for connecting to an instance on a cluster sql server.
I'm able to create an ODBC connection to the prod system using servername as: SW-CLPR01SQL\CLPR01SQL1 which tells me my credentials are correct and have the right permissions.
Any help would be appreciated.
Thanks.

Hi Jonathan,
I have to upgrade one customer from UCCX 7.0 SR5 to 8.5 and they are currently using ODBC connector to connect to their CRM oracle based now i need to know how can i configure the ODBC connector in UCCX 8.5 so then i can cofigure the DB in UCCX DB properties. Any doc which explains how to configure ODBC or JDBC connector in UCCX 8.5 to connect to third party DB

Similar Messages

  • Weblogic - deploying of the new application causes the change of the datasource config

    Hi there,
    The description of the issue is:
    I have weblogic domain and some application deployed on it.
    The config.xml for the domain contains following:
      <jdbc-system-resource>
        <name>Pool</name>
        <target>myserver</target>
        <deployment-order>1</deployment-order>
        <descriptor-file-name>Pool-jdbc.xml</descriptor-file-name>
      </jdbc-system-resource>
      <jdbc-system-resource>
        <name>JNDI</name>
        <target>myserver</target>
        <deployment-order>4</deployment-order>
        <descriptor-file-name>JNDI-jdbc.xml</descriptor-file-name>
      </jdbc-system-resource>
    When I tried to deploy/undeploy another application (pretty much simple hello world from netbeans) on the same domain, I found that this part of config changes to:
      <jdbc-system-resource>
        <name>Pool</name>
        <target>myserver</target>
        <deployment-order>1</deployment-order>
        <descriptor-file-name>jdbc/Pool-jdbc.xml</descriptor-file-name>
      </jdbc-system-resource>
      <jdbc-system-resource>
        <name>JNDI</name>
        <target>myserver</target>
        <deployment-order>4</deployment-order>
        <descriptor-file-name>jdbc/JNDI-jdbc.xml</descriptor-file-name>
      </jdbc-system-resource>
    So the path to the files changes by adding jdbc/ in the beginning.
    And then first application fails to start as the path to datasource config has been changed therefore application cannot connect to the database.
    Can anyone tell me why is this happening and how to avoid that? Is there any other configs, which might be affected by deploying another application?
    Thank you,
    Viktor Ozerov

    Hi Viktor,
    As far as I know, the default path for JDBC datasources XML files is ${DOMAIN_HOME}/config/jdbc/, and paths to JDBC datasources in config.xml are added like this "jdbc/FILE.xml", so I think it's a normal behavior.
    Have you relocated the datasources XML files from thier default location, or have you created them manually directly under ${DOMAIN_HOME}/config directory..?
    Regards,
    Mohab

  • UCCX 9.0.1 Datasource to IBM iSeries

    I am doing an upgrade from UCCX 7.0.2 to 9.0.1.
    The UCCX 7.0.2 has an ODBC driver connection to an IBM iSeries DB server using an iSeries driver.  I need to replicate this connection on UCCX 9.0.
    On UCCX 9.0 I only have the ability to use a few type of drivers, JDBC DB2 driver being one of them.  I have tried using the following drivers:
    db2jcc.jar
    db2jcc4.jar
    I have also loaded the customer supplied db2jcc_license_cu.jar
    Both of the drivers load successfully under the com.ibm.db2.jcc.DB2Driver class, but when I try to make a Database Source connection within UCCX the test connection always fails.  I have created a new DB account so I have verified that the username and password are correct.
    I have tried these different formats when creating the Database Source.  I don't know what port number I should be using.  I saw 50000 mentioned in a few forums.
    jdbc:db2//10.80.1.100:50000/val
    jdbc:db2//10.80.1.100/val
    No matter the syntax the Test Connection always fails.
    Thanks,
    Brian Corbet

    We recently took a customer from CCX 7.x (Windows based) to 9.x (Cisco UCOS based) and ran into this issue. 
    Problem:
    Connecting via JDBC to an iSeries DB2 database
    description: Getting an error when trying to add an iSeries DB2 DataSource to the CCX server.  Adding the Datasource fails. In the CCX Engine logs, you see something similar to the following:
    [SQLException@185bf33] Message    = [jcc][t4][10509][13454][4.16.53] Connection to the data server failed. The IBM Data Server for JDBC and SQLJ license was invalid
     %MIVR-LIB_JDBC-7-UNK:or was not activated for the DB2 for z/OS subsystem. If you are connecting directly to
    %MIVR-LIB_JDBC-7-UNK:the data server and using DB2 Connect Unlimited Edition for System z, perform the
    %MIVR-LIB_JDBC-7-UNK:activation step by running the activation program in the license activation kit.  
    %MIVR-LIB_JDBC-7-UNK:If you are using any other edition of DB2 Connect, obtain the license file,
    %MIVR-LIB_JDBC-7-UNK:db2jcc_license_cisuz.jar, from the license activation kit, and follow the installation
    %MIVR-LIB_JDBC-7-UNK:directions to include the license file in the class path. ERRORCODE=-4230, SQLSTATE=42968
    Solution:
    1) The customer provided the db2jcc_license_cisuz.jar file, part of the “DB2 Connect” file set, which they purchased from IBM.
    2) I installed the Java SE JDK version 8_20 (not sure that the JDK version actually matters except later when I set my PATH).
    3) I copied the db2jcc4.jar file from the 10.5 driver and the db2jcc_license_cisuz.jar file from the provided DB2 Connect file set to the root of my c: drive.
    4) I ran the following commands in Windows Command Prompt to combine the jar files into a single file:
    PATH=%PATH%;C:\Program Files\Java\jdk1.8.0_20\bin 
    c:
    cd \
    mkdir tmp
    cd tmp
    jar -xf ../db2jcc4.jar
    jar -xf ../db2jcc_license_cisuz.jar
    cd ..
    jar -cvf combined.jar -C tmp .
    5) I browsed in CCX Administration to Subsystems > Database > Drivers, chose my file “combined.jar” file (C:\combined.jar) and selected "com.ibm.db2.jcc.DB2Driver” from the drop down box.  I clicked upload and it accepted it.
    6) I browsed in CCX Administration to Subsystems > Database > Datasource and built my datasource.  I entered my DSN name, username, password, confirmed the password, chose “com.ibm.db2.jcc.DB2Driver” from the drop down box, and entered my JDBC URL - jdbc:db2://<iSeries IP Address>:446/SXXXXXXX - where, SXXXXXXX is the database name. 
    7) I then went into the Datasource and tested.  It tested successfully.
    This allowed us to connect to the customer’s iSeries database.
    Please note that after we fixed this issue, we ran into another one. Here's a description of that issue and how we resolved it.
    Problem:
    Inserting Rows to a non-journaled iSeries DB2 database
    Description: Getting an error when we try to insert or update an iSeries DB2 database, using the DB Write Step.  This was working before in CCX 7.x (Windows based) when the connection was using ODBC. The CCX engine is successfully able to connect to the customer database via JDBC, however, we are seeing something similar to this in the CCX Engine logs when we try to do database writes (DB Write in CCX script):
    %MIVR-LIB_JDBC-7-UNK:com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-7008, SQLSTATE=55019, SQLERRMC=DATABASENAME    ;3, DRIVER=4.16.53 
    Solution:
    The key to this problem turned out to be that the customer database was not journaled.  IBM provided useful information in this regard. In particular, the following IBM tech note indicates that they do NOT support manipulating the JDBC driver parameters on the iSeries.  Instead, either the database must be journaled, or you must use “WITH NC” (omitting the quotes) at the end of your INSERT or UPDATE SQL query (at the end of our DB Write step) .  When we use “WITH NC”, the database inserts work without error.
    See this link for more details.
    http://www-01.ibm.com/support/docview.wss?uid=swg21676715

  • Uccx 8.0 email IMAP config

    Hi all, Does anyone have a screen shot of their IMAP config within the global settings in UCCX please, I just can't get it to accept the IMAP config but we can't figure out what's wrong but all looks OK.
    Thanks

    We have:
    IMAP Host:
    Port: 143
    Username: [email protected]
    Password:
    SMTP Host:
    Port: 25
    Username: [email protected]
    Password:
    I believe what caught us up at first was IMAP was configured to require a secure connection. Try adjusting the Exchange IMAP properties to make it work non-secure first.

  • Authentication error at planning datasource config

    Hi,
    I have one planning application. Some days ago, I changed the password of 'admin' and synced it through shared services. planning and all other applications are working ok thereafter. But now I need to create a seperate planning application for which one new datasource is required. When I try to create a new datasource, it is giving error: "Failed to authenticate user admin against provider native directory". After giving the datasource name when I want to go to next screen the error is coming. Can you please guide me on this problem?
    Regqrds.

    Hi,
    The Shared services is up & running, but when I want to login in Shared services with 'admin' Id then the same error is coming- "Failed to authenticate user admin against provider native directory". But I can login into planning and workspace with the modified password without any problem.
    Can anyone please suggest the way to overcome the aforesaid problem. Appreciate your help & supports.
    Regards.

  • Multiple DataSource using single Connection Pool

    Previously using Weblogic 6.1 we had a configuration where multiple Datasources used a single connection pool. Now that we are in the process of upgrading to Weblogic 9.1, we are attempting to recreate the same configuration.
    The Weblogic 9.1 upgrade wizard appears to have created the relevent datasource & connection pool configuration files but when attempting to use these I am receiving the following errors:
    ####<30-Jan-2007 11:18:21 o'clock GMT> <Info> <JDBC> <tu0991ws9004> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1170155901758> <BEA-001508> <Destroying Connection Pool TestDSLegacyPool.>
    ####<30-Jan-2007 11:18:21 o'clock GMT> <Info> <JDBC> <tu0991ws9004> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1170155901758> <BEA-001155> <The following exception has occurred:
    weblogic.common.ResourceException: Unknown Data Source TestDSLegacyPool
         at weblogic.jdbc.common.internal.ConnectionPoolManager.shutdownAndDestroyPool(ConnectionPoolManager.java:419)
         at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:251)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    >
    ####<30-Jan-2007 11:18:21 o'clock GMT> <Error> <Deployer> <tu0991ws9004> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1170155901773> <BEA-149205> <Failed to initialize the application 'TestDSLegacyPool' due to error weblogic.application.ModuleException: .
    weblogic.application.ModuleException:
         at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:257)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    weblogic.common.ResourceException: weblogic.common.ResourceException: DataSource(TestDSLegacyPool) can't be created with non-existent Pool (connection or multi) (Beach Brochure Browse Pool)
         at weblogic.jdbc.common.internal.DataSourceManager.checkDataSource(DataSourceManager.java:239)
         at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:247)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    weblogic.common.ResourceException: DataSource(TestDSLegacyPool) can't be created with non-existent Pool (connection or multi) (Beach Brochure Browse Pool)
         at weblogic.jdbc.common.internal.DataSourceManager.verifyPoolDeployment(DataSourceManager.java:607)
         at weblogic.jdbc.common.internal.DataSourceManager.checkDSConfig(DataSourceManager.java:594)
         at weblogic.jdbc.common.internal.DataSourceManager.checkDataSource(DataSourceManager.java:236)
         at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:247)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    ++++++++++++++++++++++++++++++++++++++++++++++++++
    The configuration files content is :
    TestDSLegacyPool-9290-jdbc.xml
    <?xml version='1.0' encoding='UTF-8'?>
    <jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/910/domain.xsd">
    <name>TestDSLegacyPool</name>
    <internal-properties>
    <property>
    <name>LegacyType</name>
    <value>3</value>
    </property>
    <property>
    <name>LegacyPoolName</name>
    <value>Beach Brochure Browse Pool</value>
    </property>
    </internal-properties>
    <jdbc-data-source-params>
    <jndi-name>beachBrochureBrowseDS</jndi-name>
    <global-transactions-protocol>None</global-transactions-protocol>
    </jdbc-data-source-params>
    </jdbc-data-source>
    CP-Beach_Brochure_Browse_Pool-1043-jdbc.xml
    <?xml version='1.0' encoding='UTF-8'?>
    <jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/910/domain.xsd">
    <name>Beach Brochure Browse Pool</name>
    <internal-properties>
    <property>
    <name>LegacyType</name>
    <value>1</value>
    </property>
    </internal-properties>
    <jdbc-driver-params>
    <url>jdbc:oracle:thin:@aserver:1522:adb</url>
    <driver-name>oracle.jdbc.driver.OracleDriver</driver-name>
    <properties>
    <property>
    <name>user</name>
    <value>gf_user</value>
    </property>
    <property>
    <name>dll</name>
    <value>ocijdbc9</value>
    </property>
    <property>
    <name>protocol</name>
    <value>thin</value>
    </property>
    </properties>
    <password-encrypted>{3DES}4UT5899x/Z4=</password-encrypted>
    </jdbc-driver-params>
    <jdbc-connection-pool-params>
    <initial-capacity>1</initial-capacity>
    <max-capacity>3</max-capacity>
    </jdbc-connection-pool-params>
    </jdbc-data-source>
    Would anyone be able to point me in the right direction with this? Configuring the Datasources through the Admin Console creates a single Datasource configuration file that contains its relevent connection pool configuration, but the Weblogic Upgrade wizard creates a Datasource config file and a separate connection pool config file. What would I need to do to use the config files generated by the Weblogic Upgrade wizard?
    Any help appreciated
    Thanks
    Andrew

    Andrew Harrison wrote:
    Previously using Weblogic 6.1 we had a configuration where multiple Datasources used a single
    connection pool. Now that we are in the process of upgrading to Weblogic 9.1, we are attempting
    to recreate the same configuration.Hi, sorry to say, that is no longer possible:
    http://e-docs.bea.com/wls/docs90/jdbc_admin/jdbc_intro.html#1044158
    Simplified JDBC Resource Configuration
    In WebLogic Server 9.0, the number of JDBC resource types was reduced to simplify JDBC configuration and to reduce the likelihood
    of configuration errors. Instead of configuring a JDBC connection pool and then configuring a data source or tx data source to
    point to the connection pool and bind to the JNDI tree, you configure a data source that encompasses a connection pool.
    Note: Because of the new configuration design, you can no longer have multiple data sources that point to a single connection
    pool. Instead, you can create additional data sources, each with its own pool of connections, or you can bind a single data source
    to the JNDI tree with multiple names. See Binding a Data Source to the JNDI Tree with Multiple Names for more information.
    Joe
    >
    The Weblogic 9.1 upgrade wizard appears to have created the relevent datasource & connection pool
    configuration files but when attempting to use these I am receiving the following errors:
    ####<30-Jan-2007 11:18:21 o'clock GMT> <Info> <JDBC> <tu0991ws9004> <AdminServer> <[ACTIVE]
    ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <>
    <1170155901758> <BEA-001508> <Destroying Connection Pool TestDSLegacyPool.>
    ####<30-Jan-2007 11:18:21 o'clock GMT> <Info> <JDBC> <tu0991ws9004> <AdminServer> <[ACTIVE]
    ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <>
    <1170155901758> <BEA-001155> <The following exception has occurred:
    weblogic.common.ResourceException: Unknown Data Source TestDSLegacyPool
         at weblogic.jdbc.common.internal.ConnectionPoolManager.shutdownAndDestroyPool(ConnectionPoolManager.java:419)
         at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:251)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    ####<30-Jan-2007 11:18:21 o'clock GMT> <Error> <Deployer> <tu0991ws9004> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1170155901773> <BEA-149205> <Failed to initialize the application 'TestDSLegacyPool' due to error weblogic.application.ModuleException: .
    weblogic.application.ModuleException:
         at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:257)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    weblogic.common.ResourceException: weblogic.common.ResourceException: DataSource(TestDSLegacyPool) can't be created with non-existent Pool (connection or multi) (Beach Brochure Browse Pool)
         at weblogic.jdbc.common.internal.DataSourceManager.checkDataSource(DataSourceManager.java:239)
         at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:247)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    weblogic.common.ResourceException: DataSource(TestDSLegacyPool) can't be created with non-existent Pool (connection or multi) (Beach Brochure Browse Pool)
         at weblogic.jdbc.common.internal.DataSourceManager.verifyPoolDeployment(DataSourceManager.java:607)
         at weblogic.jdbc.common.internal.DataSourceManager.checkDSConfig(DataSourceManager.java:594)
         at weblogic.jdbc.common.internal.DataSourceManager.checkDataSource(DataSourceManager.java:236)
         at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:247)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    ++++++++++++++++++++++++++++++++++++++++++++++++++
    The configuration files content is :
    TestDSLegacyPool-9290-jdbc.xml
    <?xml version='1.0' encoding='UTF-8'?>
    <jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/910/domain.xsd">
    <name>TestDSLegacyPool</name>
    <internal-properties>
    <property>
    <name>LegacyType</name>
    <value>3</value>
    </property>
    <property>
    <name>LegacyPoolName</name>
    <value>Beach Brochure Browse Pool</value>
    </property>
    </internal-properties>
    <jdbc-data-source-params>
    <jndi-name>beachBrochureBrowseDS</jndi-name>
    <global-transactions-protocol>None</global-transactions-protocol>
    </jdbc-data-source-params>
    </jdbc-data-source>
    CP-Beach_Brochure_Browse_Pool-1043-jdbc.xml
    <?xml version='1.0' encoding='UTF-8'?>
    <jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/910/domain.xsd">
    <name>Beach Brochure Browse Pool</name>
    <internal-properties>
    <property>
    <name>LegacyType</name>
    <value>1</value>
    </property>
    </internal-properties>
    <jdbc-driver-params>
    <url>jdbc:oracle:thin:@aserver:1522:adb</url>
    <driver-name>oracle.jdbc.driver.OracleDriver</driver-name>
    <properties>
    <property>
    <name>user</name>
    <value>gf_user</value>
    </property>
    <property>
    <name>dll</name>
    <value>ocijdbc9</value>
    </property>
    <property>
    <name>protocol</name>
    <value>thin</value>
    </property>
    </properties>
    <password-encrypted>{3DES}4UT5899x/Z4=</password-encrypted>
    </jdbc-driver-params>
    <jdbc-connection-pool-params>
    <initial-capacity>1</initial-capacity>
    <max-capacity>3</max-capacity>
    </jdbc-connection-pool-params>
    </jdbc-data-source>
    Would anyone be able to point me in the right direction with this? Configuring the Datasources
    through the Admin Console creates a single Datasource configuration file that contains its relevent
    connection pool configuration, but the Weblogic Upgrade wizard creates a Datasource config file and
    a separate connection pool config file. What would I need to do to use the config files generated
    by the Weblogic Upgrade wizard?
    Any help appreciated
    Thanks
    Andrew

  • Connect JBOSS to MySQL using datasource,both servers are on different machi

    HI,
    In my application, I use JBOSS server and MySQL database.JBOSS and MySQL server are on two different machines.I am using mysql datasource,not driver manager to get the connection. i configured mysql-ds.xml and put it in %JBOSS_HOME%\server\default\deploy directory.
    I have also put the mysql connector jar in the %JBOSS_HOME%\server\default\lib directory.
    mysql-ds.xml file
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- $Id: mysql-ds.xml 41016 2006-02-07 14:23:00Z acoliver $ -->
    <!-- Datasource config for MySQL using 3.0.9 available from:
    http://www.mysql.com/downloads/api-jdbc-stable.html
    -->
    <datasources>
    <local-tx-datasource>
    <jndi-name>JBossAtWorkDS</jndi-name>
    <connection-url>jdbc:mysql://192.168.1.3:3306/JBossAtWorkDS</connection-url>
    <driver-class>com.mysql.jdbc.Driver</driver-class>
    <user-name>sa</user-name>
    <password></password>
    <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
    <!-- should only be used on drivers after 3.22.1 with "ping" support
    <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
    -->
    <!-- sql to call when connection is created
    <new-connection-sql>some arbitrary sql</new-connection-sql>
    -->
    <!-- sql to call on an existing pooled connection when it is obtained from pool - MySQLValidConnectionChecker is preferred for newer drivers
    <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
    -->
    <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
    <metadata>
    <type-mapping>mySQL</type-mapping>
    </metadata>
    </local-tx-datasource>
    </datasources>
    code to make the connection is as follows...
    public class JDBCCarDAO implements CarDAO
    private List carList;
    private static final String DATA_SOURCE="java:comp/env/jdbc/JBossAtWorkDS";
    public JDBCCarDAO()
    public List findAll()
    List carList = new ArrayList();
    DataSource dataSource = null;
    Connection conn = null;
    Statement stmt = null;
    ResultSet rs = null;
    try
    dataSource = ServiceLocator.getDataSource(DATA_SOURCE);
    conn = dataSource.getConnection();
    stmt = conn.createStatement();
    stmt.execute("select * from CAR");
         rs = stmt.getResultSet();
    while(rs.next())
    CarDTO car = new CarDTO();
    car.setMake(rs.getString("MAKE"));
    car.setModel(rs.getString("MODEL"));
    car.setModelYear(rs.getString("MODEL_YEAR"));
    carList.add(car);
    catch (Exception e)
    System.out.println("No SQL connection is made"+e);
    finally
    try
    if(rs != null){rs.close();}
    if(stmt != null){stmt.close();}
    if(conn != null){conn.close();}
    catch(Exception e)
    System.out.println(e);
    return carList;
    I am getting an error as follows...
    No SQL connection is made.
    org.Jboss.util.NestedSQLException:Could not create connection; -nested throwable: (java.sql.SQLException:Unable to connect to any host due to exception:java.net.ConnectException:Connection Time out:connect......
    how to get rid of this problem????plz...someone help me....

    If you have access to a copy of TimesTen 6.0 you can look in the AppServer Configuration Guide (appsrv.pdf) that was shipped with that release. This guide is currently being rewritten and so is not yet available for 7.0.
    If you can't get hold of a copy, e-mail me at [email protected] and I'll send it to you.
    Chris

  • Implement custom datasource (IDataSource)

    Hi,
    how can I implement a new datasource for the UME? I searched the SDN and didn't find anything. Then I guess datasource* on my classpath and found the [com.sap.security.core.persistence.datasource.imp.UMEClientDataSource|http://www.sapjarfinder.com/?q=UMEClientDataSource&st=] class, which implements the com.sap.security.core.persistence.datasource.IDataSource interface. When I do a search on IDataSource on the SDN, I found [this|http://help.sap.com/saphelp_nw04s/helpdata/en/e7/8f0440a832e369e10000000a155106/frameset.htm]. To quote this source:
    className: Specifies the implementation class of the data source,
    which implements the IDataSource interface.
    The specified class has to be loadable by the
    class loader which loads the jar com.sap.security.core.jar
    and further
    This list may be extended in the future by new
    data source implementations developed by SAP or customers.
    So to me this appears to me that I "only" have to provide an implementation of the IDataSource interface, somehow take care that my class gets loaded by the same ClassLoader, and reference it in the DataSource config file? If so, how can I take care that my class gets loaded by this classloader?
    Is it necessary that the jar/class is available in the j2ee\cluster\server0\bin\ext\com.sap.security.core.sda folder? What type of ClassLoader is it which loads the ext-jars? Does anybody of you have experience with implementing a new datasource for the UME? Where can I find further documentation on implementing a new datasource?
    Best regards,
    Fabian

    All of the documentation says it works with RTSP, and has been tested and shown to be working with a few RTSP servers. Perhaps you could get one of them and see if you can view content that comes from one of the ones that's known to play ball with JMF?

  • Server hang for waitting test sql response

    hi all
    I have deploy ear to weblogic and use jndi to lookup weblogic datasource pool.
    sometimes the server will hang about 10 miniute.
    the thread dump show that a thread wait weblogic test sql to response.
    I had ever try to change jdbc driver ,but the problem is still exist.
    any suggestion?
    ===weblogic datasource config===
    url : jdbc:jtds:sybase://192.168.1.1:5100/NIAIMM2
    driver : net.sourceforge.jtds.jdbc.Driver
    Initial Capacity: 5
    Maximum Capacity: 150
    Capacity Increment: 1
    Test Connections On Reserve : unchecked
    Test Frequency:120
    Test Table Name:SQL SELECT 1
    Seconds to Trust an Idle Pool Connection:10
    Shrink Frequency:900
    Init SQL:
    Connection Creation Retry Frequency:60
    Login Delay:0
    Inactive Connection Timeout:0
    Maximum Waiting for Connection:2147483647
    Connection Reserve Timeout:10
    Statement Timeout:3
    Ignore In-Use Connections:checked
    Pinned-To-Thread:unchecked
    Remove Infected Connections Enabled:checked
    ===environment===
    Weblogic 10.3.3
    Sybase ASE 15.5
    Linux ubuntu
    ===thread dump===
    "[STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=10 tid=0x0000000042b7d000 nid=0x9a2 runnable [0x00007ff979c16000]
    java.lang.Thread.State: RUNNABLE
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at java.io.DataInputStream.readFully(DataInputStream.java:178)
         at java.io.DataInputStream.readFully(DataInputStream.java:152)
         at net.sourceforge.jtds.jdbc.SharedSocket.readPacket(SharedSocket.java:846)
         at net.sourceforge.jtds.jdbc.SharedSocket.getNetPacket(SharedSocket.java:727)
         - locked <0x00007ffa0732c2a0> (a java.util.ArrayList)
         at net.sourceforge.jtds.jdbc.ResponseStream.getPacket(ResponseStream.java:466)
         at net.sourceforge.jtds.jdbc.ResponseStream.read(ResponseStream.java:103)
         at net.sourceforge.jtds.jdbc.ResponseStream.peek(ResponseStream.java:88)
         at net.sourceforge.jtds.jdbc.TdsCore.wait(TdsCore.java:3932)
         at net.sourceforge.jtds.jdbc.TdsCore.executeSQL(TdsCore.java:1046)
         - locked <0x00007ffa07337830> (a net.sourceforge.jtds.jdbc.TdsCore)
         at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:537)
         at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.execute(JtdsPreparedStatement.java:558)
         - locked <0x00007ffa0732bb90> (a net.sourceforge.jtds.jdbc.ConnectionJDBC3)
         at weblogic.jdbc.common.internal.ConnectionEnv.testInternal(ConnectionEnv.java:821)
         at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:756)
         at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:495)
         at weblogic.common.resourcepool.ResourcePoolImpl.testResource(ResourcePoolImpl.java:2345)
         at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1657)
         at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1564)
         at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1553)
         at weblogic.common.resourcepool.ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:2001)
         at weblogic.common.resourcepool.ResourcePoolImpl.access$900(ResourcePoolImpl.java:40)
         at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2433)
         at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Edited by: 860320 on May 20, 2011 3:56 AM

    hi all
    I have encounter the problem again at 09:26 AM
    and the DBA give me the log as follow:
    does anyone know what RepAgent(6) is?
    is it "ct_results()" cause the db to wait sql response.
    01:09:00000:01089:2011/05/25 08:37:31.08 server A client process exited abnormally, or a network error was enco
    untered. Unless other errors occurred, continue processing normally.
    01:09:00000:01089:2011/05/25 08:37:31.08 kernel extended error information: hostname: login: utfadm
    01:12:00000:00000:2011/05/25 08:40:18.16 kernel nrpacket: recv, Connection timed out, spid: 2457, suid: 3
    01:12:00000:00000:2011/05/25 08:40:18.16 kernel extended error information: hostname: n-chk-app5 login: utfadm
    01:05:00000:00000:2011/05/25 08:40:18.77 kernel nrpacket: recv, Connection timed out, spid: 2593, suid: 3
    01:05:00000:00000:2011/05/25 08:40:18.77 kernel extended error information: hostname: n-chk-app5 login: utfadm
    01:09:00000:02329:2011/05/25 09:13:31.38 kernel Cannot send, host process disconnected: 0000016a suid: 3
    01:09:00000:02329:2011/05/25 09:13:31.38 server Error: 1608, Severity: 18, State: 3
    01:09:00000:02329:2011/05/25 09:13:31.38 server A client process exited abnormally, or a network error was enco
    untered. Unless other errors occurred, continue processing normally.
    01:09:00000:02329:2011/05/25 09:13:31.38 kernel extended error information: hostname: login: utfadm
    01:00:00000:02161:2011/05/25 09:29:19.80 server RepAgent(6): Received the following communications error messag
    e: Msg 05030506: ct_results(): network packet layer: internal net library error: Net-Lib protocol driver call to
    read data failed.
    01:08:00000:00369:2011/05/25 09:44:10.01 kernel Cannot send, host process disconnected: 0000016a suid: 3
    01:08:00000:00369:2011/05/25 09:44:10.01 server Error: 1608, Severity: 18, State: 3
    01:08:00000:00369:2011/05/25 09:44:10.01 server A client process exited abnormally, or a network error was enco
    untered. Unless other errors occurred, continue processing normally.
    01:08:00000:00369:2011/05/25 09:44:10.01 kernel extended error information: hostname: login: utfadm

  • Oracle errors in Weblogic Error logs appear in non english

    We have a problem with weblogic error logging. Specifically, in a managed server's log file, Oracle errors such as ORA-XXXX show in Greek, not English. We are assuming
    that this is because the timezone is Europe/Athens. However, the weblogic application server runs with user.language=en, user.country=US. What's more, there are 4 application servers and 2 of them have this problem. The oracle database is accessed via weblogic datasources.
    Oracle database server Setup: Oracle Server 11gR2 running on Oracle Linux 64 bit, timezone set to Europe/Athens
    Weblogic Server: Weblogic 10.3.5 running on Oracle Linux 64 bit, timezone set to Europe/Athens
    The managed server, according to jrockit, the jvm runs with the following language related system properties:
    user.language=en, user.country=US, user.timezone=Europe/Athens
    The question is: How do we tell oracle / weblogic to log english text for the ORA errors?
    Thanks,
    Chris

    I digged in the weblogic installation directory and it seems like the domain configuration wizard messed up the jdbc configs for the data sources.
    The config xml files for the data sources in the /domain root/config/jdbc directory had oracle driver but the test query was for pointbase. I double checked from the database.xml file in the init-info directory and corrected the entry in the datasource config xmls and voila!.. the errors were gone.
    I am not sure if this was the right approach and whether i have solved the issue or simply patched it.. so I am keeping the question open. If any one has any inputs I will be grateful.
    If the mods/admins feel that the thread should be marked as solved I will surely do so.
    Thanks.

  • Help:Can not find the file in jar!

    Hello everyone:
    I build a project using Netbeans 5.0 and make a jar file with it...
    The code in the project as follows will throw an exception described that it can not find the file named datasource-config.xml
    String dataFilePath = getClass().getResource(dataFile).getPath();
    //System.out.println("filepath:"+dataFilePath);
    InputStream input = new FileInputStream(dataFilePath);
    when I run the project with the main() function as an entry it works perfectly and output:
    filepath:/C:/projects/java_project/search/build/classes/com/cn/wxjt/lucene/config/datasource-config.xml
    But when I compressed the project with jar and run it , it will show:
    filepath:file:/C:/projects/java_project/search/dist/search.jar!/com/cn/wxjt/lucene/config/datasource-config.xml
    there is a (!) between search.jar and /com/cn/wxjt...
    I dont know why I generate a ! symbol in the file path... Is it cause the exception->
    java.io.FileNotFoundException: file:\C:\projects\java_project\search\dist\search.jar!\com\cn\wxjt\lucene\config\datasource-config.xml
    If you have any idea, plz tell me.
    Thank you and best wishes to you !
    :)

    If the file you want to read is in your jar file, use
    getClass ().getResourceAsStream
    (relative_path_file_name)Hope that help,
    Jackhey jack i want to open the file as new File
    i m using this.getClass().getResource("resource/backend.xml");
    the resource is the directory inside the jar file.
    when i prints the url it shows:
    the jar file is in the WORK directory
    URL : jar:file:/home/neeraj/WORK/show.jar!/resource/backend.xml
    now when i creates new File using the url.getFile() method the file does not exist.
    although the same programs runs well when i uses the InputStream
    so plz tell me cant I create a new File from the above method????
    thanks in advance
    with regards
    neeraj

  • Help me to remove this Error in Entity Beans

    this is the Error i am getting along with this Error i have also put my ds xml file and other related file , please help me to remove this error
    at org.jboss.mx.server.ReflectedDispatcher.handleInvocationExceptions(Re
    flectedDispatcher.java:91)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
    java:64)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
    java:197)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
    ler.java:884)
    at $Proxy18.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:414)
    at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
    java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
    java:197)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy71.start(Unknown Source)
    at org.jboss.ejb.EjbModule.startService(EjbModule.java:367)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
    upport.java:271)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
    eanSupport.java:221)
    at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
    java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
    java:197)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
    ler.java:884)
    at $Proxy18.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:414)
    at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
    java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
    java:197)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy15.start(Unknown Source)
    at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:570)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:829)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
    at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
    java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
    java:197)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy8.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
    tScanner.java:304)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
    canner.java:460)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
    doScan(AbstractDeploymentScanner.java:201)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
    loop(AbstractDeploymentScanner.java:212)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
    run(AbstractDeploymentScanner.java:191)
    Caused by: org.jboss.deployment.DeploymentException: Error in jbosscmp-jdbc.xml
    : datasource-mapping MySql not found
    at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCEntityMetaData.<init>(JDB
    CEntityMetaData.java:483)
    at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCApplicationMetaData.<init
    (JDBCApplicationMetaData.java:312)at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCXmlFileLoader.load(JDBCXm
    lFileLoader.java:67)
    at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadJDBCEntityMetaDat
    a(JDBCStoreManager.java:721)
    at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBC
    StoreManager.java:409)
    at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManage
    r.java:353)
    at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManag
    er.java:155)
    at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:337)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
    upport.java:271)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
    eanSupport.java:221)
    at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
    java:60)
    ... 65 more
    11:37:34,679 INFO [EJBDeployer] Deployed: file:/C:/jboss-3.2.6/server/default/d
    eploy/ProductBean.jar
    11:37:34,679 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
    MBeans waiting for other MBeans:
    ObjectName: jboss.j2ee:jndiName=FaqMstLocal,plugin=pool,service=EJB
    state: CREATED
    I Depend On:
    Depends On Me:
    ObjectName: jboss.j2ee:jndiName=FaqMstLocal,service=EJB
    state: FAILED
    I Depend On:
    Depends On Me: MBeanException: org.jboss.deployment.DeploymentException: Error
    in jbosscmp-jdbc.xml : datasource-mapping MySql not found
    Cause: org.jboss.deployment.DeploymentException: Error in jbosscmp-jdbc.xml : da
    tasource-mapping MySql not found
    MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
    ObjectName: jboss.j2ee:jndiName=FaqMstLocal,plugin=pool,service=EJB
    state: CREATED
    I Depend On:
    Depends On Me:
    ObjectName: jboss.j2ee:jndiName=FaqMstLocal,service=EJB
    state: FAILED
    I Depend On:
    Depends On Me: MBeanException: org.jboss.deployment.DeploymentException: Error
    in jbosscmp-jdbc.xml : datasource-mapping MySql not found
    Cause: org.jboss.deployment.DeploymentException: Error in jbosscmp-jdbc.xml : da
    tasource-mapping MySql not found
    1 ) Contain of mysql-ds.xml File
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- $Id: mysql-ds.xml,v 1.1.2.1 2003/12/12 19:19:56 starksm Exp $ -->
    <!-- Datasource config for MySQL using 3.0.9 available from:
    http://www.mysql.com/downloads/api-jdbc-stable.html
    -->
    <datasources>
    <local-tx-datasource>
    <jndi-name>MySql</jndi-name>
    <connection-url>jdbc:mysql://192.168.111.44:3306/temp</connection-url>
              <driver-class>com.mysql.jdbc.Driver</driver-class>
    <user-name>new_temp</user-name>
    <password>temp</password>
    </local-tx-datasource>
    </datasources>
    2) i have also add datasource mappping in standardjaws.xml and standardjbosscmp-jdbc.xml file
    File :standardjaws.xml
    <datasource>java:/MySql</datasource>
              <type-mapping>MySql</type-mapping>
         File : standardjbosscmp-jdbc.xml
         <datasource>java:/MySql</datasource>
    <datasource-mapping>MySql</datasource-mapping>

    have a look at http://www.onjava.com/pub/a/onjava/2004/02/25/jbossjdbc.html

  • Forcibly releasing inactive connection  BEA-001153

    Hello there!, here at work we use Jdeveloper 11.1.3.0 , with JNDI Data Sources to access database (configured from WLS) My DataSource config is:
    <?xml version='1.0' encoding='UTF-8'?>
    <jdbc-data-source xmlns="http://xmlns.oracle.com/weblogic/jdbc-data-source" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/jdbc-data-source http://xmlns.oracle.com/weblogic/jdbc-data-source/1.0/jdbc-data-source.xsd">
      <name>arq</name>
      <jdbc-driver-params>
        <url>jdbc:oracle:thin:@192.168.101.**:1521/HLSEDB</url>
        <driver-name>oracle.jdbc.OracleDriver</driver-name>
        <properties>
          <property>
            <name>user</name>
            <value>dbadmin</value>
          </property>
        </properties>
        <password-encrypted>{AES}6mOLLY92ueqAFcFK3k29k/SUeCy/qgp1a9HGsHsCTg4=</password-encrypted>
      </jdbc-driver-params>
      <jdbc-connection-pool-params>
        <initial-capacity>1</initial-capacity>
        <max-capacity>15</max-capacity>
        <capacity-increment>1</capacity-increment>
        <shrink-frequency-seconds>900</shrink-frequency-seconds>
        <highest-num-waiters>2147483647</highest-num-waiters>
        <connection-creation-retry-frequency-seconds>0</connection-creation-retry-frequency-seconds>
        <connection-reserve-timeout-seconds>10</connection-reserve-timeout-seconds>
        <test-frequency-seconds>120</test-frequency-seconds>
        <test-connections-on-reserve>false</test-connections-on-reserve>
        <ignore-in-use-connections-enabled>true</ignore-in-use-connections-enabled>
        <inactive-connection-timeout-seconds>360</inactive-connection-timeout-seconds>
        <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
        <login-delay-seconds>0</login-delay-seconds>
        <statement-cache-size>10</statement-cache-size>
        <statement-cache-type>LRU</statement-cache-type>
        <remove-infected-connections>true</remove-infected-connections>
        <seconds-to-trust-an-idle-pool-connection>10</seconds-to-trust-an-idle-pool-connection>
        <statement-timeout>-1</statement-timeout>
        <pinned-to-thread>false</pinned-to-thread>
      </jdbc-connection-pool-params>
      <jdbc-data-source-params>
        <jndi-name>jdbc/arq</jndi-name>
        <global-transactions-protocol>OnePhaseCommit</global-transactions-protocol>
      </jdbc-data-source-params>
    </jdbc-data-source>Minutes after deploying mi application, console starts to show :
    <JDBC> <BEA-001153> <Forcibly releasing inactive connection "weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection@22e" back into the connection pool "SegDS", currently reserved by: java.lang.Exception
         at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:318)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:344)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:322)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:438)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:317)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:106)
         at weblogic.jdbc.pool.Driver.connect(Driver.java:149)There's any best practice or guide to configure my Datasource? or we should avoid JNDI's and start to use only appmodule connection?
    Thanks !

    I found the answer for this issue, because "Inactive timeout connection" of "advanced" in "data sources" of welogic admin console set to 300 seconds, once we changed to "zero". This msg is gone.

  • Crystal Report prompts for username / pwd when deployed to Bus Obj Server

    Hi All,
    I'm relatively new to Crystal Reports development.  My day job is test analyst.  I'm reasonably technically proficient.
    PROBLEM
    I have created a number of Crytsal Reports which have now been deployed to an Enterprise Business Objects Report Server.  The Server is Business Objects Server XI release 2.
    When I run the report in Crystal Reports Desiger 2008 it does not prompt me to enter the database credentials except if I have modified the SQL command or some other report detail.  Most times I run the report, no database username / pwd is required because I already set this up in the datasource config.
    I' connecting to an Oracle database using ODBC (RDO) connection type.  I cannot get the ODBC (RDO) connection type working from my PC using Crystal Reports Designer 2008, because I don't have ODBC configured for my datasource.  Instead, Im using the native Oracle Server driver to connect to my datasource.
    An existing user in the client organisation configured my report to use the ODBC (RDO) conneciton type for me because the Business Objects Server in the client organisation does not (currently) support the native Oracle driver.  Other reports this user has created and deployed using the ODBC conenction type run successfully without prompting user to enter the database connection credentials.
    NOTE:
    This report users an SQL Command (new to Crystal 2008 I beleive?).  The command is reqiured for this report due to the complexity of the underlying SQL query.
    Does anybody know why the report keeps prompting me to enter the database credentials at runtime?  Obviously for security reasons I don't want report users to have to enter the database schema name and password in order to run the report.

    Hi,
    You need to uncheck "Propmt the user for database logon when viewing". You will find this when you deploy the report on the BOE XI R2.
    The deployment step main heading is
    Specify Databse Crendentials.
    Hope this helps,
    Thanks
    -Azhar

  • Cannot allocate any more connections after  10.2.0.3 to 10.2.0.5 upgrade

    Recently upgraded Oracle from 10.2.0.3 to 10.2.0.5 and Glassfish from v3.0 to v3.1. We have not experienced errors of this kind previous to that change.
    We performed the operation on our test server first and experienced no issues save some 'expect behaviour' changes as listed elsewhere.
    Since upgrading on our live server we have a few times come across issues where Glassfish has used up all the connections in it's connection pool. Looking at Oracle statistics for the times where this occured showed no such matching surge in connections on the Oracle side. Usage statistics show no abnormally high number of users or log-ins at the times when this problem occurs, and the usage numbers are an order of magnitude under the maximum supported volumes that we have tested/prepared for.
    This problem may be at the Oracle or Glassfish end, but we are running out of ideas so are appealing for help and suggestions from a number of forums in order to get this pinned down.
    In the meantime, we are giving our larger web applications their own connection pools incase there is a code-side problem, though the spread of errors suggests this isn't going to be the case.
    If there is any extra logging that can be done to pin down the source of the problem, I'd be eager to hear about it.
    Sample Error in Glassfish logs:
    Caused by: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: In-use connections equal max-pool-size therefore cannot allocate any more connections.
         at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:310)
         at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:236)
         at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165)
         at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:160)
         at com.sun.gjc.spi.base.DataSource.getConnection(DataSource.java:110)
         ... 24 more
    Caused by: com.sun.appserv.connectors.internal.api.PoolingException: In-use connections equal max-pool-size therefore cannot allocate any more connections.
         at com.sun.enterprise.resource.pool.UnpooledResource.getUnenlistedResource(UnpooledResource.java:115)
         at com.sun.enterprise.resource.pool.ConnectionPool.internalGetResource(ConnectionPool.java:526)
         at com.sun.enterprise.resource.pool.ConnectionPool.getResource(ConnectionPool.java:381)
         at com.sun.enterprise.resource.pool.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:242)
         at com.sun.enterprise.resource.pool.PoolManagerImpl.getResource(PoolManagerImpl.java:167)
         at com.sun.enterprise.connectors.ConnectionManagerImpl.getResource(ConnectionManagerImpl.java:341)
         at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:304)
         ... 28 more
    |#]

    790951 wrote:
    Not opened a SR. DataSource config as follows (some bits hidden for obvious reasons):
    <jdbc-connection-pool datasource-classname="oracle.jdbc.pool.OracleDataSource" max-pool-size="900" pooling="false" res-type="javax.sql.DataSource" connection-leak-timeout-in-seconds="3600" steady-pool-size="20" name="jdbc/OurResourceDS" connection-leak-reclaim="true">
    <property name="DataSourceName" value="jdbc/OurResourceDS"></property>
    <property name="Password" value="hidden-"></property>
    <property name="URL" value="jdbc:-hidden-"></property>
    <property name="User" value="-hidden-"></property>
    </jdbc-connection-pool>Looks like pooling has been disabled - is this on purpose ?
    Using Connection Pooling With Oracle Data Provider for .Net (Doc ID 240997.1)
    HTH
    Srini

Maybe you are looking for