9iAS Connection (DataSource) Pooling

We are having difficulty getting 9iAS DataSource Pooling to work. We are using 9iAS 9.0.3 (without Infrastructure) and, as per the J2EE Services Guide, have :
1) Added...
Context ic = new InitialContext();
DataSource ds (DataSource) ic.lookup("jdbc/OracleDS")
Connection con = ds.getConnection();
...to our code.
2) Modified the default DataSource's url, username, password, min-connections & max-connections from within Enterprise Manager (leaving ejb-location as is at "jdbc/OracleDS") and restarted the Instance.
The app generates an exception when trying to locate the OracleDS, however.
We have also tried replacing the "com.evermind.sql.DriverManagerDataSource" class with "oracle.jdbc.pool.OracleConnectionCacheImpl" as per another post's recommendation.
It appears that others have had similar problems (prior to 903?), but many have, in fact, (now) got this working successfully -- what are we missing please......?
Thanks.

Can you run the server with -Djbo.debugoutput=console property set on the vm command line and send us the detail exception, if any, thrown on the server console.

Similar Messages

  • Problem w/ DataSource Pooling

    We are having difficulty getting 9iAS DataSource Pooling to work. We are using 9iAS 9.0.3 (without Infrastructure) and, as per the J2EE Services Guide, have :
    1) Added...
    Context ic = new InitialContext();
    DataSource ds (DataSource) ic.lookup("jdbc/OracleDS")
    Connection con = ds.getConnection();
    ...to our code.
    2) Modified the default DataSource's url, username, password, min-connections & max-connections from within Enterprise Manager (leaving ejb-location as is at "jdbc/OracleDS") and restarted the Instance.
    The app generates an exception when trying to locate the OracleDS, however.
    We have also tried replacing the "com.evermind.sql.DriverManagerDataSource" class with "oracle.jdbc.pool.OracleConnectionCacheImpl" as per another post's recommendation.
    It appears that others have had similar problems (prior to 903?), but some have, in fact, (now) got this working successfully -- what are we missing please......?
    Thanks.

    we are coming up with a much clearer and simpler to use data-sources story, which, for now, is the following:
    1) if your component does not requires JTA services then you must use JDBC vendor specific data source such as oracle.jdbc.pool.OracleConnectioncacheImp -- only "location" JNDI context needs to be specified in data-sources.xml (and you must lookup the data source specified at this location -- you get JDBC (vendor's specific, in this case Oracle) pooling/caching
    2) if your component requires JTA services but does not require 2PC, then you must use OC4J emulated data sources DriverManagerDataSource -- "location", "ejb-location" and "xa-location" JNDI contexts must be specified in data-sources.xml but we strongly recommend to only lookup the data source specified at ejb-location -- you get OC4J connection pooling
    3) your component requires JTA AND 2PC services, you must use OC4J's non-emulated data sources OrionCMTDataSource -- only "location" JNDI context needs to be specified in data-sources.xml (and you must lookup the data source specified at this location -- you get Oracle JDBC pooling/caching -- look the doc for additional configuration (dblink, commit-coordinator, etc)
    Anything else will lead to unwanted behavior
    Kuassi

  • Using Ant task wlserver/wlconfig: Received exception while creating connection for pool.

    Hi,
    I am using ant tasks wlserver and wlconfig to configure my weblogic server. while creating a connection pool as shown below
    <target name="jdbcinfo">
    <wlconfig password="weblogic"
    username="weblogic"
    url="${url}"
    <query domain="mydomain" type="Server"
    name="myserver" property="serverbean"
    />
    <create type="JDBCConnectionPool"
    name="jdbcpoolA"
    property="jdbcPoolProp">
    <set value="false"
    attribute="ShrinkingEnabled"
    <set value
    attribute="
    <set value="${serverbean}"
    attribute="Targets"/>
    The JDBCConnectionPool is created as long as I don't specified the attribute "Targets"
    Once I add the target I get the following error
    <JDBC> <BEA-001129> <Received exception while creating connection for pool "poolname" invalid arguments in call>
    Please any help will be greatly appreciated.
    Thanks

    In your applicaion module configurations check if you are using 'JDBC URL' or 'JDBC DataSource'. You should use JDBC DataSource. Then make sure that your deployment descriptor (menu 'Application->Application Properties->Deployment) has the 'Auto Generate ...' checkbox set.
    Timo

  • Datasource pool are not recovered

    Sometimes in our environment, weblogic lose the connection with the database for any reason:
    - the network between weblogic server and data base server have some crash
    - the data base is out
    Most of the times, as soon as the connection is reestablished, the data source connections of the pool become available again. We have the properties 'test Frequency' and 'Test Table Name' setted.
    But, in some cases not yet identified, the datasource pool keeps unavailable. The datasource isn't recovered even if it is restarted. The only solution is to restart weblogic server (version 10.3.2).
    This happen in production and development environment. Unfortunately we couldn't map all variables that make this happen in order to reproduce it.
    Does anybody have faced the same problem? Any hint?
    Thanks. Mauro.

    You could try setting the property Test Connections On Reserve on the connection pool. Now the connection will be tested
    before it is given to the client.
    Also the Test Frequency property can be used to test unused connections if they are still valid. By default this is set to 120
    seconds.

  • Unable to get a connection for pool - ResourceUnavailableException

    Hi
    I have a BPEL process which starts a child instance of another asynchronous BPEL process for each message in an XML file. The child BPEL process makes a call to the Oracle Apps JCA Adapter to push the data into E-Business Suite.
    All works perfectly except when the number of messages exceeds a certain limit (15 or so). The error received is as follows:
    "Exception occured when binding was invoked.
    Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'SyncPersonRecord' failed due to:
    JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection.
    ebsPeoplesoftEmployees:SyncPersonRecord [ SyncPersonRecord_ptt::SyncPersonRecord(InputParameters,OutputParameters) ] :
    The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue:
    javax.resource.spi.ApplicationServerInternalException:
    Unable to get a connection for pool = 'eis/Apps/Apps',
    weblogic.common.resourcepool.ResourceUnavailableException:
    No resources currently available in pool eis/Apps/Apps to allocate to applications.
    Either specify a time period to wait for resources to become available, or increase the size of the pool and retry.. Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections.
    Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ".
    The invoked JCA adapter raised a resource exception.
    Please examine the above error message carefully to determine a resolution."
    Obviously what is happening is the connection pool maximum is reached (currently 15) and this is throwing the error.
    What I need to do is to implement the suggestion of "specifying a time period to wait" and I was hoping someone could tell me how I do this?
    I have tried setting the 'Connection Creation Retry Frequency' parameter to 30 seconds which made no difference and also have checked the documentation on "Configuring and Managing JDBC Data Sources for Oracle WebLogic Server".
    Does anyone know if this is something that is implemented directly in the BPEL process/composite or in the connection source itself.
    Many thanks

    Open the jndi : eis/Apps/Apps in /console - config tab - increase the initial and max conn capacity and save it. Retry the scenario

  • Datasource pool issues in weblogic

    Frequently,I am coming accross this error in my weblogic server log:Any pointers on how to resolve this? any help on this
    Adminlog:
    <Oct 15, 2013 12:11:35 PM GMT> <Info> <JDBC> <EPGCRMITG1> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-1d42ac6e:1419df56d93:-8000-0000000000003906> <1381839095305> <BEA-001128> <Connection for pool "LifeCycleDataSource-rac0" has been closed.>
    ####<Oct 15, 2013 12:11:35 PM GMT> <Info> <JDBC> <EPGCRMITG1> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-1d42ac6e:1419df56d93:-8000-0000000000003906> <1381839095354> <BEA-001128> <Connection for pool "LifeCycleDataSource-rac0" has been closed.>
    ####<Oct 15, 2013 12:11:35 PM GMT> <Info> <JDBC> <EPGCRMITG1> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-1d42ac6e:1419df56d93:-8000-0000000000003906> <1381839095356> <BEA-001128> <Connection for pool "LifeCycleDataSource-rac0" has been closed.>
    ####<Oct 15, 2013 12:12:36 PM GMT> <Warning> <JDBC> <EPGCRMITG1> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-1d42ac6e:1419df56d93:-8000-0000000000003906> <1381839156379> <BEA-001129> <Received exception while creating connection for pool "LifeCycleDataSource-rac0": IO Error: The Network Adapter could not establish the connection.>
    ####<Oct 15, 2013 12:12:36 PM GMT> <Info> <JDBC> <EPGCRMITG1> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-1d42ac6e:1419df56d93:-8000-0000000000003906> <1381839156381> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection
        at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:482)
        at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:678)
        at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:238)
        at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:34)
        at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:567)
        at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:357)
        at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:453)
        at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1841)
        at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1741)
        at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1647)
        at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1636)
        at weblogic.common.resourcepool.ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:2088)
        at weblogic.common.resourcepool.ResourcePoolImpl.access$1600(ResourcePoolImpl.java:41)
        at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2769)
        at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: oracle.net.ns.NetException: The Network Adapter could not establish the connection
        at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:398)
        at oracle.net.resolver.AddrResolution.resolveAndExecute(AddrResolution.java:438)
        at oracle.net.ns.NSProtocol.establishConnection(NSProtocol.java:711)
        at oracle.net.ns.NSProtocol.connect(NSProtocol.java:257)
        at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1222)
        at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:330)
        at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:678)
        at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:238)
        at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:34)
        at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:567)
        at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:357)
        at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:453)
        at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1841)
        at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1741)
        at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1647)
        at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1636)
        at weblogic.common.resourcepool.ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:2088)
        at weblogic.common.resourcepool.ResourcePoolImpl.access$1600(ResourcePoolImpl.java:41)
        at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2769)
        at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: java.net.SocketTimeoutException: connect timed out
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
        at java.net.Socket.connect(Socket.java:579)
        at oracle.net.nt.MetricsEnabledSocket.connect(TcpNTAdapter.java:631)
        at oracle.net.nt.TcpNTAdapter.connect(TcpNTAdapter.java:164)
    SOA Log:
    <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "ecoxproduct" failed with exception: "oracle.jdbc.xa.OracleXAException".>
    ####<Oct 16, 2013 3:53:48 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <[ACTIVE] ExecuteThread: '62' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-3ffef6c2:141a29a60f1:-8000-00000000000ff280> <1381938828168> <BEA-001128> <Connection for pool "ecoxproduct" has been closed.>
    ####<Oct 16, 2013 3:53:48 PM GMT> <Warning> <JTA> <EPGCRMITG1> <soa_server1> <[ACTIVE] ExecuteThread: '62' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-3ffef6c2:141a29a60f1:-8000-00000000000ff280> <1381938828181> <BEA-110484> <The JTA health state has changed from HEALTH_OK to HEALTH_WARN with reason codes: Resource ecoxproduct_base_domain declared unhealthy.>
    ####<Oct 16, 2013 3:53:48 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-3ffef6c2:141a29a60f1:-8000-00000000000ff282> <1381938828653> <BEA-001128> <Connection for pool "AIAJMSDS-rac0" has been closed.>
    ####<Oct 16, 2013 3:53:54 PM GMT> <Error> <JDBC> <EPGCRMITG1> <soa_server1> <FabricScheduler_QuartzSchedulerThread> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938834492> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "SOALocalTxDataSource" failed with exception: "java.sql.SQLRecoverableException: IO Error: Connection reset".>
    ####<Oct 16, 2013 3:53:54 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <FabricScheduler_QuartzSchedulerThread> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938834493> <BEA-001128> <Connection for pool "SOALocalTxDataSource" has been closed.>
    ####<Oct 16, 2013 3:53:58 PM GMT> <Error> <JDBC> <EPGCRMITG1> <soa_server1> <MDSPollingThread-[soa-infra, jdbc/mds/MDS_LocalTxDataSource]> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938838392> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "mds-soa" failed with exception: "java.sql.SQLRecoverableException: IO Error: Connection reset".>
    ####<Oct 16, 2013 3:53:58 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <MDSPollingThread-[soa-infra, jdbc/mds/MDS_LocalTxDataSource]> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938838393> <BEA-001128> <Connection for pool "mds-soa" has been closed.>
    ####<Oct 16, 2013 3:53:58 PM GMT> <Error> <JDBC> <EPGCRMITG1> <soa_server1> <MDSPollingThread-[owsm, jdbc/mds/owsm]> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938838393> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "mds-owsm" failed with exception: "java.sql.SQLRecoverableException: IO Error: Connection reset".>
    ####<Oct 16, 2013 3:53:58 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <MDSPollingThread-[owsm, jdbc/mds/owsm]> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938838394> <BEA-001128> <Connection for pool "mds-owsm" has been closed.>
    ####<Oct 16, 2013 3:53:58 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-3ffef6c2:141a29a60f1:-8000-00000000000ff284> <1381938838414> <BEA-001128> <Connection for pool "AIAJMSDS-rac0" has been closed.>
    ####<Oct 16, 2013 3:54:04 PM GMT> <Warning> <JDBC> <EPGCRMITG1> <soa_server1> <FabricScheduler_QuartzSchedulerThread> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938844505> <BEA-001129> <Received exception while creating connection for pool "SOALocalTxDataSource": IO Error: The Network Adapter could not establish the connection.>
    ####<Oct 16, 2013 3:54:04 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <FabricScheduler_QuartzSchedulerThread> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938844506> <BEA-001156> <Stack trace associated with message 001129 follows:
    This my connection pool parameters for  "ecoxproduct":
    Initial Capacity:1
    Maximum Capacity:5
    Minimun Capacity:1
    Statement Cache Type:LRU
    Statement Cache Size: 10
    Test Reserved Connections: uncheked
    Test Frequnct:120
    Test Table Name:SQL SELECT 1 FROM DUAL
    Seconds to trust ldle Poolconnection :10
    Shrink Frequency:900 SEC
    Connection cretion retry Frequncy   0
    Inactiv Connection time out:0
    Mixmunwaiting connetion:2147483647
    Connection Reserve Timeout: 10 SEC
    Thanku  you
    ram

    Hi,
    The database going down is most unlikely to happen,
    Things to check here by DBA:-
    1) If the SERVICE_NAME used in the JDBC string - This service_name might be intermittently unregistering itself from database listener
    2) If the SID is used in the JDBC string - Check if you have used proper SID name in case of RAC
    3) if SCAN_NAME is used - The scan_name also intermittently breaks the client connection.

  • Javax.servlet.ServletException: Unable to get connection,DataSource invalid

    Can somebody explain this error to me please
    javax.servlet.ServletException: Unable to get connection, DataSource invalid: "org.apache.commons.dbcp.SQLNestedException:
    Cannot create PoolableConnectionFactory (Server connection failure during transaction. Due to underlying exception:
    'java.security.AccessControlException: access denied (java.net.SocketPermission localhost resolve)'.
    ** BEGIN NESTED EXCEPTION **
    java.security.AccessControlException
    MESSAGE: access denied (java.net.SocketPermission localhost resolve)
    STACKTRACE:
    java.security.AccessControlException: access denied (java.net.SocketPermission localhost resolve)
         at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
         at java.security.AccessController.checkPermission(AccessController.java:427)
         at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
         at java.lang.SecurityManager.checkConnect(SecurityManager.java:1031)
         at java.net.InetAddress.getAllByName0(InetAddress.java:1117)
         at java.net.InetAddress.getAllByName0(InetAddress.java:1098)
         at java.net.InetAddress.getAllByName(InetAddress.java:1061)
         at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:138)
         at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:277)
         at com.mysql.jdbc.Connection.createNewIO(Connection.java:2817)
         at com.mysql.jdbc.Connection.<init>(Connection.java:1531)
         at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
         at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37)
         at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
         at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877)
         at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851)
         at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540)
         at org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.getConnection(QueryTagSupport.java:274)
         at org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.doStartTag(QueryTagSupport.java:159)
         at org.apache.jsp.index_jsp._jspx_meth_sql_query_0(index_jsp.java:100)
         at org.apache.jsp.index_jsp._jspService(index_jsp.java:58)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:275)
         at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:161)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:245)
         at org.apache.catalina.core.ApplicationFilterChain.access$0(ApplicationFilterChain.java:177)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:156)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:152)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
         at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
         at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
         at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
         at java.lang.Thread.run(Thread.java:595)
    ** END NESTED EXCEPTION **
    Attempted reconnect 3 times. Giving up.)"
         org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:843)
         org.apache.jasper.runtime.PageContextImpl.access$11(PageContextImpl.java:781)
         org.apache.jasper.runtime.PageContextImpl$12.run(PageContextImpl.java:763)
         java.security.AccessController.doPrivileged(Native Method)
         org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:761)
         org.apache.jsp.index_jsp._jspService(index_jsp.java:81)
         org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
         org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
         org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         java.lang.reflect.Method.invoke(Method.java:585)
         org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243)
         java.security.AccessController.doPrivileged(Native Method)
         javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:275)
         org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:161)

    The URL url="jdbc:mysql://localhost:3306/wroxcatalog" looks right to me...wroxcatalog is the MySQL database.
    <%@ page language="java" contentType="text/html; charset=ISO-8859-1"
        pageEncoding="ISO-8859-1"%>
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    <%@ include file="include.jsp"%>
    <sql:setDataSource
         var="datasource"
         driver="com.mysql.jdbc.Driver"
         url="jdbc:mysql://localhost:3306/wroxcatalog"
         user="wroxuser"
         password="wrox" />
    <sql:query var="books" dataSource="${datasource}">
         select id, name, description, price from products order by id
    </sql:query>
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
    <title>TryDB</title>
    </head>
    <body>
    <table border="1">
         <tr>
              <td>ID</td><td>Name</td><td>Description</td><td>Price</td>
         </tr>
              <c:forEach items="${books.rows}" var="row">
                   <tr>
                        <td><c:out value="${row.id}"/></td>
                        <td><c:out value="${row.name}"/></td>
                        <td><c:out value="${row.description}"/></td>
                        <td><c:out value="${row.price}"/></td>
                   </tr>
              </c:forEach>
    </table>
    </body>
    </html>

  • Oracle 9.i Driver issues when connecting a pool in WLS6.1

    Ok. Ammendment to other message as I haven't gotten a solution yet. My problem is
    I am using Oracle 9.i on a Sun UNIX box and using Weblogic 6.1 SP2 on another box.
    Trying to connect a pool between the two of them.
    Obviously, there has to be a way to do this but none of the documentation seems to
    tell you how. I am used to doing MS SQL drivers on NT so I am a little new to this.
    I would appreciate it if someone has a solution to this problem that will help me.
    The error I am getting is as follows:
    Starting Loading jDriver/Oracle .....
    <Jun 7, 2002 9:04:25 AM CDT> <Error> <JDBC> <Cannot startup connection pool "FargoPool"
    weblogic.common.ResourceException:
    Could not create pool connection. The DBMS driver exception was:
    java.sql.SQLException: System.loadLibrary(weblogicoci37) threw java.lang.UnsatisfiedLinkError:
    /usr/local/wlserver6.1/lib/solaris/oci901_8/libweblogicoci37.so: ld.so.1: /home/bea/jdk131/jre/bin/../bin/sparc/native_threads/java:
    fatal: libclntsh.so.9.0: open failed: No such file or directory
    at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:226)
    at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:193)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
    at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
    at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
    at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
    at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy8.addDeployment(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
    at $Proxy17.setTargets(Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
    at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
    at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
    at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:209)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
    at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
    at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
    at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
    at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy8.addDeployment(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
    at $Proxy17.setTargets(Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
    at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
    at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
    at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    Ok. Ammendment to other message as I haven't gotten a solution yet. My problem is
    I am using Oracle 9.i on a Sun UNIX box and using Weblogic 6.1 SP2 on another box.
    Trying to connect a pool between the two of them.
    Obviously, there has to be a way to do this but none of the documentation seems to
    tell you how. I am used to doing MS SQL drivers on NT so I am a little new to this.
    I would appreciate it if someone has a solution to this problem that will help me.
    The error I am getting is as follows:
    Starting Loading jDriver/Oracle .....
    <Jun 7, 2002 9:04:25 AM CDT> <Error> <JDBC> <Cannot startup connection pool "FargoPool"
    weblogic.common.ResourceException:
    Could not create pool connection. The DBMS driver exception was:
    java.sql.SQLException: System.loadLibrary(weblogicoci37) threw java.lang.UnsatisfiedLinkError:
    /usr/local/wlserver6.1/lib/solaris/oci901_8/libweblogicoci37.so: ld.so.1: /home/bea/jdk131/jre/bin/../bin/sparc/native_threads/java:
    fatal: libclntsh.so.9.0: open failed: No such file or directory
    at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:226)
    at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:193)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
    at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
    at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
    at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
    at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy8.addDeployment(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
    at $Proxy17.setTargets(Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
    at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
    at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
    at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:209)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
    at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
    at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
    at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
    at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy8.addDeployment(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
    at $Proxy17.setTargets(Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
    at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
    at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
    at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

  • Returning Connections to Pool

    Does anyone know how long iAS 6.5 SP1 (on W2K) takes to return connections to the pool after close() is called? Does the app server wait until the end of a transaction to return connections to the pool, even if close() was called earlier?

    Hello,
    I understand that a good code must release resources
    exactly.
    But the problem is that I have 50 coders that write
    thousand of JSPs and not all of them write a good
    code. You need to hold code reviews. You can't try to band-aid the situation, you have to have standards, conventions, etc.
    And it is impossible to check & debug every JSP
    for resource-leaking (a question of time-money). This is a design problem. If you are putting code inside of JSP's (which I believe is a bad thing), then you will pay the price. If you use JSP's for presentation only, then you don't need to worry about this, much.
    It is very important for a stable system that allocated
    resources must be released in every case early of
    late. The good idea is to use GC to control
    finalization & releasing of resources. In this way
    for example it makes every application server to
    return allocated db connection to pool. It works
    perfectly with local VM.No, no, no. Don't use GC to control ANYTHING. Release the resources back to the server when you're done with them, not when the object is getting collected.
    Remote GC uses object expiration time (TTL) that
    equals 15 minutes. If rmi have not received "ping"
    for that objects from remote system during this time,
    they are finalized locally. The time of 15 minutes is
    reasonable for some objects type, but some resources
    (like db connections from pool) required to be
    finalized more rapidly. Is there any method to set
    manually the TTL for rmi object?Again, don't do this. You're shooting yourself in the foot. Create all the timers you want, but don't rely on the GC.

  • Error making initial connections for pool

              I'm using WLS6.1 on NT, trying my personal implementation of a connector (non
              CCI pattern) with a particular EIS.
              i'm having this error... what depends from?:
              ####<25-ott-00 19.52.41 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
              <main> <system> <> <190014> <Initializing connection pool for resource adapter
              BlackBoxNoTx.>
              ####<25-ott-00 19.52.42 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
              <main> <system> <> <190010> <Unable to determine Resource Principal for Container
              Managed Security Context.>
              ####<25-ott-00 19.52.42 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
              <main> <system> <> <190035> <There was/were 1 physical connection(s) created with
              the following Meta Data: Product name of EIS instance: DBMS:cloudscape Product
              version of EIS instance: 3.5.1 Maximum number of connections supported from different
              processes: 0 User name for connection: null>
              ####<25-ott-00 19.52.42 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
              <main> <system> <> <190026> << BlackBoxNoTx > Connection Pool initialization has
              completed successfully.>
              ####<25-ott-00 19.52.42 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
              <main> <system> <> <190014> <Initializing connection pool for resource adapter
              SMJConnector.>
              ####<25-ott-00 19.52.42 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
              <main> <system> <> <190010> <Unable to determine Resource Principal for Container
              Managed Security Context.>
              ####<25-ott-00 19.52.47 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
              <main> <system> <> <190010> <Unable to determine Resource Principal for Container
              Managed Security Context.>
              ####<25-ott-00 19.53.06 CEST> <Error> <Connector> <semarmw0780> <examplesServer>
              <main> <system> <> <190024> << SMJConnector > Error making initial connections
              for pool. Reason: examplescnnct.ConnectionImpl>
              ####<25-ott-00 19.53.06 CEST> <Warning> <Connector> <semarmw0780> <examplesServer>
              <main> <system> <> <190025> << SMJConnector > Connection Pool has been initialized
              with no connections.>
              ####<25-ott-00 19.53.06 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
              <main> <system> <> <190026> << SMJConnector > Connection Pool initialization has
              completed successfully.>
              ####<25-ott-00 19.54.30 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
              <Application Manager Thread> <> <> <190027> << SMJConnector > Shutting down connections.>
              ####<25-ott-00 19.54.30 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
              <Application Manager Thread> <> <> <190028> << SMJConnector > Connections shutdown
              successfully.>
              

    Have you configured your principal map? Connection pools are initially populated using the
              default ("*") principal from the map.
              http://edocs.bea.com/wls/docs61/jconnector/config.html#1237429
              HTH.
              FilAiello wrote:
              > I'm using WLS6.1 on NT, trying my personal implementation of a connector (non
              > CCI pattern) with a particular EIS.
              >
              > <examplesServer>
              > <main> <system> <> <190010> <Unable to determine Resource Principal for Container
              > Managed Security Context.>
              > ####<25-ott-00 19.52.42 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
              Tom Mitchell
              [email protected]
              Very Current Beverly, MA Weather
              http://www.tom.org:8080
              

  • Transport for DB connect datasource

    Hi
    I have a query for DB connect datasources.
    I have created datasources for ORACLE quality system in SAP BI DEV. If I transported all the objects from SAP  DEV to SAP prod directly is there be any problem?
    Or I need to create the same datasource also for Oracle production system.
    Can anybody through a light how object transport happens in DB coonect scenario.
    Thanks
    Debasish

    Hi,
    As your scenario, i can understand that you have got :
    Oracle Quality connected with the BW Development.
    So if you transport BW Development to your BW Production, then there should atleast
    Oracle Production connected with the BW Production. (As your data Source created is based on the oracle system)."if this is the scenario in your case then transport your Table or view from Oracle Dev to Oracle Prod"
    Now you have to more specific that what kind of connection you have in your BW Production with oracle.
    Hope This Helps.
    Regards,
    Soumyadeep.

  • Enhance UD connect Datasource

    Hi Experts,
    we are creating a UD connect Datasource based on a View which has 10 fields.
    Now we want to add an extra field in the Datasource which is not present in the View (which we are using to create the datasource), please advice how to achieve this.
    I am not able to add the extra field in the UD Connect datasource. Same thing i was able to do when the source is Flat File.
    Thanks in advance.
    Regards,
    Rk.

    Hi M,
    Thanks for the reply,
    The field is already available in the Data Target. Reason for adding this in Datasource is that for reporting purpose we are modifying the source record such that each record is converted to 19 records while transformations.
    Along with this we have some validations to be done which will consume less time if done before the above conversion or columns to rows.
    Is there any way we can add that field in the DataSource?
    Regards,
    Rk.

  • How can I know the connections are pooled?

    Hi. everyone.
    I am wondering how I can monitor the connections are pooled.
    I am using web-logic as a web server and oracle9ir2 as a
    database server.
    When I was deploying an application to the web-logic, I created a
    connection pool.
    And then, I run the application respectively(exactly two).
    However, there is only one session in the "V$SESSION" dictionary.
    I do not understand why there is only session in the V$SESSION, although
    I run two application respectively.
    In addition, how can I monitor the oracle conenctions are pooled?
    Does V$SESSION have nothing to do with oracle connection pool?
    Thanks in advance.
    Have a good day.
    Best Regards
    Ho.

    Dear Sabdar Syed.
    Thanks for your reply.
    Here is the result of v$license.
    SQL> select * from v$license;
    SESSIONS_MAX : 0
    SESSIONS_WARNING : 0
    SESSIONS_CURRENT : 6
    SESSIONS_HIGHWATER : 6
    USERS_MAX : 0
    What does it mean, sessions_max(0), sessions_current(6), users_max(0)
    I am still confused.
    Could you give me a more detailed explanations?
    Thanks in advance. Have a good day.
    Regards.
    Ho.

  • How do I set miminum # of connections for pool with Oracle and Tomcat?

    Hi,
    I can't seem to find any attribute to initialize the number of connections for my connection pool. Here is my current context.xml file under my /App1 directory:
    <Context path="/App1" docBase="App1"
    debug="5" reloadable="true" crossContext="true">
    <Resource name="App1ConnectionPool" auth="Container"
    type="oracle.jdbc.pool.OracleDataSource"
    driverClassName="oracle.jdbc.driver.OracleDriver"
    factory="oracle.jdbc.pool.OracleDataSourceFactory"
    url="jdbc:oracle:thin:@127.0.0.1:1521:oddjob"
    user="app1" password="app1" />
    </Context>
    I've been googling and reading forums, but haven't found a way to establish the minimum number of connections. I've tried all sorts of parameters like InitialLimit, MinLimit, MinActive, etc, with no success.
    Here is some sample code that I am testing:
    package web;
    import oracle.jdbc.pool.OracleDataSource;
    import oracle.jdbc.OracleConnection;
    import javax.naming.*;
    import java.sql.SQLException;
    import java.sql.ResultSet;
    import java.sql.Statement;
    import java.util.Properties;
    public class ConnectionPool {
    String message = "Not Connected";
    public void init() {
    OracleConnection conn = null;
    ResultSet rst = null;
    Statement stmt = null;
    try {
    Context initContext = new InitialContext();
    Context envContext = (Context) initContext.lookup("java:/comp/env");
    OracleDataSource ds = (OracleDataSource) envContext.lookup("App1ConnectionPool");
    message = "Here.";
         String user = ds.getUser();
    if (envContext == null)
    throw new Exception("Error: No Context");
    if (ds == null)
    throw new Exception("Error: No DataSource");
    if (ds != null) {
    message = "Trying to connect...";
    conn = (OracleConnection) ds.getConnection();
    Properties prop = new Properties();
    prop.put("PROXY_USER_NAME", "adavey/xxx");
    if (conn != null) {
    message = "Got Connection " + conn.toString() + ", ";
              conn.openProxySession(OracleConnection.PROXYTYPE_USER_NAME,prop);
    stmt = conn.createStatement();
    rst = stmt.executeQuery("SELECT username, server from v$session where username is not null");
    while (rst.next()) {
    message = "DS User: " + user + "; DB User: " + rst.getString(1) + "; Server: " + rst.getString(2);
    rst.close();
    rst = null;
    stmt.close();
    stmt = null;
    conn.close(); // Return to connection pool
    conn = null; // Make sure we don't close it twice
    } catch (Exception e) {
    e.printStackTrace();
    } finally {
    // Always make sure result sets and statements are closed,
    // and the connection is returned to the pool
    if (rst != null) {
    try {
    rst.close();
    } catch (SQLException e) {
    rst = null;
    if (stmt != null) {
    try {
    stmt.close();
    } catch (SQLException e) {
    stmt = null;
    if (conn != null) {
    try {
    conn.close();
    } catch (SQLException e) {
    conn = null;
    public String getMessage() {
    return message;
    I'm using a utility to repeatedly call a JSP page that uses this class and displays the message variable. This utility allows me to specify the number of concurrent web requests and an overall number of requests to try. While that is running, I look at V$SESSION in Oracle and occassionaly, I will see a brief entry for app1 or adavey depending on the timing of my query and how far along the code has processed in this example. So it seems that I am only using one connection at a time and not a true connection pool.
    Is it possible that I need to use the oci driver instead of the thin driver? I've looked at the javadoc for oci and the OCIConnectionPool has a setPoolConfig method to set initial, min and max connections. However, it appears that this can only be set via Java code and not as a parameter in my context.xml resource file. If I have to set it each time I get a database connection, it seems like it sort of defeats the purpose of having Tomcat maintain the connection pool for me and that I need to implement my own connection pool. I'm a newbie to this technology so I really don't want to go this route.
    Any advice on setting up a proper connection pool that works with Tomcat and Oracle proxy sessions would be greatly appreciated.
    Thanks,
    Alan

    Well I did some more experiments and I am able to at least create a connection pool within my example code:
    package web;
    import oracle.jdbc.pool.OracleDataSource;
    import oracle.jdbc.OracleConnection;
    import javax.naming.*;
    import java.sql.SQLException;
    import java.sql.ResultSet;
    import java.sql.Statement;
    import java.util.Properties;
    public class ConnectionPool {
    String message = "Not Connected";
    public void init() {
    OracleConnection conn = null;
    ResultSet rst = null;
    Statement stmt = null;
    try {
    Context initContext = new InitialContext();
    Context envContext = (Context) initContext.lookup("java:/comp/env");
    OracleDataSource ds = (OracleDataSource) envContext.lookup("App1ConnectionPool");
    message = "Here.";
         String user = ds.getUser();
    if (envContext == null)
    throw new Exception("Error: No Context");
    if (ds == null)
    throw new Exception("Error: No DataSource");
    if (ds != null) {
    message = "Trying to connect...";
    boolean cache_enabled = ds.getConnectionCachingEnabled();
    if (!cache_enabled){
    ds.setConnectionCachingEnabled(true);
    Properties cacheProps = new Properties();
    cacheProps.put("InitialLimit","5");
         cacheProps.put("MinLimit","5");
    cacheProps.put("MaxLimit","10");
    ds.setConnectionCacheProperties(cacheProps);
              conn = (OracleConnection) ds.getConnection();
    Properties prop = new Properties();
    prop.put("PROXY_USER_NAME", "adavey/xyz");
    if (conn != null) {
    message = "Got Connection " + conn.toString() + ", ";
              conn.openProxySession(OracleConnection.PROXYTYPE_USER_NAME,prop);
    stmt = conn.createStatement();
    //rst = stmt.executeQuery("SELECT 'Success obtaining connection' FROM DUAL");
    rst = stmt.executeQuery("SELECT user, SYS_CONTEXT ('USERENV', 'SESSION_USER') from dual");
    while (rst.next()) {
    message = "DS User: " + user + "; DB User: " + rst.getString(1) + "; sys_context: " + rst.getString(2);
    message += "; Was cache enabled?: " + cache_enabled;
    rst.close();
    rst = null;
    stmt.close();
    stmt = null;
    conn.close(OracleConnection.PROXY_SESSION); // Return to connection pool
    conn = null; // Make sure we don't close it twice
    } catch (Exception e) {
    e.printStackTrace();
    } finally {
    // Always make sure result sets and statements are closed,
    // and the connection is returned to the pool
    if (rst != null) {
    try {
    rst.close();
    } catch (SQLException e) {
    rst = null;
    if (stmt != null) {
    try {
    stmt.close();
    } catch (SQLException e) {
    stmt = null;
    if (conn != null) {
    try {
    conn.close();
    } catch (SQLException e) {
    conn = null;
    public String getMessage() {
    return message;
    In my context.xml file, I tried to specify the same Connection Cache Properties as attributes, but no luck:
    <Context path="/App1" docBase="App1"
    debug="5" reloadable="true" crossContext="true">
    <Resource name="App1ConnectionPool" auth="Container"
    type="oracle.jdbc.pool.OracleDataSource"
    driverClassName="oracle.jdbc.OracleDriver"
    factory="oracle.jdbc.pool.OracleDataSourceFactory"
    url="jdbc:oracle:thin:@127.0.0.1:1521:oddjob"
    user="app1" password="app1"
    ConnectionCachingEnabled="1" MinLimit="5" MaxLimit="20"/>
    </Context>
    These attributes seemed to have no effect:
    ConnectionCachingEnabled="1" ; also tried "true"
    MinLimit="5"
    MaxLimit="20"
    So basically if I could find some way to get these attributes set within the context.xml file instead of my code, I would be a happy developer :-)
    Oh well, it's almost Miller time here on the east coast. Maybe a few beers will help me find the solution I'm looking for.

  • Job Scheduler DS consumes all connections in Pool.

    Hi all,
    I use Weblogic 12.1.3.
    My objective is to create a job scheduler, with commonj Timer API to run a in a cluster environment.
    For this, I created a cluster with two node servers (I created this in the integrated weblogic server in Jdeveloper, for simplicity).
    Then I created the DataSource which points to the table where the weblogic_timers and active tables are, which are needed for persistance of the timers, targeted this DS on the nodes in the cluster, and then went to the Cluster -> Configuration -> Scheduling and selected the respective data source as "Data Source For Job Scheduler".
    After I do this and the servers are up, all the connections in the DS pool are consumed. It seems like connections are continuosly made from weblogic to the database.
    The connection itself seems ok, since I can connect from SQLDeveloper and also tested it when I created the DataSource.
    If I have a look in the logs of the two servers, I see errors like this:
    <BEA-000627> <Reached maximum capacity of pool "JDBC Data Source-2", making "0" new resource instances instead of "1".>
    Can you give me an idea of what the issue might be?
    Please let me know if I should provide more information.
    Thanks.

    It's not an issue WebLogic can address. The thortech application is independently using
    the UCP connection pool product, not WebLogic connection pooling, so Thortech APIs
    would be the only way to debug/reconfigure the UCP.

Maybe you are looking for