Performance - Application Module instantiation

I am experiencing poor performance the first time a user instantiates a application module which is taking roughly 8 seconds down to 1 second for subsequent attempts. Pooling is enabled and we are using JDev 10.1.2 build 1811. I was wondering if someone could tell me how I could instantiate the application module pool so the users avoid this initial delay by loading these behind the scenes when they initially log onto the main application.

It's hard to say in general if you'd have a "performance issue", but what I can say is moving it to be its own top-level application module would mean:
-> An extra/different JDBC connection instance
-> An extra/different entity cache
So that might translate into slower performance, but it's always worth doing some benchmarking of exactly what you have in mind to see if for your circumstance the use would incur unwanted overhead or be negligible in the big picture.

Similar Messages

How application module helps for performance improve

Hi Everyone,
I have a sample web-application in which I am connecting with single AM instance (AM for database view object), retrieving some information and then close the connection. I am doing this as,
// making AM instance
<application module instance> = Configuration.createRootApplicationModule(<AM name>, config);
// performing operations
<operation result> = <application module instance>.<access VO with any operation>();
System.out.println("Get result here");
// disconnecting AM instance
<application module instance>.getDBTransaction().disconnect();
Configuration.releaseRootApplicationModule(<application module instance>, true);
These are the activities which are performed by a single user. Now, I am doing stress test on same activities. I am testing the same code with 300 concurrent users (using JMeter with JSP URL). These are working fine. Also I checked multiple times, it always working fine.
Now, I need to do something through which I can improve the performance. I know, I can use AM pool configurations to make this more effective. I have gone through the Oracle documents and checked the same test case with default or recommended pool configurations and I found similar kind of results (there is not much difference).
On other hand, I tried with 'releaseRootApplicationModule' method with false parameter and found better results in default as well as recommended pool configurations.
My question is, is the change of pool configurations recommended by Oracle really work? or do I need to concentrate more on coding part with default pool configurations?
Here, I would like to know, what are the best practice (in code as well as pool configurations), I need to follow if I really want to improve the performance in real scenarios (when our application will access with large no. of concurrent users).
I really look forward some help from experts. I have given a lot of time on this to know how really we can make our application more effective in terms of performance.
I really appreciate for your reply.
Regards,
Dilip Gupta.

>
We added the createRootApplicationModule() API (in the oracle.jbo.client.Configuration class) to simplify acquiring an application module from the pool for brief programmatic manipulation before it is released back to the AM pool.
Steve Muench.
>
check [url http://radio-weblogs.com/0118231/2009/08/20.html#a959]Check Your App for Misuse of Configuration.createRootApplicationModule()
Edited by: Mohammad Jabr on May 10, 2012 7:14 AM

Application Module Nesting Performance

I have multiple application modules and it is currently nested to one main application module.Due to the complexity of my logic, I would like to refactor it further but I cannot move it outside the root application module because the instance of the other services is invoked by
rootAppModule.findApplicationModule("childAppModule"),
If I move it outside the root application module, do we have a performance issue by using createApplicationModule whenever I access the application module?

It's hard to say in general if you'd have a "performance issue", but what I can say is moving it to be its own top-level application module would mean:
-> An extra/different JDBC connection instance
-> An extra/different entity cache
So that might translate into slower performance, but it's always worth doing some benchmarking of exactly what you have in mind to see if for your circumstance the use would incur unwanted overhead or be negligible in the big picture.

Nested Application Module Performance

What are the implications of nesting application modules? I am nesting them in such a way that they are defined at design-time and used by calling findApplicationModule(String) on the root ApplicationModule. Could there be any significant overhead accessing one nested app mod in this way as opposed to going to the desired app mod directly? Or is there anything else to watch out for with this type of design? I haven't had any trouble so far but my project is not too large yet.

For example, I have three ApplicationModule objects.
RootModule, Module1, and Module2. By nesting Module1
and Module2 under RootModule, I can use either once I
have an instance of RootModule by calling
findApplicationModule(String name). This is useful
when I want to do things inside both Module1 and
Module2 and still use the same connection and
transaction context.
If I only want something out of Module1 during a
request, would it be advantageous to ONLY create
Module1 directly and bypass my RootModule?
Meaning this:mod1Am =
Configuration.createRootApplicationModule("Module1","M
dule1Config");
mod1Am.myCustomOperation();As opposed to
this:rootAm =
Configuration.createRootApplicationModule("RootModule"
"RootConfig");
mod1Am = rootAm.findApplicationModule("Module1");
mod1Am.myCustomOperation();
Nick:
There are advantages to creating Module1 directly. It would be that you don't create unnecessary objects (in your case, you would avoid unnecessary creation of Module2").
However, I would make the following side comment: from your message, it sounds like you would create an AM for every request and remove it at the end. Did you consider using AppModule pool? AM pool would be better than create-remove because AM pool can keep around a number of root AM instances and manage resources for you. This way, you don't have to create any AM for each request. AM pool is also able to support stateful operations with excellent scalability.
Thanks.
Sung

Is it proper for an application module has 300 views in the data model?

Based on my understanding, all view object instances are initialized at the same time as the application module.
It follows that when an application module is associated with a user session, the queries of each view object in the data model are executed.
ie. if the data model has 325 view object instances, 325 queries will be executed.
This doesn't seem efficient:
1. As each user session only need to access a subset of the view objects (for examples 35 views), the rest of view objects need not be instantiated for that session.
2. Performance may be slow on executing all 325 queries at one time, even worse when some queries are complex queries.
Am I correct on this?
In this case, will it be better to instantiate the view objects using the view object definition at runtime instead of adding all of them to the application module at design time?

No, that's not the default behaviour.
Assuming you're talking JDev 11, the AM on it's General tab as a Tuning option where you can set the loading of the VOs to Lazy or Non-Lazy, Lazy is the default. In turn each VO on their General tab also has a Tuning option of similar nature.
Online documentation says:
Lazy LoadingSelect to choose lazy loading. In this case, the application module instance is created without any of its components. Your view object and nested application module instances will not load until the first time they are used. For example, when lazy loading is enabled, a view object is instantiated only when the application accesses it. This will make start-up time faster.
Non-lazy Loading
Select to choose non-lazy loading. Your view object and nested application module instances will load when the application starts up. For example, suppose the application module you are editing defines three view objects and two nested application modules (which appear in the Application Module Instance section of the Data Model page over the application module overview editor). When lazy loading is disabled, the application module instance is created together with all three view objects and both nested application modules.>
So in essence as you describe for each session, if we're using the Lazy setting, even though you have 325 VOs within an AM, if the user within the session only visits 35 queries, only 35 queries should fire.
Does this help?
CM.

How do I call an Application Module method from a EntityImpl class?

Guys and Gals,
Using Studio Edition Version 11.1.1.3.0.
I've got a price update form, that when submitted, takes the part numbers and prices in the form and updates the corresponding Parts' price in the Parts table. Anytime this Parts view object's ReplacementPrice attribute is changed, an application module method needs to be called which updates a whole slew of related view objects. I know you can modify view objects via associations (How do I call an Application Module method from a ViewObjectImpl class? but that's not what I'm trying to do. These AppModuleImpl methods are the hub for all price updates, as many different operations may affect related pricing (base price lists, price buckets, etc) and hence, call the updatePartPricing(key) method.
For some reason, the below code does not call / run / activate the application module's method. The AppModuleDataControl exists and recordPartHistory(key) is registered and public. At runtime, the am.<method> code is simply ignored, and as a weird side-effect, I cannot navigate out of my current page flow.
public void setReplacementPrice(Number value)
    setAttributeInternal(REPLACEMENTPRICE, value);
    AppModuleImpl am = (AppModuleImpl)this.getDBTransaction().findApplicationModule("AppModuleDataControl");
    Key key = new Key(new Object[]
        { getPartNumber() });
    am.recordPartHistory(key); // AppModuleImpl method which records pricing history
    am.updatePartPricing(key); // AppModuleImpl method which updates a whole slew of related pricing tables
}Any ideas?

Thanks Timo.
Turns out the code provided was correct, but the AppModuleImpl method being called was not. A dependent ViewObject wasn't returning the row I was expecting. I then tried to perform some operations on that row, which in turn ... just stopped everything, but didn't give me an error.
It was the lack of the error that threw me off. I had never messed with calling an AppModuleImpl method from the EntityImpl so I assumed that's what was messing up.
You are correct. It is available from the ViewRow, but I thought it better to put it in the EntityImpl. This method will be called every time the replacement cost is modified. If I didn't put it in the EntityImpl, I'd have to remember to call it every time a replacement cost changed.

Intermittent error in production server JBO-25200: Application module is not connected to a database.

We've set 60 min as session timeout and AM pool parameters also high (<AM-Pooling jbo.ampool.maxinactiveage="1200000" jbo.ampool.initpoolsize="25" jbo.ampool.maxpoolsize="1000" jbo.recyclethreshold="50" jbo.ampool.maxavailablesize="50" jbo.ampool.minavailablesize="25"/>) in our application due to requirements. We are using jdev 11.1.1.7.0
Intermittently The page is getting refreshed and unsaved data is lost when user leaves a page for 5 or 10 min and on return back to application and performing operations back. There is not much load also on the server. When we analyze the logs the below exception is thrown on the logs.
Exception Class: oracle.jbo.NotConnectedException
Message: JBO-25200: Application module is not connected to a database.
Agent: APP_BSA_BPA[mnatest_soa2]@egw-bpm2-mnat.wfs.com:5508
API: Exception
Thread Name: [ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)' <562720362>
Exception StackTrace
Method Class Line        File Name
handleRollback oracle.jbo.server.DefaultTxnHandlerImpl 145         <unknown>
doRollback oracle.jbo.server.DBTransactionImpl 5174       <unknown>
rollback oracle.jbo.server.DBTransactionImpl 2544       <unknown>
resetState oracle.jbo.server.ApplicationModuleImpl 4860       <unknown>
disconnect oracle.jbo.common.ampool.DefaultConnectionStrategy 343         <unknown>
doPoolDisconnect oracle.jbo.server.ApplicationPoolMessageHandler 592         <unknown>
doPoolMessage oracle.jbo.server.ApplicationPoolMessageHandler 430         <unknown>
doPoolMessage oracle.jbo.server.ApplicationModuleImpl 9316       <unknown>
sendPoolMessage oracle.jbo.common.ampool.ApplicationPoolImpl 4530       <unknown>
prepareApplicationModule oracle.jbo.common.ampool.ApplicationPoolImpl 2460       <unknown>
doCheckout oracle.jbo.common.ampool.ApplicationPoolImpl 2270       <unknown>
useApplicationModule oracle.jbo.common.ampool.ApplicationPoolImpl 3169       <unknown>
useApplicationModule oracle.jbo.common.ampool.SessionCookieImpl 592         <unknown>
useApplicationModule oracle.jbo.http.HttpSessionCookieImpl 234         <unknown>
useApplicationModule oracle.jbo.common.ampool.SessionCookieImpl 525         <unknown>
useApplicationModule oracle.jbo.common.ampool.SessionCookieImpl 520         <unknown>
initializeApplicationModule oracle.adf.model.bc4j.DCJboDataControl 523         <unknown>
getApplicationModule oracle.adf.model.bc4j.DCJboDataControl 869         <unknown>
internalGetBeanDataControl oracle.adf.model.bc4j.DCJboDataControl 969         <unknown>
findOrCreateMethodRowSetIterator oracle.adf.model.bc4j.DCJboDataControl 1236       <unknown>
initSourceRSI oracle.jbo.uicli.binding.JUMethodIteratorDef$JUMethodIteratorBinding 698         <unknown>
callInitSourceRSI oracle.adf.model.binding.DCIteratorBinding 1679       <unknown>
internalGetRowSetIterator oracle.adf.model.binding.DCIteratorBinding 1652       <unknown>
refresh oracle.adf.model.binding.DCIteratorBinding 4506       <unknown>
refreshIfNeeded oracle.adf.model.binding.DCExecutableBinding 341         <unknown>
getRowSetIterator oracle.adf.model.binding.DCIteratorBinding 1612       <unknown>
getViewObject oracle.jbo.uicli.binding.JUMethodIteratorDef$JUMethodIteratorBinding 473         <unknown>
_loadCriterionList oracle.adfinternal.view.faces.model.binding.FacesCtrlSearchBinding$AdfConjunctionCriterion 3504 <unknown>
getCriterionList oracle.adfinternal.view.faces.model.binding.FacesCtrlSearchBinding$AdfConjunctionCriterion 3417 <unknown>
invoke sun.reflect.GeneratedMethodAccessor4821 - <unknown>
invoke sun.reflect.DelegatingMethodAccessorImpl       25 <unknown>
invoke java.lang.reflect.Method 597         <unknown>
Any idea why this exception thrown ? Is this because of weblogic server connections cleanup or something to do with connections? As per my understanding , JDBC connection will not be released when AM is active/managed mode. Oracle Doc says
" That application module instance holds onto the JDBC connection object that it acquired from the pool until the application module instance is removed from the application module pool."

jbo.ampool.maxinactiveage is set to 20 min which means that If AM in the pool is inactive for 20 min then clean this AM in the next cycle (still that is not our case). We also set jbo.recyclethreshold="50" means 50 AMs can exists in the pool with managed-state. We set these because of performance reasons. As per my understanding, AM instance will be deleted (????) but in any action on the UI will pick up another instance of the AM because datacontrolframe is still valid in the session. Do we have any best practice like jbo.ampool.maxinactiveage should be equal to session time out?. The error seems AM lost the underlying JDBC connection and somehow application is using that stale AM ?. what will be possible reason?.

Best Practice - Bounded Task Flows, Regions and Nested Application Modules

Using JDev 11.1.1.3; understand that it's generally considered good practice to just have 1 root application module servicing model content / services for each page. In our application, we've used a number of bounded task flows and page fragments deployed as af:region's into pages as either a) views targeted in page-flow navigation, b) tab panel content inside a regular jspx, or c) af:popup / af:dialog content. As it stands, we've not engaged nesting of the application modules for this embedded region content, so these regions are no doubt instantiating new AM's if/when invoked. Should the AM's servicing these embedded regions be deployed nested within the root AM's, and then if so, does this change the way that the jsff / fragment content is actually developed (currently as per any other jspx using the DataControl pallete). Or are the best-practice directives talking about a page as being the design-time / declarative composition of content rather than the run-time aggregation of page + fragments ... in which case the fact that our embedded fragments are not using nested AM's is unlikely to concern.
Thanks,

Probably a better question for the ADF EMG: http://groups.google.com/group/adf-methodology?hl=en
CM.

Best practice for application module for scalability

if i compare application module with forms 6i runtime session.(correct me if i wrong)
In forms 6i, we create for single form for purchase entry. in which we select table like po , po_item, item_master, customer master
also single form for sales entry. in which we select table like sales , sales_item, item_master, customer master, po , po_item
So my question is. in jdeveloper , we planning to make separate jsp page and applicaiton module for purchase entry,
separare jsp page and application module for sales.
is it ok.
or
what is the best practice in this senario.?? ( or in scalability senario)
if i made one single application module for whole application (let say 300 entity's(tables)) will performance of my app server degrade.

You might want to read the chapter about AM Granularity in the ADF Developer Guide:
http://download.oracle.com/docs/html/B25947_01/bcservices009.htm#sm0229

PL/SQL from Application Module instead of Using VO/EO - Violating Standard?

Hi,
I have seen product code which Use PL/SQL APIs for committing data (Creation of Records in Table) from Application Module. There is no BC4J (VO/EO) used in this data route.
Is there any coding standard (document) which says such cases are against Standards.I know there is one Standard saying PL/SQL Based VO is dicouraged in Oracle Apps.
Thanks
Joseph

Vikram,
Performance depends on the way you are going to make use of pl/sql code. Suppose if you are using pl/sql just for final insert/update with other validations bound to it through a single call, that's fine. But in case you have other multiple calls to pl/sql blocks also for fetching data for display purpose, that's where standard VO's will be more efficient reducing the number of trip for pl/sql calls. So use it only when it is the last way and you need to handle multiple validations with complex data structure.
As for locking, yes, you might have to take care of locking handling scenario if such a situation happens. But again it depends on what's your business logic and how is your data being processed.
--Shiv

Important conceptual question about Application Module, Maximum Pool Size

Hello everyone,
We have a critical question about the Application Module default settings (taking the DB connections from a DataSource)
I know that on the Web it is generally suggested that each request must end with either a commit or rollback when executing PL/SQL blocks "directly" on the DB without the framework BC/ViewObject/Entity service intervention.
Now, for some reasons, we started to develop our applications with thinking that each Web Session would reference exactly one DB session (opened by any instance taken from the AM pool) for the whole duration of the session, so that the changes made by each Web session to its DB session would never interfere with the changes made by "other" Web Sessions to "other" DB sessions .
In other words, because of that convincement we often implemented sort of "transactions" that open and close (with either commit or rollback) each DB session not in/after a single HTTP request, but during many HTTP Requests.
As a concrete example think of this scenario:
1. the user presses the "Insert" button. An HTTP request is fired. The action listener is executed and ends up with inserting rows in a table via a PL SQL block (not via the ViewObjects API).
2. no commit or rollback after the above PL/SQL block is done yet.
3. finally the user presses a "Commit" or "Rollback" button, firing the call to the appropriate AM methos.
Those three requests consist of what I called "transaction".
From the documentation it's clear that there is no guarantee that the couple AM istance + DB session is the same during all the requests.
This means that, during step 2, it's possible that another user might reference the same "pending" AM/DbSession for his needs and "steal" somehow the work done via PL/SQL after step 1. (This happens because sessions taken by the pool are always rolled back by default.)
Now my question is:
Suppose we set the "Maximum Pool Size" parameter to very a great number (always inferior to the maximum number of concurrent users):
Is there any guarantee that all the requests will be isolated in that case?
I hope the problem is clear.
Let me know if you want more details.

Thanks for the answers.
If I am right, from all your answers about resource avaiability, this means that even supposing the framework is able to always give us the same AM instance back from the AM pool (by following the session-affinity criterias), there is, however, no "connection affinity" with the connections from the DataSource. This means that the "same AM instance" might take the "a new DB connection", if necessary, from the connection pool of the DataSource. If that happens, that could give us the same problems as taking "a new AM instance" (that is, not following session-affinity) from the beginning, since each time an a new connection is taken (either via a new AM instance or via the same AM instance plus a new DB connection), the corresponding DB session is rolle back by default, clearing all the pending transactions we might have performed before with direct PL/SQL calls bypassing the AM services during the life cycle of our application, so that the new HTTP request will have a clean DB session to start to work with.

Guidelines for setting Application Module Pool Size Parameters?

Are there guidelines for setting the application module pool size parameters, such as initial pool size, maximum pool size, etc., based on the expected number of users or other factors? I've read the developer guide sections (ch 28-29), but still don't have a good feel for how to correctly set the optimal values for the pool configuration parameters? Even more importanty, how do I monitor the pool's efficiency during runtime to determine if the pooling parameters are configured correctly?
This will be critical to performance and scalability, so I'm looking for a way to get some visibility into how the pooling is working during production operation to assess whether there are bottlenecks/constraints/ineffeciencies?
Note I am using Tomcat as the java runtime container; ADF BC / JSF jdev 10.1.3.1
Thanks in advance and Merry Christmas!

KUBA - were you able to resolve these issues and if so are there any lessons learned you can share?
I'm hoping someone from the ADF team can answer our original question including guidelines for setting pool parameters and how to monitor the pool's performance while running in production.
thanks

ADF & Spring: Application Module

Hi!
Im testing a mix of ADF and Spring.
I create an Bean in the Spring Context that is an ApplicationModule
<bean id="myAM" class="oracle.jbo.client.Configuration" factory-method="createRootApplicationModule">
<constructor-arg><value>mypkg.myAM</value></constructor-arg>
<constructor-arg><value>MyAMLocal</value></constructor-arg>
</bean>
Testing the application it works fine.
But I want more and i wish the ADF takes this instance of MyApp and avoid a new instantiation of it. (Now i have 2 instances of MyApp, one created by Spring and another created by ADF)
Theres some way to say ADF to take an existing instance to put it in the session or somethig?
Thank you!!

OK the question is Why??
Seriously though - you can create a data control that exposes Spring artifacts through the Data Control palette which would seem to be the more normal way around. Do you need the Application Module to inject it into some other Spring Artifact?

Obtaining DataSource from Application Module

How may i obtain DataSource from pool managed by Application Module? I want some of my db-related operation performed by Spring's JdbcOperations class ( http://www.springframework.org/docs/api/org/springframework/jdbc/core/JdbcOperations.html ) and i want have only one connection pool in my application.
Thanks,
Kind regards,
Marcin Zduniak / http://J2ME.pl

Refer
http://www.oracle.com/technology/products/jdev/howtos/10g/usingdatasources/using_datasources.html

JAAS Authorization - Application Module

I created a project based on the BC4J technology. The application module is configured for using the security : jbo.security.enforce=Must. This application module is also configured to deploy the user/password.
When I used this application through a web application, I don't meet any problem.
If I create a POJO class in the same project as BC4J in which I instantiate an instance in the application module pool, I receive the following message :
oracle.jbo.JboException: JBO-29000: Unexpected exception caught: oracle.jbo.JboException, msg=JBO-33021: Failed authenticate user null.
The java class in charge of instantiating the application module pool and get an instance of it works without any problem as soon as the security is not implemented.
Hereafter you can find the method used :
public ApplicationModule getApplicationModule()
try{
PoolMgr poolMgr = PoolMgr.getInstance();
this.lg_ApplPool = poolMgr.findPool( this.lg_configPackage + "." + this.lg_configName, // name of the pool
this.lg_configPackage, // name of the package
this.lg_configName, // name of the configuration
null);
// SessionCookie Creation
String timeStamp = (new java.util.Date()).toString();
// for web application, replace timeStamp by ip address of the client
this.lg_Cookie = lg_ApplPool.createSessionCookie(this.lg_applicationId,timeStamp,null);
CordaEnvInfoProvider lEnvInfoProvider = new CordaEnvInfoProvider ("xxx","xxx");
// this.lg_Cookie = lg_ApplPool.createSessionCookie(this.lg_applicationId,timeStamp,null);
this.lg_Cookie.setEnvInfoProvider(lEnvInfoProvider);
ApplicationModule lAM = this.lg_Cookie.useApplicationModule();
return lAM;
catch(Exception e)
System.out.println("_CrdAppModulePoolMgr - exception : " + e.getMessage());
e.printStackTrace();
return null;
After Having search quite a long time to find a solution, I have no more idea. The only thing I see now is to forget about Jaas if the application module has not to be used by a Java client not being a JClient (Swing) or a Web application.
Could you let me know if
1. jaas works with java client not being Swing or web application
2. if so, could you give me more information about how to work with BC4J application module and security enforce to Must ?
N.B.
POJO Client :
public class TestAppModulePoolMgr
private ApplicationModule lg_Am = null;
private CrdAppModulePoolMgr lgCrdAppModulePoolMgr = null;
private ApplicationPool lg_ApplPool = null;
private SessionCookie lg_Cookie = null;
public TestAppModulePoolMgr()
this.lg_CrdAppModulePoolMgr = _CrdAppModulePoolMgr.getCrdAppModulePoolMgr();
this.lg_CrdAppModulePoolMgr.setApplicationId("CrdGenerationAppModuleId");
this.lg_CrdAppModulePoolMgr.setConfigName("_CrdGenerationAppModuleLocal");
this.lg_CrdAppModulePoolMgr.setConfigPackage("CORDA_BSV");
this.lg_Am = lg_CrdAppModulePoolMgr.getApplicationModule();
this.lg_ApplPool = lg_CrdAppModulePoolMgr.getApplicationPool();
this.lg_Cookie = lg_CrdAppModulePoolMgr.getApplicationSessionCookie();
* @param args
public static void main(String[] args)
TestAppModulePoolMgr testAppModulePoolMgr = new TestAppModulePoolMgr();
}

Thank you.
I use SSO authentication to test my application so have no users defined.
Can I use the test-all user? If so, what is the password?

Performance - Application Module instantiation

Similar Messages

Maybe you are looking for