Problem in Connection pooling after deploying BC4J App Module as EJB

Hi,
We have deployed the application modules on standalone OC4J as stateful EJB session beans.
The problem is that with each user, the number of database connections seem to increase. This is making the application unscalable, which defeats the purpose of using EJB!
Can someone please suggest how to limit the number of database conections in this scenario?
Can this be solved by application module pooling? How can we use the PoolMgr to work with the session beans?
We have tried to invoke disconnect on the application module after calling methods(using appmodule.disconnect(true)) and reconnect (appmodule.reconnect()) on entering the method. This keeps the number of connections low and works the first time the method is invoked. But subsequently, it gives nullpointerexception when the Row is accessed in the JSP.
The exception we are getting is :
java.lang.NullPointerException
     at oracle.jbo.client.remote.ViewUsageImpl.getStructDef(ViewUsageImpl.java:241)
     at oracle.jbo.client.remote.ViewUsageImpl.findAttributeDef(ViewUsageImpl.java:275)
     at oracle.jbo.client.remote.RowImpl.getAttributeIndexOf(RowImpl.java:368)
     at oracle.jbo.client.remote.RowImpl.getAttribute(RowImpl.java:144)
     at Supplier.client.ejb.beanmanaged.SupplierAM_IntPaymtVORowBeanManagedClient.getMdid(SupplierAM_IntPaymtVORowBeanManagedClient.java:63)
     at supplier.sccPayCheq._jspService(_sccPayCheq.java:102)
     [SRC:/Supplier/sccPayCheq.jsp:44]
The Application module configuration (in bc4j.xcfg) is:
<AppModuleConfig name="SupplierAM9iAS">
<AppServerConnectionName>StandaloneOC4JConnection</AppServerConnectionName>
<AppModuleJndiName>Supplier.SupplierAM</AppModuleJndiName>
<java.naming.security.credentials>admin</java.naming.security.credentials>
<DeployPlatform>EjbIas</DeployPlatform>
<java.naming.security.principal>admin</java.naming.security.principal>
<DtMiddleTierDeploymentProfile>ProjectMiddleTier.deploy</DtMiddleTierDeploymentProfile>
<ApplicationName>Supplier.SupplierAM</ApplicationName>
<DtDeploymentProfile>ProjectEJB.deploy</DtDeploymentProfile>
<DtCommonDeploymentProfile>ProjectCommon.deploy</DtCommonDeploymentProfile>
<JDBCDataSource>jdbc/ConnectionCoreDS</JDBCDataSource>
<jbo.server.internal_connection>jdbc/ConnectionCoreDS</jbo.server.internal_connection>
<jbo.ejb.txntype>local</jbo.ejb.txntype>
<jbo.doconnectionpooling>true</jbo.doconnectionpooling>
<ApplicationPath>ProjectEJB</ApplicationPath>
</AppModuleConfig>
The Datasource used (in $ORACLE_HOME/j2ee/home/config/data-sources.xml) is:
<data-source
          class="oracle.jdbc.pool.OracleConnectionCacheImpl"           connection-driver="oracle.jdbc.driver.OracleDriver"
          ejb-location="jdbc/ConnectionDS"
          inactivity-timeout="30"
          location="jdbc/ConnectionCoreDS"
          name="ConnectionDS"
          password="*******"
          pooled-location="jdbc/ConnectionPooledDS"
          url="jdbc:oracle:thin:@<IPADDESS>:<SID>"
          username="USER"
          xa-location="jdbc/xa/ConnectionXADS"
          max-connections="5"
          min-connections="1"/>

Can this be solved by application module pooling? How
can we use the PoolMgr to work with the session
beans?You can use a stateless checkout/checkin appmodule.
Take a look at the following help topics which explain this in good detail.
"About Application Module Pooling"
"About JSP Pages and Application Module Pooling"
The pool can help reuse the appmodule instance across requests thus reducing the number of concurrent db sessions.
Dhiraj

Similar Messages

Problems using connection pooling

I'm having problems configuring connection pooling in oc4j. Have specified my datasource/connection pool in my data-sources.xml. I always get the following error when I try to access it with an instance of OracleConnectionPoolDataSource within my apps. The app server dosen't seem to create the connections when started 'cos its not displayed within Oracle dba studio. Can anyone tell what I need to do pls.
regards!
dyzke
//-- error displayed
Exception in thread "main" java.sql.SQLException: Io exception: The Network Adap
ter could not establish the connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:323)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:260)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.ja
va:365)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java
:111)
// -- extract
<data-source
          class="com.evermind.sql.DriverManagerDataSource"
name="MYDS"
          location="jdbc/XXX"
xa-location="jdbc/xa/OracleXADS"
          ejb-location="jdbc/OracleDS"
pooled-location="xxx/xxxx"
          max-connections="10"
          min-connections="3"
          connection-driver="oracle.jdbc.driver.OracleDriver"
          username="admin"
          password="admin"
          url="jdbc:oracle:thin:@localhost:xxx"
          inactivity-timeout="30"
     />

see my answer in the other newsgroup.
please don't cross post.
"M. Hammer" <[email protected]> wrote in message
news:[email protected]..
Hi,
We have problems using connection pooling in a WLS 5.1.x - Cluster. Is it
possible to use CP in such a cluster at all ? The problem is, connections
will be opened and never been closed. How can I configure a cluster forCP?
>
I have a WLS-Cluster with 2 instances and my webApp uses connectionpooling.
By the way I get a connection on Instance 1, Instance 2 gets a connection
also, but never releases it.
In my opinion, the reference to the connection in the partner-instancewill
be lost.
How do I have to configure my cluster to work well with that stuff ?
Thank a lot,
Markus.

My iphone 5 and ipad 4th generation having the same problem of connecting to wifi, cannot load app store and cannot connect to itune store... help !!

my iphone 5 and ipad 4th generation having the same problem of connecting to wifi, cannot load app store and cannot connect to itune store... help !!

Try this:
1. Close all apps in the Task Bar. Double-click the Home button and hold apps down for a second or two. Tap the minus sign to close app.
2. Hold the Sleep and Home button down until you see the Apple Logo.

Deploying App Module as EJB Session Bean to JBoss

I am attempting to follow the How-To at
http://otn.oracle.com/products/jdev/howtos/appservers/deploy_bc4j_to_jboss.html for deploying BC4J to JBoss. In particular, I was looking at the section 'BC4J as an EJB Session Bean', because that is the route we would like to take.
The document instructs you to create a business components deployment profile.. ok, done.
It then instructs you to copy the app module configuration that was just created and rename it. However, the editor will not let you rename the configuration.
Then when 'Creating a JSP to Access Your Application Module as a EJB', the wizard to create the JSP will not allow you to select the app module configuration that was just created. It only shows the Local configuration.
What am I doing wrong? I am using JDeveloper 9.0.3.1.
My ultimate goal is to take an existing BC4J/JSP application and deploy the app module as an EJB, so the JSP and EJB can reside on separate machines.
Any pointers that anyone can give me about deploying an app module as a Session Facade (BMT) to JBoss, with a JSP front end, is greatly appreciated. I have read the how-tos available from OTN. I have relatively little experience with EJB, so please forgive me if there's something obvious I'm missing.
Thanks!!!

Can this be solved by application module pooling? How
can we use the PoolMgr to work with the session
beans?You can use a stateless checkout/checkin appmodule.
Take a look at the following help topics which explain this in good detail.
"About Application Module Pooling"
"About JSP Pages and Application Module Pooling"
The pool can help reuse the appmodule instance across requests thus reducing the number of concurrent db sessions.
Dhiraj

Connection failure after deploying to 10.1.3 app server

I am working on a three-tier application that uses session EJB facades and TopLink for persistence. I configured a datasource in the embedded OC4J server preferences in JDeveloper (10.1.3) and can successfully deploy my persistence code to the embedded server and access it from a test client.
I recently installed Oracle App Server 10g 10.1.3 to be used for integration testing. In JDeveloper, I configured a new application server connection and EJB Jar deployment profile to allow me to deploy my persistence code to the new server. When I deploy my code to the server and attempt to use one of the session EJB persistence methods, I get the following exception message:
Internal Exception: java.sql.SQLException: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.Error Code: 0
In the Oracle Enterprise Manager, my application is running and the datasource and connection pool test successfully.
If I restart OC4J from Oracle Enterprise Manager, my application works correctly, at least until I have to deploy new code to the server, at which time the above error reappears. My question: Should OC4J have to be restarted each time new code is deployed? I am not making any changes to the datasource or connection pool configurations. Thanks.

Thanks Jaap.
I was told recently by someone at Oracle that Forms/Reports is supported on 10.1.3.x and eventually on 11g (not yet released), and I was also told 10.1.3 doesn't require two servers, but I'm having trouble finding much to support either claim.
Reason I'm asking is that we're currently using the client/server Forms/Reports and need to decide on a migration path and l don't know if it's wise to continue with the 10.1.2 App Server knowing it's going to be de-supported in a few short years and I don't want to go with 10.1.3 if it requires additional servers (we're small). We're looking at APEX as a possible alternative...
Tim

Failed to obtain/create connection from connection pool after redeploy

I have a web application (.war) that uses a jdbc connection pool. The application works fine, however after I redeploy it using the administration console I get "Failed to obtain/create connection from connection pool [ Datavision_Pool ]. Reason : null" followed by "Error allocating connection : [Error in allocating a connection. Cause: null]" from javax.enterprise.resource.resourceadapter and I am forced to restart the instance. I am running Sun Java System Application Server 9.1 (build b58g-fcs)
using a connection pool to a Microsoft SQL 2000 database using inet software's JDBC drivers. I need to be able to redeploy applications without having to restart the instance. Any help is appreciated.

I have turned on some additional diagnostics and found out some answers and a work-around, but I think that there may be a bug in the way JDBC connection pool classes are loaded. The actual error was a null pointer in the JDBC driver class in the perpareStatement method. The only line in this method is "return factory.createPreparedStatement( this , sql );" and the only possible NPE would be if the factory was null, which should be impossible because it is a static variable and it is initialized when the class is loaded. The problem occurs because we deploy the JDBC driver .jar file within our .war file, for use when a client doesn't have or want to use connection pooling. Apparently, the connection pool must have picked up some of these classes and when the .war was redeployed, the reference to the factory was lost for existing connections (not sure how). If I remove the JDBC .jar file from the .war, it works, but that wasn't an ideal solution, the other way to get it to work was to change the sun-web.xml file to have <class-loader delegate="true">. We previously had it set to false in version 8.1 because of interference with a different version of the apache Tiles classes, which has now been addressed in version 9.1.
I still think there is an issue, because the connection pool should never use the application specific classloaders. Am I wrong to believe this?

Problem creating connection pool to mysql database

Please, do not ignore this message and help me, if you have any Idea
I have Sun Java System Application Server 8.1 installed on my computer, I installed also MySQL Connector/J to access MySql Databases through JDBC
But now when I try to create new connection pool, an error comes:
Following parameter were used:
Name: MYSQL1
Resource Type: javax.sql.XADataSource
Database Vendor: mysql
Datasource Classname: com.mysql.jdbc.Driver
serverName 192.168.0.152
port 3306
networkProtocol
user testuser
password ***
databaseName test
datasourceName
After saving and then klicking on Ping button, following error comes: "An error has occurred.
Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: com.mysql.jdbc.Driver"
I checked the logs of MySql, there was no attempt to access given Database or MYSQL-server at all
What Am I doing wrong? How can I create MySql connection under Sun Java System Application Server 8.1?
Any help will be appreciated

The driver is in right place
Originally I placed him in wrong directory and got an error, indicationg, that Driver class is not found, but then I corrected it, The problem is in connection to database - it doesn't work.
I tired to load the same driver into Netbeans and could easyli create a connection to database, but I get it not working ander Sun Application server

Weblogic 9.2 - Problem with Connection Pool not releasing resources

We have a third party application that is running Weblogic 9.2 and has a connection pool to a SQL 2005 db for queries within it's batch process. What I have noticed is that it does not seem to be releasing SQL cpu back after the batch and this is causing issues with processes for other dB's within the instance. Has anyone encountered this issue and if so what is the solution (short of isolating it within it's own instance). Can the connection be reset to release resources?

Yes it is a weblogic connection pool. What I mean is that when a batch run I can see the CPU for the SQL process associated with the connection increase but when the batch is completed the CPU remains high when I would expect it to move back down to an 'idle' level as after that as all it would be doing is the occasional "select 1' ping to keep the connection active.
What i do see is that the cpu in activity monitor shows high cpu and it never goes down unless the connection is killed and re-established. As this is a shared instance other apps are complaining of slow running procs.

Deploying BC4J apps to different platforms/databases

Hi all,
Maybe I've missed something very basic... This seems like it should be a breeze to set up, but after a decent amount of searching the help docs and the forums, I haven't found a good way to specify different database settings for different deployment platforms (e.g. development, QA, production, etc). All I really want to do is point the application to a different database for each different deployment platform.
It seems like the Deployment Descriptor might be a prime place for this stuff, but I don't see anything like that in the deployment settings.
I've also successfully messed around with different configurations on a per-app-module basis (e.g. creating configs called "DEV", "QA", etc with different connection strings)... This works, but it's kind of a hack if you use a lot of different app modules. Managing (in my case) six different deployment platforms for each app module can get tedious.
I can see something in the Configuration properties called "Deployment Platform", but this field is read-only and I can't figure out how to get the app module to point to different DBs based on this property... I also can't figure out how to add any other deployment platforms -- I always just see "LOCAL"...
Any help with this would be greatly appreciated. At this point my best option is to create six different configurations in each app module, and call them something like MyBizModule-DEV, MyBizModule-QA, etc... Then I specify which platform to use in a properties file, e.g. "DEV", and when I create an app module, I just append that platform keyword to the app module name to get the configuration name... But I know there has to be a more elegant way of doing this.
Thanks,
Jeff

Jeff,
It seems you are confusing the deloyment platform to the database server being used. The deployment platform property in the configuration is used to determine how the appmodule is deployed --locally, as an ejb session bean or as a corba server. The database connection to be used is referred to by <JDBCName> or the <JDBCDataSource> property. JDBCName refers to the named database connection defined in the ide. <JDBCDataSource> refers the jdbc 2.0 datasource defined in the appserver. Both the mechanisms provide the abstraction for changing the target database url.
Instead of creating different configurations you can change the connection definition for different environments.
Hope this helps
Dhiraj

Can I use same connection pool on multiple web app?

Hi,
I have several web applications on my domain, and they all share the same database.
I am using TOMCAT 4, and I've wrote my own pool, but the problem is that there are also some other domains on the server, so I can't put my connection pool in the tomcat's share or common directory.
Right now, I am thinking of switching to use tomcat's datasource implementation. How do I configure the datasource so that all my web apps will use the same connection pool?
Thanks!

There's no actual webapp configuration when using Datasources... your Java code accesses the Datasource through JNDI:
     Connection con = null;
     String dataSourceName = "someDataSource"
     try {
          Hashtable parms = new Hashtable();
          parms.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.ejs.ns.jndi.CNInitialContextFactory");
          Context ctx = new InitialContext(parms);
          javax.sql.DataSource ds = (javax.sql.DataSource)ctx.lookup(dataSourceName);
          con = ds.getConnection();
     } catch (NamingException e) {
          throw new SQLException("NamingException - " + e.toString());
     }If you want, you can keep the DataSource name in the application's ServletContext, so that you don't hard code it into your Java code.

Images are not shown after deploying in apps

After deploying my application in apps i have put all my images in media folder even then the images are not displaying, can any tell me what is the reason for this, but when i have deployed before it was working fine...

when the page is displayed without the image, right click on the image place holder and click on properties. Under General tab,
address will show you the place/url page is looking for the image. Make sure you have put the image on that path and the name of image mathes the case as well.
--Tanveer

REgarding problem in Connection pooling of weblogic server

Hi ,
I have installed weblogic server 9 and trying to connection pooling in datasource , i am getting error to unable to load driver class: oracle.jdbc.DataSource
see below error log
####<Oct 29, 2008 4:55:34 PM IST> <Error> <Console> <cdhulipati> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1225279534589> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException:
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:268)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.RedeployOperation.createAndPrepareContainer(RedeployOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:118)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:215)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.prepare(DeploymentReceiverCallbackDeliverer.java:40)
     at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.callDeploymentReceivers(AwaitingContextUpdateCompletion.java:156)
     at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.handleContextUpdateSuccess(AwaitingContextUpdateCompletion.java:66)
     at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.contextUpdated(AwaitingContextUpdateCompletion.java:32)
     at weblogic.deploy.service.internal.targetserver.TargetDeploymentService.notifyContextUpdated(TargetDeploymentService.java:225)
     at weblogic.deploy.service.internal.DeploymentService$1.run(DeploymentService.java:189)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: weblogic.common.resourcepool.ResourceSystemException: Cannot load driver class: oracle.jdbc.DataSource      at weblogic.jdbc.common.internal.JDBCUtil.parseException(JDBCUtil.java:292)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.loadDriver(ConnectionEnvFactory.java:77)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.<init>(ConnectionEnvFactory.java:133)
     at weblogic.jdbc.common.internal.ConnectionPool.initPooledResourceFactory(ConnectionPool.java:687)
     at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:192)
     at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1177)
     at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:184)
     at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:177)
     at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:370)
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:243)
>
Please help me out

chaitudnvr wrote:
Please help me outYou would probably get better help in a forum where your question was on-topic. This forum is about XML and Java and your question isn't about either of them.

REgarding problem in Connection pooling

Hi ,
I have installed weblogic server 9 and trying to connection pooling in datasource , i am getting error to unable to load driver class: oracle.jdbc.DataSource
see below error log
####<Oct 29, 2008 4:55:34 PM IST> <Error> <Console> <cdhulipati> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1225279534589> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException:
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:268)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.RedeployOperation.createAndPrepareContainer(RedeployOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:118)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:215)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.prepare(DeploymentReceiverCallbackDeliverer.java:40)
     at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.callDeploymentReceivers(AwaitingContextUpdateCompletion.java:156)
     at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.handleContextUpdateSuccess(AwaitingContextUpdateCompletion.java:66)
     at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.contextUpdated(AwaitingContextUpdateCompletion.java:32)
     at weblogic.deploy.service.internal.targetserver.TargetDeploymentService.notifyContextUpdated(TargetDeploymentService.java:225)
     at weblogic.deploy.service.internal.DeploymentService$1.run(DeploymentService.java:189)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: weblogic.common.resourcepool.ResourceSystemException: Cannot load driver class: oracle.jdbc.DataSource      at weblogic.jdbc.common.internal.JDBCUtil.parseException(JDBCUtil.java:292)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.loadDriver(ConnectionEnvFactory.java:77)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.<init>(ConnectionEnvFactory.java:133)
     at weblogic.jdbc.common.internal.ConnectionPool.initPooledResourceFactory(ConnectionPool.java:687)
     at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:192)
     at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1177)
     at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:184)
     at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:177)
     at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:370)
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:243)
>
Please help me out

I think you have your driver slightly incorrect.
Try: oracle.jdbc.OracleDriver
instead of oracle.jdbc.DataSource
Cheers,
-Adrian

Reg:Problem with Connection Pool

Hi all,
I copied DAc analysis RPD from the link (http://www.rittmanmead.com/2009/01/analyzing-bi-apps-etl-runs-using-obiee-and-the-dac-repository/ ) into my existing RPD by changing the connection pool of DAC Analysis RPD to the connection pool settings of my Existing RPD.
W_ETL_DEFN,W_ETL_DEFN_RUN,W_ETL_FOLDER,W_ETL_GROUP_STEP,W_ETL_PHASE,W_ETL_RUN_STEP,W_ETL_STEP,S_ETL_DAY
All these tables are coming from a schema BISchema.. Except S_ETL_DAY table. it is coming from the Usage Tracking tables and all the tables in the Usage tracking are coming from OBIAPP Schema.
In order to know about the ETL Runs Over time we need S_ETL_Day table..
So how do I import S_ETL_Day table to DAC folder..where the Schema of both DAC tables and Usage tracking table is Different.
Need Help....

that you can do but there is a way to use that S_ETL_DAY table in do a double mapping in the BMM layer so that you can those fields in that particular table...

Problems with connection pool

hi,
I have problems with Weblogic 5.1 connection pool. Normally it works
fine, but
under heavy load the connection pool doesn't work at all: it
negotiates a new connection every time.
Has anyone else had problems like this?
regards, EK

Mitesh Patel wrote:
What is your max capacity of the pool? Generally, max capacity value of
the pool should be no. of concurrent users connecting to database at
peak load.Hi Eino. Actually, I'll disagree temporarily with Mitesh ;-)
If your application is designed so that all JDBC work is done
during a single client-server invoke, such as in stateless session
beans, or servlets etc, you should only need as many connections
in the pool as your server has execute-threads. This is because
each thread will be handling one client at a time, and as long as
the code gets a pool connection, uses it, and closes it during the
one invocation, the closed connection will be there for the next.
one.
Let me see your pool definition. The only issue that may
cause occasional problems like you see, is if pool refresh is
running. Pool refresh will temporarily reserve all the currently-
unused pool conenctions to test them, and during this time, any
incoming application demand will cause the pool to make new connections
(or throw an exception!) to meet demand. If you have testConnsOnReserve
set to true, this is all the pool checking you need IMO. I would set
the refresh minute parameter to 99999999 to effectively turn off
refresh. I'm betting that will solve your issue. Let me know...
Joe
>
>
Mitesh
Eino Komsi wrote:
hi,
I have problems with Weblogic 5.1 connection pool. Normally it works
fine, but
under heavy load the connection pool doesn't work at all: it
negotiates a new connection every time.
Has anyone else had problems like this?
regards, EK

Problem in Connection pooling after deploying BC4J App Module as EJB

Similar Messages

Maybe you are looking for