JDBC Version/connection pooling

Hi all
I am using JDK1.1.8 (this is device dependant so please don't suggest using a different JDK), and jTurbo1.22 as my driver. I have three questions:
1. What version of JDBC does JDK1.1.8 support?
2. Can I use Connection Pooling with this set up (driver + JDK)?
3. If I can't use connection pooling, any suggestions on how to control more than one connection to a database?
Thanks
John

1. What version of JDBC does JDK1.1.8 support?Version 1.
2. Can I use Connection Pooling with this set up (driver + JDK)?Connection pooling is a interface to a driver. You can do it in any version of java. However, if you are asking about a specific implementation that is a different matter.
3. If I can't use connection pooling, any suggestions on how to control more than one connection to a database?
Control it? Connection pooling requires keeping connections fresh. If you aren't using the connection then something, especially with Oracle, has to do this.
So you solutions are:
-Find a connection pool
-Write your own minimalistic one and deal with keeping the connections fresh.
-Close the connections when you are done with them.

Similar Messages

  • A very surprise problem about JDBC and connection pool

    I occur a very problem about JDBC and connection pool on Weblogic Platform
    8.1.
    There is a table in Oracle
    Table
    Name: t1
    id varchar2(5);
    content clob;
    id is primary key.
    If I use a connection pool to connect to Oracle,like following program:
    InitialContext ic = new InitialContext();
    DataSource ds = (DataSource) ic.lookup("cgOracleDataSource");
    con = ds.getConnection();
    then following program will throw a ClassCastException
    String sql = "select content from t1 where id = ?";
    PreparedStatement pst = con.prepareStatement(sql);
    pst.setString(1,"001");
    oracle.sql.CLOB clob = (oralce.sql.CLOB)rs.getClob("content") //this
    statement will throw ClassCastException
    but if I use JNDI to connect to Oracle,like following program, then those
    program above is ok
    private String dbdriver="oracle.jdbc.driver.OracleDriver";
    private String dburl="jdbc:oracle:thin:@192.168.7.148:1521:ep";
    private String username="ep";
    private String password="epuser";
    Class.forName(dbdriver);
    conn = DriverManager.getConnection(dburl, username, password);
    conn.setAutoCommit(false);
    On the contrary, if I use JNDI to connect to Oracle, following program will
    throw ClassCastException
    weblogic.jdbc.vendor.oracle.OracleThinClob clob =
    (weblogic.jdbc.vendor.oracle.OracleThinClob)rs.getClob("content");
    but it is fine if I use connection pool to connect to Oracle.
    I am confused this problem, who can tell me why?
    Daniel

    When you are getting connection using datasource lookup from weblogic
    connection pool, this connection is internally wrapped and hence you have to
    cast it to weblogic.jdbc.vendor.oracle.OracleThinClob which you do and so it
    works.
    But when you get connection by loading driver straight, you are getting naked
    oracle connection. In this case when you cast it to oracle.sql.Clob it works,
    as you have seen in your test case.
    I hope this explains what is going on with your code.
    Thanks,
    Mitesh
    Daniel wrote:
    I occur a very problem about JDBC and connection pool on Weblogic Platform
    8.1.
    There is a table in Oracle
    Table
    Name: t1
    id varchar2(5);
    content clob;
    id is primary key.
    If I use a connection pool to connect to Oracle,like following program:
    InitialContext ic = new InitialContext();
    DataSource ds = (DataSource) ic.lookup("cgOracleDataSource");
    con = ds.getConnection();
    then following program will throw a ClassCastException
    String sql = "select content from t1 where id = ?";
    PreparedStatement pst = con.prepareStatement(sql);
    pst.setString(1,"001");
    oracle.sql.CLOB clob = (oralce.sql.CLOB)rs.getClob("content") //this
    statement will throw ClassCastException
    but if I use JNDI to connect to Oracle,like following program, then those
    program above is ok
    private String dbdriver="oracle.jdbc.driver.OracleDriver";
    private String dburl="jdbc:oracle:thin:@192.168.7.148:1521:ep";
    private String username="ep";
    private String password="epuser";
    Class.forName(dbdriver);
    conn = DriverManager.getConnection(dburl, username, password);
    conn.setAutoCommit(false);
    On the contrary, if I use JNDI to connect to Oracle, following program will
    throw ClassCastException
    weblogic.jdbc.vendor.oracle.OracleThinClob clob =
    (weblogic.jdbc.vendor.oracle.OracleThinClob)rs.getClob("content");
    but it is fine if I use connection pool to connect to Oracle.
    I am confused this problem, who can tell me why?
    Daniel

  • Is in ORACLE JDBC drivers connection pooling support

    Hi All!
    Can anybody give me information about subj?
    Any information appreciated

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Mike:
    Hi All!
    Can anybody give me information about subj?
    Any information appreciated<HR></BLOCKQUOTE>
    Yes, Oracle JDBC drivers do support connection pooling. Download the latest drivers to get samples and refer doc for more details.

  • JDBC Adapter - Connection Pooling

    Does anybody know if we can specify a Connection Pool to the JDBC Adapter? I mean the number of connections that the Adapter can have open to say Oracle Data.
    Regards
    Mike

    Hi Michael,
    Some of the specifications that are given while configuring the JDBC adapter, especially regarding the number of connections that you acn have...is given clearly in this documentation for JDBC adapter:-
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/756b3c0d592c7fe10000000a11405a/frameset.htm
    Specifically check for the following parameters :-
    <i>db.transactionIsolation=0|1|2|4|8
    db.autoCommit=NO|YES
    db.pollInterval=
    db.retryInterval=
    db.logPollInterval=NO|YES</i>
    Regards,
    Sushumna

  • JDBC connection pool failures when used by JMS stores

              We are using WebLogic 6.1 sp2. We defined a separate connection pool for use by
              a JMS Store.
              <JDBCConnectionPool Name="sybaseJMSPool"
              Targets="cluster00"
              InitialCapacity="2"
              MaxCapacity="10"
              DriverName="com.sybase.jdbc2.jdbc.SybDriver"
              Properties="[email protected]@;[email protected]@;charset=utf8"
              URL="jdbc:sybase:Tds:@jms.db.host@/@jms.db.name@"/>
              (note that the @xxx@ string are replaced by actual values).
              We are using Sybase Jconnect 5.5 to a Sybase ASE 12.5 database.
              We deployed this configuration on a number of environments (testing, staging,
              ..). The actual hardware and network configuration is different for the different
              system, but the WebLogic domain stays the same regarding this issue.
              On the test system we frequently get the following exceptions:
              <Aug 13, 2002 1:56:04 PM CEST> <Alert> <JMS> <www00-test> <node00>
              <ExecuteThread: '6' for queue: 'JMS.TimerClientPool'> <> <> <040048>
              <JMSServer "JMSServer00", store failure while writing message for topic
              OrderChangeTopic, java.io.IOException: JMS JDBC store, connection pool =
              <sybaseJMSPool>, prefix = <JMS00>: write failed
              java.sql.SQLException: JZ006: Caught IOException:
              com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
              closed.
              at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
              (ErrorMessage.java:715)
              at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
              at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
              at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
              at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
              at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
              at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
              (SybStatement.java:1625)
              at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
              (SybPreparedStatement.java:91)
              at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
              (P6LogPreparedStatement.java:179)
              at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
              at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
              at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
              at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              .>
              java.io.IOException: JMS JDBC store, connection pool = <sybaseJMSPool>, prefix
              = <JMS00>: write failed
              java.sql.SQLException: JZ006: Caught IOException:
              com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
              closed.
              at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
              (ErrorMessage.java:715)
              at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
              at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
              at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
              at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
              at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
              at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
              (SybStatement.java:1625)
              at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
              (SybPreparedStatement.java:91)
              at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
              (P6LogPreparedStatement.java:179)
              at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
              at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
              at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
              at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              at weblogic.jms.store.JDBCIOStream.throwIOException
              (JDBCIOStream.java:1213)
              at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1256)
              at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
              at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              Before that this message appeared:
              <Aug 13, 2002 11:31:16 AM CEST> <Error> <ConnectionManager> <www00-test>
              <node00> <ExecuteThread: '26' for queue: 'default'> <> <> <000000>
              <Closing: 'weblogic.rjvm.t3.T3JVMConnection@795af6' because of: 'Server
              received a message over an uninitialized connection: 'JVMMessage from: 'null'
              to: '-4555218188801970213S:192.168.13.1:[7001,7001,7002,7002,7001,7002,-
              1]:ADIS:node00' cmd: 'CMD_REQUEST', QOS: '101', responseId: '1',
              invokableId: '287', flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev
              offset: '34'''>
              This problem did not occur on another system which was used during a 2 day stress
              testing session.
              It seems that the problem occurs after a period in which no user request where
              made. The user requests trigger EJB's that start sending JMS messages.
              When the problem occurs, the JMS messaging systems seems to lock up as no messages
              are received anymore by the different listeners (MDBs).
              Undeploying and redeploying the JBDC connection pool solves the problem. This
              solution is unacceptable in case of a production system.
              A similarly defined connection pool, which is used by the EJBs to make database
              connection, does not manifest this problem.
              <JDBCConnectionPool Name="sybasePool"
              Targets="cluster00"
              InitialCapacity="10"
              CapacityIncrement="5"
              MaxCapacity="50"
              PreparedStatementCacheSize="150"
              DriverName="com.sybase.jdbc2.jdbc.SybDriver"
              Properties="[email protected]@;[email protected]@;JCONNECT_VERSION=6;charset=utf8"
              URL="jdbc:sybase:Tds:@db.host@/@db.name@"/>
              The JDBC connection pool is used as follows by the JDBC store
              <JMSJDBCStore ConnectionPool="sybaseJMSPool" Name="JDBCStore00" PrefixName="JMS00"/>
              <JMSServer Name="JMSServer00" Store="JDBCStore00" Targets="node00">
              <JMSTopic JNDIName="ADIS.JMSError" JNDINameReplicated="false" Name="ErrorTopic"/>
              <JMSTopic JNDIName="ADIS.Status"
              Name="StatusTopic" RedeliveryDelayOverride="300000"/>
              <JMSTopic JNDIName="ADIS.OrderChange" JNDINameReplicated="false"
              Name="OrderChangeTopic" RedeliveryLimit="3"/>
              </JMSServer>
              Turning on the "Test Reserved Connection" with a appropriate test table does not
              help.
              Some sources on the internet tell us that JZ0C0 errors in the Jconnect driver
              can be related to network problems. Nevertheless the connection pool should be
              able to cope with this.
              Can you provide any solution for this ? Or give us hints what can cause the problem
              

    Zhenhao Qi wrote:
    thanks! Joe.
    The SQL statement itself can no longer be simplified, the long excuation time is due to the database size and complicated Select criteria. I can easily reproduce the problem by using this SQL. I tried "BEA's Oracle driver (Type 4): Version 8.1.7,9.0.1,9.2.0". the question can be dissect into 2 pieces:
    1) why the jdbc connection (using oracle.jdbc.OracleDriver) won't return anything if the SQL execution time > 5min, that is probably the Oracle's problem
    2) why the occupied connection pool won't release even I set "Statementtimeout=600", this is Weblogic's problem.
    ZhenhaoHi. Yes, (1) is oracle's problem. (2) may also be. The JDBC spec has very few
    allowances for one thread to interrupt a second thread's JDBC call. If we
    transmit your timeout request by calling setQueryTimeout() on the oracle
    statement, and if you have a weblogic-controlled transaction we call
    Statement.cancel() on any ongoing statement, we end up relying on whether
    the Oracle driver implements and responds to those calls.
    Are you doing weblogic-controlled transactions? Are you/can you
    call Statement.setQueryTimeout() on your statements, or are these
    generated JDBC queries?
    If you can duplicate the problem using the weblogic.jdbc.oracle.OracleDriver
    we have some other debug avenues. This would be good even if you really
    want to use the thin driver, because we will do the same JDBC calls to
    either driver, and the debug would prove (if) we set up a query timeout
    and if we call cancel(). If we do, then we can know that it is the Oracle
    driver failing in these regards.
    Joe

  • View # of current Connection of jdbc connection pool

    Do you guy know of ANY METHODS of viewing # of current database Connection of jdbc connection pool in SUNAPP SERVER?
    for example i have jdbc/Dashboard Connection Pool in SUNAPP SERVER and I wanted to view, at any point of time, how many connection database that it is being utilized during that time. The reason I wanted to see the # of currection jdbc connection is because my Max (400connections) ran out or hanging really long period of time.
    Thanks,
    Kelvin

    There is no way currently to do this

  • Connection Pool Metrics in ASC - doesn't seem to reflect the usage

    Guys,
    So i am trying to monitor the jdbc connection pool usage using the Application server Console (following the link --> Cluster Topology > Application Server: engas-machine > OC4J: oc4jinstance > JDBC Resources > Connection Pool Metrics: "myconnectionpool"
    But i don't see the Pool Usage not reflecting any change and displaying the value 0 for all attributes as below
         Connections In Use     0          
         Free Connections          0          
         Total Connections in Pool          0          
         Threads Waiting for Connections     0
    I wonder why is that, i wonder if i have to use ojdbc-dms driver for the ASC to display the actual statistics ?
    Thanks in advance

    BTW. here is the data-source.xml file...
    <data-sources xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/data-sources-10_1.xsd" schema-major-version="10" schema-minor-version="1">
    <managed-data-source connection-pool-name="MyAppConnectionPool" jndi-name="jdbc/mydb" name="mydatasource"/>
    <connection-pool name="MyAppConnectionPool" initial-limit="20" max-connections="100" min-connections="20">
    <connection-factory factory-class="oracle.jdbc.pool.OracleDataSource" user="[username]" password="[password]" url="jdbc:oracle:oci:@mydb" commit-record-table-name=""/>
    </connection-pool>
    </data-sources>
    </connection-pool>
    </data-sources>

  • Pointbase Server, Connection Pool Issue

    Hi All,
              I have set up a cluster containing two nodes - one local and other
              remote machine.
              I have extended my domain to include the Integration and Workshop
              extensions, as my application needs them. I have also configured the
              Node Manager to start the remote server and also setup the workshop
              database on my machine.
              I have set the classpath in the Node Manager to contain the jars -
              E:\bea_sp5\weblogic81\server\lib\weblogic.jar;E:\bea_sp5\weblogic81\common\eval\pointbase\lib\pbserver44.jar;
              E:\bea_sp5\weblogic81\common\eval\pointbase\lib\pbtools44.jar;
              E:\bea_sp5\weblogic81\server\lib\wli.jar;E:\bea_sp5\weblogic81\server\lib\knex.jar;
              <Jun 15, 2006 2:52:59 PM GMT+05:30> <Info>
              <[email protected]:5557> <Starting Server
              VSDClusterDomain2::MngdServer2 ...>
              <Jun 15, 2006 2:53:00 PM GMT+05:30> <Info>
              <[email protected]:5557> <Server VSDClusterDomain2::MngdServer2
              started, process id = 2,364>
              <Jun 15, 2006 2:53:02 PM GMT+05:30> <Info> <WebLogicServer>
              <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM
              Version 1.4.2_08-b03 from Sun Microsystems Inc.>
              <Jun 15, 2006 2:53:02 PM GMT+05:30> <Info> <Management> <BEA-141140>
              <The managed server is going to contact the admin server at
              http://15.76.223.63:7001 to check if there exists a running admin
              server at this URL.>
              <Jun 15, 2006 2:53:04 PM GMT+05:30> <Info> <Configuration Management>
              <BEA-150017> <This server is being started as a dependent managed
              server.>
              <Jun 15, 2006 2:53:04 PM GMT+05:30> <Info> <Management> <BEA-141107>
              <Version: WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
              WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
              WebLogic Integration 8.1 SP5 Wed Sep 21 21:56:54 PDT 2005 643163>
              <Jun 15, 2006 2:53:04 PM GMT+05:30> <Info> <Configuration Management>
              <BEA-150015> <Connecting to the administration server
              http://15.76.223.63:7001 to retrieve the initial configuration.>
              <Jun 15, 2006 2:53:13 PM GMT+05:30> <Notice> <Log Management>
              <BEA-170019> <The server log file
              E:\bea_sp5\weblogic81\common\nodemanager\MngdServer2\MngdServer2.log is
              opened. All server side log events will be written to this file.>
              <Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090082>
              <Security initializing using security realm myrealm.>
              <Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090170>
              <Loading the private key stored under the alias DemoIdentity from the
              jks keystore file E:\bea_sp5\weblogic81\server\lib\DemoIdentity.jks.>
              <Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090171>
              <Loading the identity certificate stored under the alias DemoIdentity
              from the jks keystore file
              E:\bea_sp5\weblogic81\server\lib\DemoIdentity.jks.>
              <Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090169>
              <Loading trusted certificates from the jks keystore file
              E:\bea_sp5\weblogic81\server\lib\DemoTrust.jks.>
              <Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090169>
              <Loading trusted certificates from the jks keystore file
              E:\bea_sp5\jdk142_08\jre\lib\security\cacerts.>
              <Jun 15, 2006 2:53:17 PM GMT+05:30> <Notice> <WebLogicServer>
              <BEA-000328> <Starting WebLogic Managed Server "MngdServer2" for domain
              "VSDClusterDomain2">
              <Jun 15, 2006 2:53:21 PM GMT+05:30> <Warning> <HTTP> <BEA-101296>
              <Unable to load the default compiler class "com.sun.tools.javac.Main".
              Using the default javac compiler to compile JSPs.>
              <Jun 15, 2006 2:53:22 PM GMT+05:30> <Notice> <Cluster> <BEA-000138>
              <Listening for announcements from cluster Cluster1 on 237.0.0.1:7001.>
              <Jun 15, 2006 2:53:22 PM GMT+05:30> <Notice> <Cluster> <BEA-000133>
              <Waiting to synchronize with other running members of Cluster1.>
              <Jun 15, 2006 2:53:53 PM GMT+05:30> <Error> <JDBC> <BEA-001150>
              <Connection Pool "cgJMSPool-nonXA" deployment failed with the following
              error: No registered driver accepts URL:
              jdbc:pointbase:server://15.76.223.63:9093/workshop.>
              <Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001150>
              <Connection Pool "bpmArchPool" deployment failed with the following
              error: No registered driver accepts URL:
              jdbc:pointbase:server://15.76.223.63:9093/workshop.>
              <Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001150>
              <Connection Pool "cgPool" deployment failed with the following error:
              No registered driver accepts URL:
              jdbc:pointbase:server://15.76.223.63:9093/workshop.>
              <Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001151> <Data
              Source "cgDataSource-nonXA" deployment failed with the following error:
              DataSource(cgDataSource-nonXA;weblogic.jdbc.jts.ebusinessPool) can't be
              created with non-existent Pool (connection or multi)
              (cgJMSPool-nonXA).>
              <Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001151> <Data
              Source "cgDataSource" deployment failed with the following error:
              DataSource(cgDataSource;cgSampleDataSource) can't be created with
              non-existent Pool (connection or multi) (cgPool).>
              <Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001151> <Data
              Source "bpmArchDataSource" deployment failed with the following error:
              DataSource(bpmArchDataSource) can't be created with non-existent Pool
              (connection or multi) (bpmArchPool).>
              <Jun 15, 2006 2:54:07 PM GMT+05:30> <Alert> <JMS> <BEA-040052>
              <JMSServer "cgJMSServer_auto_2" store failed to open
              java.io.IOException: JMS JDBC store, connection pool =
              <cgJMSPool-nonXA>, prefix = <VSD_2>: connection pool does not exist.
              java.io.IOException: JMS JDBC store, connection pool =
              <cgJMSPool-nonXA>, prefix = <VSD_2>: connection pool does not exist
              at
              weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
              at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
              at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
              at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
              at weblogic.jms.backend.BEStore.open(BEStore.java:262)
              at weblogic.jms.backend.BEStore.start(BEStore.java:151)
              at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
              at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
              at weblogic.jms.backend.BackEnd.migratableActivate(BackEnd.java:2939)
              at
              weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
              at
              weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
              at
              weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
              at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
              at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at
              sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at
              sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:324)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:516)
              at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at
              weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
              at
              weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
              at
              weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
              at
              weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7731)
              at
              weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1321)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:339)
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              <Jun 15, 2006 2:54:07 PM GMT+05:30> <Error> <JMS> <BEA-040368> <The
              following exception has occurred:
              weblogic.jms.common.JMSException: JMS can not open store
              cgJMSStore_auto_2
              at weblogic.jms.backend.BEStore.start(BEStore.java:163)
              at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
              at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
              at weblogic.jms.backend.BackEnd.migratableActivate(BackEnd.java:2939)
              at
              weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
              at
              weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
              at
              weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
              at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
              at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at
              sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at
              sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:324)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:516)
              at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at
              weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
              at
              weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
              at
              weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
              at
              weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7731)
              at
              weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1321)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:339)
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              Caused by: java.io.IOException: JMS JDBC store, connection pool =
              <cgJMSPool-nonXA>, prefix = <VSD_2>: connection pool does not exist
              at
              weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
              at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
              at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
              at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
              at weblogic.jms.backend.BEStore.open(BEStore.java:262)
              at weblogic.jms.backend.BEStore.start(BEStore.java:151)
              ... 33 more
              weblogic.jms.common.JMSException: JMS can not open store
              cgJMSStore_auto_2
              at weblogic.jms.backend.BEStore.start(BEStore.java:163)
              at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
              at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
              at weblogic.jms.backend.BackEnd.migratableActivate(BackEnd.java:2939)
              at
              weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
              at
              weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
              at
              weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
              at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
              at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at
              sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at
              sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:324)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:516)
              at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at
              weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
              at
              weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
              at
              weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
              at
              weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7731)
              at
              weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1321)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:339)
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              Caused by: java.io.IOException: JMS JDBC store, connection pool =
              <cgJMSPool-nonXA>, prefix = <VSD_2>: connection pool does not exist
              at
              weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
              at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
              at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
              at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
              at weblogic.jms.backend.BEStore.open(BEStore.java:262)
              at weblogic.jms.backend.BEStore.start(BEStore.java:151)
              ... 33 more
              --------------- nested within: ------------------
              weblogic.cluster.migration.MigrationException: Failed to activate
              JMSServer cgJMSServer_auto_2 - with nested exception:
              [weblogic.jms.common.JMSException: JMS can not open store
              cgJMSStore_auto_2]
              at weblogic.jms.backend.BackEnd.migratableActivate(BackEnd.java:2946)
              at
              weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
              at
              weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
              at
              weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
              at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
              at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at
              sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at
              sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:324)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:516)
              at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at
              weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
              at
              weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
              at
              weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
              at
              weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7731)
              at
              weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1321)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:339)
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              Why do you think this error is occuring? Any other setting needs to be
              done to overcome this problem ?
              Thanks in advance,
              Sandeep

    Please verify following
    1) have you defined jndi name for database correctly ??
    2) Have you added sqljdbc jar file in soa suite server?
    3) How much time it takes when you execute same query in JDev ?
    4) If you think configuration is issue, please verify the Jdev conn details @ http://soasphere.blogspot.com/2008/11/connecting-sql-server-from-jdeveloper.html and soa suite server side required settings @ Deploy error because of  sql server database adapter

  • Dynamic Connection Pool Creation Failing in a cluster

    Hi,
    I am trying to create a connection pool in a clustered environment. This connection
    pool is created lazily behind a Stateless Session Bean. We first attempt to determine
    whether, the connection pool exists using JdbcServices.poolExists(someName), and
    create it if it does not exist. A failure occurs on creation because it looks
    like the connection pool might have been created by a bean on a different weblogic
    VM instance. Is there any way to dynamically create a connection pool and make
    it visible to the whole cluster? Thanks in advance for any help. Michael Dolbear
    Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Checking existence of connection pool
    Content
    ConnectionPool requested by user guest>
    <Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Creating connection pool ContentConnectionPoo
    l requested by user guest>
    weblogic.common.ResourceException: weblogic.management.MBeanCreationException:
    Start server side stack trace:
    javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=JD
    BCConnectionPool
    at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
    at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:
    2352)
    at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874)
    at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanSer
    verImpl.java:181)
    at weblogic.management.internal.Helper.createMBean(Helper.java:376)
    at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
    at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
    ServerImpl.java:278)
    at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
    635)
    at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
    621)
    at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
    Impl.java:397)
    at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    weblogic.management.MBeanCreationException: - with nested exception:
    [javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=J
    DBCConnectionPool]
    at weblogic.management.internal.Helper.createMBean(Helper.java:383)
    at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
    at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
    ServerImpl.java:278)
    at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
    635)
    at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
    621)
    at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
    Impl.java:397)
    at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    - with nested exception:
    [javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=J
    DBCConnectionPool
    Start server side stack trace:
    javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=JD
    BCConnectionPool
            at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
            at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:
    2352)
            at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874)
            at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanSer
    verImpl.java:181)
            at weblogic.management.internal.Helper.createMBean(Helper.java:376)
            at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
            at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
    ServerImpl.java:278)
            at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
    635)
            at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
    621)
            at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
    Impl.java:397)
            at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
            at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
            at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
            at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
            at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End  server side stack trace
    at weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.java:47
    2)
    at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:727
    at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:709
    at com.thc.ids.inf.framework.opf.rdbms.datastore.ConnectionPoolCreator.createConne
    ctionPool(ConnectionPoolCreator.java:82)
    at com.thc.ids.inf.framework.opf.datastore.DataStoreRepository.createConnectionPoo
    lIfNonExistent(DataStoreRepository.java:211)
    at com.thc.ids.inf.util.persistence.content.ConnectionPoolInitializer.createConnec
    tionPoolIfNeeded(ConnectionPoolInitializer.java:48)
    at com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.create
    ConnectionPoolIfNeeded(Unknown Source)
    at com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.getIma
    ge(Unknown Source)
    at com.thc.ids.inf.services.business.crs.ContentRetrievalService.getImage(Unknown
    Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.thc.ids.inf.util.reflection.MethodDescription.invokeMethod(MethodDescriptio
    n.java:181)
    at com.thc.ids.inf.util.reflection.MethodInvocation.invoke(MethodInvocation.java:7
    9)
    at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean.invoke(ServiceBean.java:
    186)
    at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl.invoke(Ser
    viceBean_bjedmi_EOImpl.java:37)
    at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl_WLSkel.inv
    oke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    <Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Checking existence of connection
    pool Content
    ConnectionPool requested by user guest>
    <Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Creating connection pool ContentConnectionPoo
    l requested by user guest>
    weblogic.common.ResourceException: weblogic.management.MBeanCreationException:
    Start server side stack trace:
    javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=JD
    BCConnectionPool
    at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
    at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:
    2352)
    at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874)
    at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanSer
    verImpl.java:181)
    at weblogic.management.internal.Helper.createMBean(Helper.java:376)
    at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
    at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
    ServerImpl.java:278)
    at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
    635)
    at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
    621)
    at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
    Impl.java:397)
    at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    weblogic.management.MBeanCreationException: - with nested exception:
    [javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=J
    DBCConnectionPool]
    at weblogic.management.internal.Helper.createMBean(Helper.java:383)
    at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
    at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
    ServerImpl.java:278)
    at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
    635)
    at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
    621)
    at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
    Impl.java:397)
    at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    - with nested exception:
    [javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=J
    DBCConnectionPool
    Start server side stack trace:
    javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=JD
    BCConnectionPool
            at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
            at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:
    2352)
            at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874)
            at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanSer
    verImpl.java:181)
            at weblogic.management.internal.Helper.createMBean(Helper.java:376)
            at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
            at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
    ServerImpl.java:278)
            at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
    635)
            at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
    621)
            at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
    Impl.java:397)
            at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
            at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
            at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
            at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
            at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End  server side stack trace
    at weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.java:47
    2)
    at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:727
    at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:709
    at com.thc.ids.inf.framework.opf.rdbms.datastore.ConnectionPoolCreator.createConne
    ctionPool(ConnectionPoolCreator.java:82)
    at com.thc.ids.inf.framework.opf.datastore.DataStoreRepository.createConnectionPoo
    lIfNonExistent(DataStoreRepository.java:211)
    at com.thc.ids.inf.util.persistence.content.ConnectionPoolInitializer.createConnec
    tionPoolIfNeeded(ConnectionPoolInitializer.java:48)
    at com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.create
    ConnectionPoolIfNeeded(Unknown Source)
    at com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.getIma
    ge(Unknown Source)
    at com.thc.ids.inf.services.business.crs.ContentRetrievalService.getImage(Unknown
    Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.thc.ids.inf.util.reflection.MethodDescription.invokeMethod(MethodDescriptio
    n.java:181)
    at com.thc.ids.inf.util.reflection.MethodInvocation.invoke(MethodInvocation.java:7
    9)
    at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean.invoke(ServiceBean.java:
    186)
    at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl.invoke(Ser
    viceBean_bjedmi_EOImpl.java:37)
    at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl_WLSkel.inv
    oke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    The only way to do it is using MBeans. You could search this newsgroup
    for "JDBCConnectionPoolMBean" to get an idea of how it could be done.
    Slava
    P.S. http://search.bea.com/weblogic/gonews
    "Mark Mortensen" <[email protected]> wrote in message
    news:[email protected]...
    >
    Slava,
    I am working with Mike on this issue and wanted to add some moreclarifications.
    We have a two server cluster where one of the EJB's on one of the Managedservers
    creates the connection pool. The problem comes in when a request comes tothe
    second server in the cluster. The connection pool is created by the firstserver
    but it is only assigned to the first server in the targets section on theconsole.
    It isn't assigned to the cluster. Is there a way to programmaticallyassign the
    pool to the cluster instead of just the server that created the pool?
    -Mark
    "Michael Dolear" <[email protected]> wrote:
    Hi Slava,
    Here is what I am doing. The code is spread across a couple of classes.
    I am using
    what was described in BEA's doc on dynamic connection pool creation.
    I didn't
    see anything about MBean apis required:
    * Dynamically create a connection pool using
    aConnectionPoolProperties.
    Please
    see ConnectionPoolCreator
    * for the required properties that must be sent in.
    * @param aConnectionPoolProperties
    public synchronized void createConnectionPoolIfNonExistent(Properties
    aConnectionPoolProperties)
    throwsPersistenceFrameworkInitializationException
    ConnectionPoolCreator tempPoolCreator;
    Pool tempPool;
    tempPoolCreator = new ConnectionPoolCreator();
    tempPool =tempPoolCreator.getConnectionPool(aConnectionPoolProperties);
    if (tempPool == null)
    tempPoolCreator.createConnectionPool(aConnectionPoolProperties);
    >>
    * Create Connection pool given the properties that I have beenconfigured
    with
    * @return Pool
    public Pool createConnectionPool(Properties aConnectionProperties)
    throwsPersistenceFrameworkInitializationException
    JdbcServices tempServices;
    try
    tempServices = this.lookupJdbcServices();
    tempServices.createPool(aConnectionProperties);
    returntempServices.getPool(aConnectionProperties.getProperty(CONNECTION_POOL_NAME)
    catch (Exception e)
    PersistenceFrameworkUtils.logException(e);
    throw newPersistenceFrameworkInitializationException(e.getMessage());
    * Answer a connectionPool or null.
    * @return Pool
    public Pool getConnectionPool(Properties aConnectionProperties)
    throwsPersistenceFrameworkInitializationException
    JdbcServices tempServices;
    try
    tempServices = this.lookupJdbcServices();
    if (tempServices.poolExists(
    aConnectionProperties.getProperty(CONNECTION_POOL_NAME)))
    return tempServices.getPool(
    aConnectionProperties.getProperty(CONNECTION_POOL_NAME));
    else
    return null;
    catch (Exception e)
    PersistenceFrameworkUtils.logException(e);
    throw
    newPersistenceFrameworkInitializationException(e.getMessage());
    "Slava Imeshev" <[email protected]> wrote:
    Hi Michael,
    Could you show us the code? Without looking at the code
    I can only say that JdbcServices.poolExists(someName)
    returns true only in case the pool is up and running.
    If the connection pool MBean was created but not assigned
    a target, subsequent tries to create it would fail.
    Regards,
    Slava Imeshev
    "Michael Dolbear" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    I am trying to create a connection pool in a clustered environment.This
    connection
    pool is created lazily behind a Stateless Session Bean. We first
    attempt
    to determine
    whether, the connection pool exists usingJdbcServices.poolExists(someName), and
    create it if it does not exist. A failure occurs on creation becauseit
    looks
    like the connection pool might have been created by a bean on a
    different
    weblogic
    VM instance. Is there any way to dynamically create a connection pooland
    make
    it visible to the whole cluster? Thanks in advance for any help.
    Michael
    Dolbear
    Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Checking existence ofconnection pool
    Content
    ConnectionPool requested by user guest>
    <Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Creating connection poolContentConnectionPoo
    l requested by user guest>
    weblogic.common.ResourceException:weblogic.management.MBeanCreationException:
    Start server side stack trace:
    javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=JD
    BCConnectionPool
    at
    com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:1
    34
    at
    com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.
    ja
    va:
    2352)
    at
    com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:
    87
    4)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBe
    an
    Ser
    verImpl.java:181)
    atweblogic.management.internal.Helper.createMBean(Helper.java:376)
    atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
    MB
    ean
    ServerImpl.java:278)
    at
    weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
    ja
    va:
    635)
    at
    weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
    ja
    va:
    621)
    at
    weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
    nH
    ome
    Impl.java:397)
    atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
    :2
    2)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    weblogic.management.MBeanCreationException: - with nested exception:
    [javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=J
    DBCConnectionPool]
    atweblogic.management.internal.Helper.createMBean(Helper.java:383)
    atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
    MB
    ean
    ServerImpl.java:278)
    at
    weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
    ja
    va:
    635)
    at
    weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
    ja
    va:
    621)
    at
    weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
    nH
    ome
    Impl.java:397)
    atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
    :2
    2)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    - with nested exception:
    [javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=J
    DBCConnectionPool
    Start server side stack trace:
    javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=JD
    BCConnectionPool
    at
    com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:1
    34
    at
    com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.
    ja
    va:
    2352)
    at
    com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:
    87
    4)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBe
    an
    Ser
    verImpl.java:181)
    atweblogic.management.internal.Helper.createMBean(Helper.java:376)
    atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
    MB
    ean
    ServerImpl.java:278)
    at
    weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
    ja
    va:
    635)
    at
    weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
    ja
    va:
    621)
    at
    weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
    nH
    ome
    Impl.java:397)
    atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
    :2
    2)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    at
    weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.ja
    va
    :47
    2)
    at
    weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.jav
    a:
    727
    at
    weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.jav
    a:
    709
    at
    com.thc.ids.inf.framework.opf.rdbms.datastore.ConnectionPoolCreator.create
    Co
    nne
    ctionPool(ConnectionPoolCreator.java:82)
    at
    com.thc.ids.inf.framework.opf.datastore.DataStoreRepository.createConnecti
    on
    Poo
    lIfNonExistent(DataStoreRepository.java:211)
    at
    com.thc.ids.inf.util.persistence.content.ConnectionPoolInitializer.createC
    on
    nec
    tionPoolIfNeeded(ConnectionPoolInitializer.java:48)
    at
    com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.c
    re
    ate
    ConnectionPoolIfNeeded(Unknown Source)
    at
    com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.g
    et
    Ima
    ge(Unknown Source)
    at
    com.thc.ids.inf.services.business.crs.ContentRetrievalService.getImage(Unk
    no
    wn
    Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    com.thc.ids.inf.util.reflection.MethodDescription.invokeMethod(MethodDescr
    ip
    tio
    n.java:181)
    at
    com.thc.ids.inf.util.reflection.MethodInvocation.invoke(MethodInvocation.j
    av
    a:7
    9)
    at
    com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean.invoke(ServiceBean.
    ja
    va:
    186)
    at
    com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl.invok
    e(
    Ser
    viceBean_bjedmi_EOImpl.java:37)
    at
    com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl_WLSke
    l.
    inv
    oke(Unknown Source)
    atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.ja
    va
    :93
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
    :2
    2)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    <Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Checking existence ofconnection
    pool Content
    ConnectionPool requested by user guest>
    <Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Creating connection poolContentConnectionPoo
    l requested by user guest>
    weblogic.common.ResourceException:weblogic.management.MBeanCreationException:
    Start server side stack trace:
    javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=JD
    BCConnectionPool
    at
    com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:1
    34
    at
    com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.
    ja
    va:
    2352)
    at
    com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:
    87
    4)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBe
    an
    Ser
    verImpl.java:181)
    atweblogic.management.internal.Helper.createMBean(Helper.java:376)
    atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
    MB
    ean
    ServerImpl.java:278)
    at
    weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
    ja
    va:
    635)
    at
    weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
    ja
    va:
    621)
    at
    weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
    nH
    ome
    Impl.java:397)
    atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
    :2
    2)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    weblogic.management.MBeanCreationException: - with nested exception:
    [javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=J
    DBCConnectionPool]
    atweblogic.management.internal.Helper.createMBean(Helper.java:383)
    atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
    MB
    ean
    ServerImpl.java:278)
    at
    weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
    ja
    va:
    635)
    at
    weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
    ja
    va:
    621)
    at
    weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
    nH
    ome
    Impl.java:397)
    atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
    :2
    2)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    - with nested exception:
    [javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=J
    DBCConnectionPool
    Start server side stack trace:
    javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=JD
    BCConnectionPool
    at
    com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:1
    34
    at
    com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.
    ja
    va:
    2352)
    at
    com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:
    87
    4)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBe
    an
    Ser
    verImpl.java:181)
    atweblogic.management.internal.Helper.createMBean(Helper.java:376)
    atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
    MB
    ean
    ServerImpl.java:278)
    at
    weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
    ja
    va:
    635)
    at
    weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
    ja
    va:
    621)
    at
    weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
    nH
    ome
    Impl.java:397)
    atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
    :2
    2)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    at
    weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.ja
    va
    :47
    2)
    at
    weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.jav
    a:
    727
    at
    weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.jav
    a:
    709
    at
    com.thc.ids.inf.framework.opf.rdbms.datastore.ConnectionPoolCreator.create
    Co
    nne
    ctionPool(ConnectionPoolCreator.java:82)
    at
    com.thc.ids.inf.framework.opf.datastore.DataStoreRepository.createConnecti
    on
    Poo
    lIfNonExistent(DataStoreRepository.java:211)
    at
    com.thc.ids.inf.util.persistence.content.ConnectionPoolInitializer.createC
    on
    nec
    tionPoolIfNeeded(ConnectionPoolInitializer.java:48)
    at
    com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.c
    re
    ate
    ConnectionPoolIfNeeded(Unknown Source)
    at
    com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.g
    et
    Ima
    ge(Unknown Source)
    at
    com.thc.ids.inf.services.business.crs.ContentRetrievalService.getImage(Unk
    no
    wn
    Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    com.thc.ids.inf.util.reflection.MethodDescription.invokeMethod(MethodDescr
    ip
    tio
    n.java:181)
    at
    com.thc.ids.inf.util.reflection.MethodInvocation.invoke(MethodInvocation.j
    av
    a:7
    9)
    at
    com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean.invoke(ServiceBean.
    ja
    va:
    186)
    at
    com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl.invok
    e(
    Ser
    viceBean_bjedmi_EOImpl.java:37)
    at
    com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl_WLSke
    l.
    inv
    oke(Unknown Source)
    atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.ja
    va
    :93
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
    :2
    2)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

  • How to catch exception when have max connection pool

    hi,
    i have define in oracle user that i could have max 10 sessions at the same time.
    I have jdbc datasource & connection pool defined at glassfish server(JSF application).
    now, if in application is too many queries to the database then i have error: nullpointer exception - becouse when i try to do:
    con = Database.createConnection(); - it generates nullpointer exception becouse there isn't free connection pool
    i try to catch exception like this:
    public List getrep_dws_wnioski_wstrzymane_graph() {     int i = 0;     try {     con = Database.createConnection();     ps =    (Statement) con.createStatement();     rs = ps.executeQuery("select data, klasa, ile_dni_wstrzymana, ile_wnioskow from stg1230.dwsww_wstrzymane_dws8 order by data, klasa, ile_dni_wstrzymana, ile_wnioskow");     while(rs.next()){       rep_dws_wnioski_wstrzymane_graph.add(i,new get_rep_dws_wnioski_wstrzymane_graph(rs.getString(1),rs.getString(2),rs.getString(3),rs.getString(4)));       i++;     }     } catch (NamingException e) {         e.printStackTrace();     } catch (SQLException e) {         e.printStackTrace();     } catch (NullPointerException e) {         e.printStackTrace();         throw new NoConnectionException();  // catch null 1     } finally {     try {         con.close();     } catch (SQLException e) {         e.printStackTrace();     } catch (NullPointerException e) {         e.printStackTrace();         throw new NoConnectionException();  // catch null 2     }     } return rep_dws_wnioski_wstrzymane_graph; }
    but at line:
    con.close();
    i have nullpointerexception
    and
    at line
    throw new NoConnectionException(); // catch null 2
    i have: caused by exception.NoConnectionException
    what's wrong with my exception class? how to resolve it?
    public class NoConnectionException extends RuntimeException{     public NoConnectionException(String msg, Throwable cause){       super(msg, cause);     }     public NoConnectionException(){       super();     } }
    at web.xml i have defined:
    <error-page>         <exception-type>exception.NoConnectionException</exception-type>         <location>/NoConnectionExceptionPage.jsp</location>     </error-page>

    thanks,
    i did it and i have error:
    java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
    at com.sun.gjc.spi.base.DataSource.getConnection(DataSource.java:115)
    at logic.Database.createConnection(Database.java:37): conn = ds.getConnection();
    public class Database {
         public static Connection createConnection() throws NamingException,
                    SQLException {
                Connection conn = null;
                try{
                    Context ctx = new InitialContext();
              if (ctx == null) {
                   throw new NamingException("No initial context");
              DataSource ds = (DataSource) ctx.lookup("jdbc/OracleReports");
              if (ds == null) {
                   throw new NamingException("No data source");
              conn = ds.getConnection();  // here's exception when max connections to database
              if (conn == null) {
                   throw new SQLException("No database connection");
                } catch (NamingException e) {
                    e.printStackTrace();
                    throw new NoConnectionException(); 
             } catch (SQLException e) {
                 e.printStackTrace();
                    throw new NoConnectionException(); 
                catch (NullPointerException e) {
                 e.printStackTrace();
                    throw new NoConnectionException();  // obsluga bledy na wypadek jesli braknie wolnych polaczen do bazy
            return conn;
    }and at my ealier code i have error:
    at logic.GetDataOracle.getrep_dws_wnioski_wstrzymane_graph(GetDataOracle.java:192)
    at line: con = Database.createConnection();
    in code:
    public List getrep_dws_wnioski_wstrzymane_graph() {
        int i = 0;
        try {
        con = Database.createConnection();
        ps =    (Statement) con.createStatement();
        rs = ps.executeQuery("select data, klasa, ile_dni_wstrzymana, ile_wnioskow from stg1230.dwsww_wstrzymane_dws8 order by data, klasa, ile_dni_wstrzymana, ile_wnioskow");
        while(rs.next()){
          rep_dws_wnioski_wstrzymane_graph.add(i,new get_rep_dws_wnioski_wstrzymane_graph(rs.getString(1),rs.getString(2),rs.getString(3),rs.getString(4)));
          i++;
        } catch (NamingException e) {
            e.printStackTrace();
        } catch (SQLException e) {
            e.printStackTrace();
        } catch (NullPointerException e) {
            e.printStackTrace();
            throw new NoConnectionException();
        } finally {
        try {
            if(con != null)
            con.close();
        } catch (SQLException e) {
            e.printStackTrace();
        } catch (NullPointerException e) {
            e.printStackTrace();
            throw new NoConnectionException(); 
    return rep_dws_wnioski_wstrzymane_graph;
    }so what's wrong?
    i have limit max sessions 10 at oracle so i set at my connection pool 5 connections as max. But when i get max 5 sesssins and try to execute next query then i can't catch exception..

  • Error: : connection pool does not exist

    I am getting a Connection pool does not exitst Error on starting Web
    Logic. When i Checked on http://localhost:8002/console ->
    jdbc-connectionpools
    Productionpool(name of the connection pool), I checked the testing tab
    it shows it is unavailable while it shows Deployed=true on the
    Configuraton tab.
    It is failing on my system while its working on other systems. I am
    using weblogicSP4_814
    Can u pls provide me some solution for this error.
    <Jun 16, 2006 4:33:11 PM IST> <Warning> <JDBC> <BEA-001129> <Received
    exception while creating connection for pool "noti
    fJMSJDBCConnPool": access denied (java.util.PropertyPermission
    oracle.net.wallet_location read)>
    <Jun 16, 2006 4:33:12 PM IST> <Warning> <JDBC> <BEA-001129> <Received
    exception while creating connection for pool "noti
    fJMSJDBCConnPool": access denied (java.util.PropertyPermission
    oracle.net.wallet_location read)>
    <Jun 16, 2006 4:33:13 PM IST> <Error> <JDBC> <BEA-001150> <Connection
    Pool "notifJMSJDBCConnPool" deployment failed with
    the following error: 0:Could not create pool connection. The DBMS
    driver exception was: access denied (java.util.Proper
    tyPermission oracle.net.wallet_location read).>
    <Jun 16, 2006 4:33:13 PM IST> <Warning> <JDBC> <BEA-001129> <Received
    exception while creating connection for pool "prod
    uctionPool": access denied (java.util.PropertyPermission
    oracle.net.wallet_location read)>
    <Jun 16, 2006 4:33:14 PM IST> <Warning> <JDBC> <BEA-001129> <Received
    exception while creating connection for pool "prod
    uctionPool": access denied (java.util.PropertyPermission
    oracle.net.wallet_location read)>
    <Jun 16, 2006 4:33:15 PM IST> <Error> <JDBC> <BEA-001150> <Connection
    Pool "productionPool" deployment failed with the f
    ollowing error: 0:Could not create pool connection. The DBMS driver
    exception was: access denied (java.util.PropertyPerm
    ission oracle.net.wallet_location read).>
    <Jun 16, 2006 4:33:15 PM IST> <Error> <JDBC> <BEA-001151> <Data Source
    "notifJMSJDBCConnPool" deployment failed with the
    following error: DataSource(weblogic.jdbc.jts.notifJMSJDBCConnPool)
    can't be created with non-existent Pool (connection
    or multi) (notifJMSJDBCConnPool).>
    <Jun 16, 2006 4:33:15 PM IST> <Error> <JDBC> <BEA-001151> <Data Source
    "productionPool" deployment failed with the follo
    wing error: DataSource(weblogic.jdbc.jts.productionPool) can't be
    created with non-existent Pool (connection or multi) (
    productionPool).>
    <Jun 16, 2006 4:33:15 PM IST> <Alert> <JMS> <BEA-040052> <JMSServer
    "NotificationJMSServer" store failed to open java.io
    .IOException: JMS JDBC store, connection pool = <notifJMSJDBCConnPool>,
    prefix = <notif>: connection pool does not exist
    java.io.IOException: JMS JDBC store, connection pool =
    <notifJMSJDBCConnPool>, prefix = <notif>: connection pool does no
    t exist
    at
    weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
    at
    weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
    at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
    at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
    at weblogic.jms.backend.BEStore.open(BEStore.java:262)
    at weblogic.jms.backend.BEStore.start(BEStore.java:151)
    at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
    at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
    at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
    at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentÂTarget.java:337)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymenÂtTarget.java:597)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(ÂDeploymentTarget.java:575)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeployÂmentTarget.java:241)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3Â9)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpÂl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpÂl.java:755)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:Â734)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeÂanImpl.java:516)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeÂanServerImpl.java:990)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerÂImpl.java:948)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
    at
    weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.javÂa:475)
    at
    weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerÂMBean_Stub.java:7731)
    at
    weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlavÂeDeployer.java:1321)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:33Â9)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeplÂoymentManagerServerLifeCycleImpl.j
    ava:229)
    at
    weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
    at weblogic.Server.main(Server.java:32)
    <Jun 16, 2006 4:33:15 PM IST> <Error> <JMS> <BEA-040123> <Failed to
    start JMS Server "NotificationJMSServer" due to webl
    ogic.jms.common.JMSException: JMS can not open store notifJMSJDBCStore.
    weblogic.jms.common.JMSException: JMS can not open store
    notifJMSJDBCStore
    at weblogic.jms.backend.BEStore.start(BEStore.java:163)
    at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
    at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
    at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
    at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentÂTarget.java:337)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymenÂtTarget.java:597)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(ÂDeploymentTarget.java:575)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeployÂmentTarget.java:241)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3Â9)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpÂl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpÂl.java:755)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:Â734)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeÂanImpl.java:516)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeÂanServerImpl.java:990)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerÂImpl.java:948)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
    at
    weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.javÂa:475)
    at
    weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerÂMBean_Stub.java:7731)
    at
    weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlavÂeDeployer.java:1321)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:33Â9)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeplÂoymentManagerServerLifeCycleImpl.j
    ava:229)
    at
    weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
    at weblogic.Server.main(Server.java:32)
    Caused by: java.io.IOException: JMS JDBC store, connection pool =
    <notifJMSJDBCConnPool>, prefix = <notif>: connection p
    ool does not exist
    at
    weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
    at
    weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
    at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
    at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
    at weblogic.jms.backend.BEStore.open(BEStore.java:262)
    at weblogic.jms.backend.BEStore.start(BEStore.java:151)
    ... 29 more
    <Jun 16, 2006 4:33:32 PM IST> <Warning> <HTTP> <BEA-101248>
    <[D:\Build\autodeploys\i2\weblogic_home\config\vendavo\.\app
    lications\.wlnotdelete\wlap12518\vendavo.war]: Deployment descriptor
    "web.xml" is malformed. Check against the DTD: org.
    xml.sax.SAXParseException: The content of element type "web-app" must
    match "(icon?,display-name?,description?,distribut
    able?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapÂping*,session-config?,mime-mapping*,welcome-f
    ile-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-consÂtraint*,login-config?,security-role*,env-entr
    y*,ejb-ref*,ejb-local-ref*)". (line 252, column 11).>
    java.lang.ExceptionInInitializerError
    at com.vendavo.cl.ClassHelper.<clinit>(ClassHelper.java:28)
    at
    com.vendavo.cl.io.ResourceHelper.addLoader(ResourceHelper.java:121)
    at
    com.vendavo.cl.io.ResourceHelper.<init>(ResourceHelper.java:39)
    at
    com.vendavo.cl.io.ResourceHelper.<clinit>(ResourceHelper.java:29)
    at
    com.vendavo.platform.action.StartupAction.init(StartupAction.java:75)
    at
    com.vendavo.platform.action.StartupAction.contextInitialized(StartupAction.Âjava:311)
    at
    weblogic.servlet.internal.WebAppServletContext$FireContextListenerAction.ruÂn(WebAppServletContext.java:7044)
    at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjeÂct.java:321)
    at
    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at
    weblogic.servlet.internal.WebAppServletContext.notifyCreated(WebAppServletCÂontext.java:1753)
    at
    weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServlÂetContext.java:3352)
    at
    weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:727)
    at
    weblogic.servlet.internal.WebService.preloadResources(WebService.java:486)
    at
    weblogic.servlet.internal.ServletInitService.resume(ServletInitService.javaÂ:30)
    at
    weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
    at weblogic.Server.main(Server.java:32)
    Caused by: java.security.AccessControlException: access denied
    (java.util.PropertyPermission * read,write)
    at
    java.security.AccessControlContext.checkPermission(AccessControlContext.javÂa:269)
    at
    java.security.AccessController.checkPermission(AccessController.java:401)
    at
    java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
    at
    java.lang.SecurityManager.checkPropertiesAccess(SecurityManager.java:1243)
    at java.lang.System.getProperties(System.java:501)
    at
    com.vendavo.cl.property.AppProperties.loadSystemProperties(AppProperties.jaÂva:411)
    at
    com.vendavo.cl.property.AppProperties.loadBasics(AppProperties.java:326)
    at
    com.vendavo.cl.property.AppProperties.getInstance(AppProperties.java:160)
    at com.vendavo.cl.log.VLog.loadAppProperties(VLog.java:134)
    at com.vendavo.cl.log.VLog.createDefaultSetup(VLog.java:94)
    at com.vendavo.cl.log.VLog.<clinit>(VLog.java:66)
    ... 18 more
    <Jun 16, 2006 4:33:34 PM IST> <Warning> <HTTP> <BEA-101162> <User
    defined listener com.vendavo.platform.action.StartupAc
    tion failed: java.lang.NoClassDefFoundError.>
    <Jun 16, 2006 4:33:34 PM IST> <Warning> <HTTP> <BEA-101162> <User
    defined listener com.vendavo.platform.action.StartupAc
    tion failed: java.lang.NoClassDefFoundError.>
    <Jun 16, 2006 4:33:34 PM IST> <Error> <HTTP> <BEA-101216> <Servlet:
    "AdminServlet" failed to preload on startup in Web a
    pplication: "soap".
    Thanks in Advance,
    Ketan.B.Parekh

    ketan parekh wrote:
    I am getting a Connection pool does not exitst Error on starting Web
    Logic. When i Checked on http://localhost:8002/console ->
    jdbc-connectionpools
    Productionpool(name of the connection pool), I checked the testing tab
    it shows it is unavailable while it shows Deployed=true on the
    Configuraton tab.
    It is failing on my system while its working on other systems. I am
    using weblogicSP4_814
    Can u pls provide me some solution for this error. Hi. Would you run the utils.dbping utility, and then
    give it the arguments to connect to the same DBMS with
    the same user as your pool? Show me the exception you
    get if it fails:
    C:\bea81sp5\weblogic81>java utils.dbping
    Usage: java utils.dbping DB2B [-d dynamicSections] USER PASS HOST:PORT/DBNAME
    or java utils.dbping JCONN2 USER PASS HOST:PORT/DBNAME
    or java utils.dbping JCONNECT USER PASS HOST:PORT/DBNAME
    or java utils.dbping INFORMIXB USER PASS HOST:PORT/DBNAME/INFORMIXSERVER
    or java utils.dbping MSSQLSERVER4 USER PASS HOST:PORT/DBNAME
    or java utils.dbping MSSQLSERVER4 USER PASS [DBNAME@]HOST[:PORT]
    or java utils.dbping MSSQLSERVERB USER PASS HOST:PORT/DBNAME
    or java utils.dbping ORACLE USER PASS DBNAME
    or java utils.dbping ORACLEB USER PASS HOST:PORT/DBNAME
    or java utils.dbping ORACLE_THIN USER PASS HOST:PORT:DBNAME
    or java utils.dbping POINTBASE USER PASS HOST[:PORT]/DBNAME
    or java utils.dbping SYBASEB USER PASS HOST:PORT/DBNAME
    >
    >
    <Jun 16, 2006 4:33:11 PM IST> <Warning> <JDBC> <BEA-001129> <Received
    exception while creating connection for pool "noti
    fJMSJDBCConnPool": access denied (java.util.PropertyPermission
    oracle.net.wallet_location read)>
    <Jun 16, 2006 4:33:12 PM IST> <Warning> <JDBC> <BEA-001129> <Received
    exception while creating connection for pool "noti
    fJMSJDBCConnPool": access denied (java.util.PropertyPermission
    oracle.net.wallet_location read)>
    <Jun 16, 2006 4:33:13 PM IST> <Error> <JDBC> <BEA-001150> <Connection
    Pool "notifJMSJDBCConnPool" deployment failed with
    the following error: 0:Could not create pool connection. The DBMS
    driver exception was: access denied (java.util.Proper
    tyPermission oracle.net.wallet_location read).>
    <Jun 16, 2006 4:33:13 PM IST> <Warning> <JDBC> <BEA-001129> <Received
    exception while creating connection for pool "prod
    uctionPool": access denied (java.util.PropertyPermission
    oracle.net.wallet_location read)>
    <Jun 16, 2006 4:33:14 PM IST> <Warning> <JDBC> <BEA-001129> <Received
    exception while creating connection for pool "prod
    uctionPool": access denied (java.util.PropertyPermission
    oracle.net.wallet_location read)>
    <Jun 16, 2006 4:33:15 PM IST> <Error> <JDBC> <BEA-001150> <Connection
    Pool "productionPool" deployment failed with the f
    ollowing error: 0:Could not create pool connection. The DBMS driver
    exception was: access denied (java.util.PropertyPerm
    ission oracle.net.wallet_location read).>
    <Jun 16, 2006 4:33:15 PM IST> <Error> <JDBC> <BEA-001151> <Data Source
    "notifJMSJDBCConnPool" deployment failed with the
    following error: DataSource(weblogic.jdbc.jts.notifJMSJDBCConnPool)
    can't be created with non-existent Pool (connection
    or multi) (notifJMSJDBCConnPool).>
    <Jun 16, 2006 4:33:15 PM IST> <Error> <JDBC> <BEA-001151> <Data Source
    "productionPool" deployment failed with the follo
    wing error: DataSource(weblogic.jdbc.jts.productionPool) can't be
    created with non-existent Pool (connection or multi) (
    productionPool).>
    <Jun 16, 2006 4:33:15 PM IST> <Alert> <JMS> <BEA-040052> <JMSServer
    "NotificationJMSServer" store failed to open java.io
    .IOException: JMS JDBC store, connection pool = <notifJMSJDBCConnPool>,
    prefix = <notif>: connection pool does not exist
    java.io.IOException: JMS JDBC store, connection pool =
    <notifJMSJDBCConnPool>, prefix = <notif>: connection pool does no
    t exist
    at
    weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
    at
    weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
    at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
    at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
    at weblogic.jms.backend.BEStore.open(BEStore.java:262)
    at weblogic.jms.backend.BEStore.start(BEStore.java:151)
    at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
    at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
    at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
    at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment??Target.java:337)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deploymen??tTarget.java:597)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(??DeploymentTarget.java:575)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploy??mentTarget.java:241)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3??9)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp??l.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp??l.java:755)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:??734)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe??anImpl.java:516)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBe??anServerImpl.java:990)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServer??Impl.java:948)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
    at
    weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.jav??a:475)
    at
    weblogic.management.configuration.ServerMBean_Stub.updateDeployments(Server??MBean_Stub.java:7731)
    at
    weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(Slav??eDeployer.java:1321)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:33??9)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl??oymentManagerServerLifeCycleImpl.j
    ava:229)
    at
    weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
    at weblogic.Server.main(Server.java:32)
    <Jun 16, 2006 4:33:15 PM IST> <Error> <JMS> <BEA-040123> <Failed to
    start JMS Server "NotificationJMSServer" due to webl
    ogic.jms.common.JMSException: JMS can not open store notifJMSJDBCStore.
    weblogic.jms.common.JMSException: JMS can not open store
    notifJMSJDBCStore
    at weblogic.jms.backend.BEStore.start(BEStore.java:163)
    at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
    at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
    at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
    at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment??Target.java:337)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deploymen??tTarget.java:597)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(??DeploymentTarget.java:575)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploy??mentTarget.java:241)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3??9)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp??l.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp??l.java:755)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:??734)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe??anImpl.java:516)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBe??anServerImpl.java:990)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServer??Impl.java:948)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
    at
    weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.jav??a:475)
    at
    weblogic.management.configuration.ServerMBean_Stub.updateDeployments(Server??MBean_Stub.java:7731)
    at
    weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(Slav??eDeployer.java:1321)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:33??9)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl??oymentManagerServerLifeCycleImpl.j
    ava:229)
    at
    weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
    at weblogic.Server.main(Server.java:32)
    Caused by: java.io.IOException: JMS JDBC store, connection pool =
    <notifJMSJDBCConnPool>, prefix = <notif>: connection p
    ool does not exist
    at
    weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
    at
    weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
    at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
    at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
    at weblogic.jms.backend.BEStore.open(BEStore.java:262)
    at weblogic.jms.backend.BEStore.start(BEStore.java:151)
    ... 29 more
    <Jun 16, 2006 4:33:32 PM IST> <Warning> <HTTP> <BEA-101248>
    <[D:\Build\autodeploys\i2\weblogic_home\config\vendavo\.\app
    lications\.wlnotdelete\wlap12518\vendavo.war]: Deployment descriptor
    "web.xml" is malformed. Check against the DTD: org.
    xml.sax.SAXParseException: The content of element type "web-app" must
    match "(icon?,display-name?,description?,distribut
    able?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-map??ping*,session-config?,mime-mapping*,welcome-f
    ile-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-cons??traint*,login-config?,security-role*,env-entr
    y*,ejb-ref*,ejb-local-ref*)". (line 252, column 11).>
    java.lang.ExceptionInInitializerError
    at com.vendavo.cl.ClassHelper.<clinit>(ClassHelper.java:28)
    at
    com.vendavo.cl.io.ResourceHelper.addLoader(ResourceHelper.java:121)
    at
    com.vendavo.cl.io.ResourceHelper.<init>(ResourceHelper.java:39)
    at
    com.vendavo.cl.io.ResourceHelper.<clinit>(ResourceHelper.java:29)
    at
    com.vendavo.platform.action.StartupAction.init(StartupAction.java:75)
    at
    com.vendavo.platform.action.StartupAction.contextInitialized(StartupAction.??java:311)
    at
    weblogic.servlet.internal.WebAppServletContext$FireContextListenerAction.ru??n(WebAppServletContext.java:7044)
    at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubje??ct.java:321)
    at
    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at
    weblogic.servlet.internal.WebAppServletContext.notifyCreated(WebAppServletC??ontext.java:1753)
    at
    weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServl??etContext.java:3352)
    at
    weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:727)
    at
    weblogic.servlet.internal.WebService.preloadResources(WebService.java:486)
    at
    weblogic.servlet.internal.ServletInitService.resume(ServletInitService.java??:30)
    at
    weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
    at weblogic.Server.main(Server.java:32)
    Caused by: java.security.AccessControlException: access denied
    (java.util.PropertyPermission * read,write)
    at
    java.security.AccessControlContext.checkPermission(AccessControlContext.jav??a:269)
    at
    java.security.AccessController.checkPermission(AccessController.java:401)
    at
    java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
    at
    java.lang.SecurityManager.checkPropertiesAccess(SecurityManager.java:1243)
    at java.lang.System.getProperties(System.java:501)
    at
    com.vendavo.cl.property.AppProperties.loadSystemProperties(AppProperties.ja??va:411)
    at
    com.vendavo.cl.property.AppProperties.loadBasics(AppProperties.java:326)
    at
    com.vendavo.cl.property.AppProperties.getInstance(AppProperties.java:160)
    at com.vendavo.cl.log.VLog.loadAppProperties(VLog.java:134)
    at com.vendavo.cl.log.VLog.createDefaultSetup(VLog.java:94)
    at com.vendavo.cl.log.VLog.<clinit>(VLog.java:66)
    ... 18 more
    <Jun 16, 2006 4:33:34 PM IST> <Warning> <HTTP> <BEA-101162> <User
    defined listener com.vendavo.platform.action.StartupAc
    tion failed: java.lang.NoClassDefFoundError.>
    <Jun 16, 2006 4:33:34 PM IST> <Warning> <HTTP> <BEA-101162> <User
    defined listener com.vendavo.platform.action.StartupAc
    tion failed: java.lang.NoClassDefFoundError.>
    <Jun 16, 2006 4:33:34 PM IST> <Error> <HTTP> <BEA-101216> <Servlet:
    "AdminServlet" failed to preload on startup in Web a
    pplication: "soap".
    Thanks in Advance,
    Ketan.B.Parekh

  • NameNotFOundException in OC4J Connection Pool

    Hi,
    I am trying to implement connection pooling in OC4J.I modified the data-sources.xml file as follows:
    <!-- DataSource for Connection Pooling for MD Database -->
    <managed-data-source name="MDDS"
    connection-pool-name="SampleConnectionPool"
    jndi-name="jdbc/MDDS"/>
    <connection-pool name="SampleConnectionPool"
         min-connections="10"
         max-connections="100"
         inactivity-timeout="30">
    <connection-factory factory-class="oracle.jdbc.pool.OracleDataSource"
    user="xxx"
    password="xxx"
    url="jdbc:oracle:thin:@//localhost:1521/zzz">
    </connection-factory>
    </connection-pool>
    My Java Coding is as follows:
    javax.naming.InitialContext ic = new javax.naming.InitialContext();
         javax.sql.DataSource dataSource = (javax.sql.DataSource)ic.lookup("jdbc/MDDS");
         con = dataSource.getConnection();
    While executing the above code,I am getting "javax.naming.NameNotFoundException : jdbc/MDDS not found..
    Am I missing any step?.Thanks.

    Have you restarted the container?

  • Connection Pooling  How To ?

    Hi All ,
    i am developing a struts based web-application with JBoss 4.0.5 as Application Server and Oracle 10g Express edition .
    I am configuring my application for connection pooling .
    I have tried following methods :
    1. Oracle Connection Pooling following thius link http://www.lc.leidenuniv.nl/awcourse/oracle/java.920/a96654/connpoca.htm
    2. Configuring Jboss's Internal Container Level Connection pooling simply creating the datasources
    3. JDBC level Connection Pooling
    but unluckily did not succeed in any of these method .
    The application works OK with Second method but When it is being hit with 200 request/second The pool gets exhaulsted .
    i am unable to decide which approach i should be using as my application can receive large no. of requests around 1000/sec ?
    Please help me out ,
    Tell some useful link if possible ..
    Regards Jasdeep

    The pool can't do magic. If your database operations take ten seconds each, you get 1000 requests a second, and you have a pool size of 200, the pool will effectively empty instantly.
    You need to get some measurements of how long the typical transactions last and figure out an appropriate pool size for that. If it's more than the database can handle then you're going to have to upgrade.
    It's that simple.

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

    Hi,
    And thanks in advance for your support.
    In weblogic 12, managing to get the eclipse link connection sequencing mechanism when one uses Tables for sequencing entity ids seems to be complicated.
    QUICK REFERENCE:
    http://www.eclipse.org/eclipselink/api/2.5/org/eclipse/persistence/config/PersistenceUnitProperties.html
    The concept:
    While having EJB, MDBs etc... run on a JEE container, be it glassfish or weblogic, it should be possible to have the main thread transaction be managed as part of JTA global transactions by the contianer.
    Namely, pumping messages to JMS queues, persisting entities etc.
    Meanwhile, it should be also possible to as the transaction is on going write and update entity ids from sequencing tables.
    For this very purpose, eclipse link provides persistence.xml properties, such as the now deprecated eclipselink.jdbc.sequence-connection-pool" value="true", to fullfill this very purpose.
    This option greatly avoids dead longs, by allowing eclipse link to fetch a non JTA managed connection, pseudo "two phase locking read table update table" go to the datbase and fetch a new sequence.
    The same mechnism under JTA is a disaster. A transaction that creates ten different entities, might do ten reads and updates on this table, while mean while a competing transaction might be trying to do the same. It is guaranteed dead lock with minimal stress on the environment.
    Under glassfish, for example, tagging a persistence.xml with :
    <persistence-unit name="MY_PU" transaction-type="JTA">
            <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
            <jta-data-source>jdbc/DERBY_DS</jta-data-source>
            <non-jta-data-source>jdbc/DERBY_DS</non-jta-data-source>       
            <properties>           
                <property name="eclipselink.jdbc.sequence-connection-pool" value="true" />
            </properties>
    </peristence-unit>
    does miracles, when entities are using TABLE sequencing.
    Under weblogic, say you are using the Derby embedded XA driver with two phase commit, deploying the applicaiton immediately leads to:
    Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.3.v20120629-r11760): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: java.sql.SQLException: Cannot call commit when using distributed transactions
    Error Code: 0
      at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:324)
      at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicCommitTransaction(DatabaseAccessor.java:426)
      at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.commitTransaction(DatasourceAccessor.java:389)
      at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.commitTransaction(DatabaseAccessor.java:409)
      at org.eclipse.persistence.internal.sequencing.SequencingManager$Preallocation_Transaction_Accessor_State.getNextValue(SequencingManager.java:579)
      at org.eclipse.persistence.internal.sequencing.SequencingManager.getNextValue(SequencingManager.java:1067)
      at org.eclipse.persistence.internal.sequencing.ClientSessionSequencing.getNextValue(ClientSessionSequencing.java:70)
      at org.eclipse.persi
    While weblogic is right that their might be a distributed transaction ongoing, it is mistaken in the fact tha tthe connection requested by eclipse link for generating the ID should be part of the global transaciton.
    Eclipse link provides other ways to attempt to configure the sequencing mechanism, by sating for example a non-jta transaction.
    I have attempted also using these properties both withe original data DERBY_DS that uses the XA driver, and later with a new data source i created on purpose to try to work around the sequencing contengy.
    For example:
    <!--property name="eclipselink.jdbc.sequence-connection-pool.nonJtaDataSource" value="jdbc/DERBY_SEQUENCING_NON_JTA" /-->
                <!--property name="eclipselink.connection-pool.sequence.nonJtaDataSource" value="jdbc/DERBY_SEQUENCING_NON_JTA" /-->
    This new DERBY_SEQUENCING_NON_JTA is explicitly configured to use a NON_XA driver with global transactions flag set to disabled.
    Regardless, the only thing I get out of this is that the application is deployed and super fast, up to the point where i stress it with a system test that introduces some degreee of concurrency, and then I see the dead locks on the sequencing table.
    Meaning that the ongoing transactions are holding tight to their locks on the sequencing table.
    Is this a known issue?
    Is there something I am missing in the configuration?
    It really should not be this diffcult to get eclipse link to run its sequence reads and updates on a separate transaction of the main JTA transaction, but so far looks impossible.
    Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.3.v20120629-r11760): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested
    Error Code: 30000
    Call: UPDATE ID_GEN SET SEQ_VALUE = SEQ_VALUE + ? WHERE SEQ_NAME = ?
      bind => [2 parameters bound]
    Query: DataModifyQuery(name="MyEntity_Gen" sql="UPDATE ID_GEN SET SEQ_VALUE = SEQ_VALUE + ? WHERE SEQ_NAME = ?")
    Many thanks for your help.

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

  • WLS 10.0 JDBC connection pool shrink not working

    We seem to be having a problem with jdbc connection pools not shrinking. In the connection pool properties in the WLS console we have:
    Initial Capacity 4
    Maximum Capacity 15
    Shrink Frequency 900
    However when I look at the underlying xml config file (see below) the last two values above are not present in the config!
    Any ideas what is going on here?
    thankyou,
    Chris
    <?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:schemaLo
    cation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
    <name>mdmrDataSource</name>
    <jdbc-driver-params>
    <url>jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = xxxrac01-vip.nzlxxx01.com) (PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP) (HOST = xxxrac02-vip.nzlxxx01.com) (PORT = 1521)) (LOAD_BALANCE = yes) (CONNECT_DATA =(SERVE
    R = DEDICATED) (SERVICE_NAME = xxxrac.nzlami01.com)))</url>
    <driver-name>oracle.jdbc.pool.OracleDataSource</driver-name>
    <properties>
    <property>
    <name>user</name>
    <value>xxx_comms</value>
    </property>
    <property>
    <name>fastConnectionFailoverEnabled</name>
    <value>true</value>
    </property>
    <property>
    <name>implicitCachingEnabled</name>
    <value>true</value>
    </property>
    <property>
    <name>connectionCachingEnabled</name>
    <value>true</value>
    </property>
    <property>
    <name>ONSConfiguration</name>
    <value>nodes=xxxrac1:6251,xxxrac2:6251</value>
    </property>
    </properties>
    <password-encrypted>xxx</password-encrypted>
    </jdbc-driver-params>
    <jdbc-connection-pool-params>
    <initial-capacity>4</initial-capacity>
    <test-connections-on-reserve>true</test-connections-on-reserve>
    <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
    </jdbc-connection-pool-params>
    <jdbc-data-source-params>
    <jndi-name>jdbc/XXXX</jndi-name>
    <global-transactions-protocol>None</global-transactions-protocol>
    </jdbc-data-source-params>
    </jdbc-data-source>

    You are right that the XML seems to lask those other settings... Did you
    sae those settings from the console?
    This is what's in one of mine....
    <jdbc-connection-pool-params>
    <initial-capacity>0</initial-capacity>
    <max-capacity>300</max-capacity>
    <shrink-frequency-seconds>900</shrink-frequency-seconds>

Maybe you are looking for