Hello, in this video I will explain what is the best revision mode, this mode your diff application can enter in this mode into situation. First one, if you set a session timeout is more than one hour, because by default, after one hour, the application will be entered into this the best efficient mode. So, you should sit session will be for one hour so that you will prevent your ADF application to be entered in the passivation mode. This is one reason can make it if application a be in the best revision mode. The second reason will be the overloading. If you have configured your application bullying size is less than what is the concurrent user and use the application for example, you have 50 user using your if application but you didn't configure when you're a application bullying.

Some user will be entered in the best division What best efficient mode it means the underlying resources like the memory, or the data source in the WebLogic. And all resources behind your application will leave you and maybe it will be assigned to any other user. So your session you read if application session will be active, but in the underlying data sources and object and own memory object can be the bullying and everything can leave you and go to any other user. When this habit, it can be habit if you make decision more than one hour, or you have a lot of user overloading in your application. And you didn't configure your application pooling to accept all this number of users. Your ADF application will be in unexpected behavior.

If it is inserted to the best division would he is a rule see some arrows coming was always From where it is, you know coming here you can see some changes and this change didn't save. So, he will see unexpected behavior will happen. If you want to test your a EDF application in the best revision mode to see how your PDF application will looks like if it is entered to the basic vision mode, you can simply open your application module in the configuration This is enabled in the application module obligation would you pull the UCC section on check Can you can you can uncheck this same you can do it in the shear on check this and run your application. Once you're on the solidification, this application will be run in the best division mode to see what this user will see if he was on The best efficient mode.

If you want to return the back your application to use a normal activation mode, you can select this and is a local you can select Enable application while you're pulling. This is how you can if you want to see how your application will work if some user be in the best efficient mode, what is the application behavior will look like on the chicks This enabled application would you blink in that case, you can run the application and you will run your application in a best efficient I talked about this sufficient mood in my blog a couple of years ago, here is I talk about this application bullying. As you can see here, the be sufficient mood officer be sufficient mood was efficient mood is a service efficient mood will manage system resource. So if you leave your application idea for a longer time, that is Like database pooling or memory will be gone to any other active application in that case would be in the best submission.

Okay wins application can interpret the best efficient mode. So by default, if you leave the application for one hour application will enter in server submission mode. So you be sure that your session should be less than one hour. But in case if you want the decision to be more than one hour, there are some changes you have to do in the application module. And second decision can happen as well. If your application under heavy load, and you didn't make a configuration in the morning to accept this load.

What I have to do with the application becoming a sufficient mode you can just look at it and log in again so that it will become other new resources. How can I test my application is the best division as I told you is the Enable application module bullying you can uncheck it and run your application is a case you will run your application in best efficient mode. And you can know how it will look like okay in case if you want to make a decision more than one hour and is the same time you want your application to become in the best efficient mode, there are some changes you have to do in your application application module, you should set the time to live to be minus one and the max inactive age should be something big, large like like this non big number and you should sit as well do do connection pooling to be true and disconnect deliver to be one census for living.

In that case, you can set your because this this number will be make your reservation mode will enter after this. This is means five hours to this I think milli second or second, maybe second and it means for five hour Your application would be entered in the best efficient. So, you can go here in your application module is a poor variety here okay you can press here plus, because all this is this is live in G, but it will visit you have to press plus. So, if you want to see exactly what you should do max inactive, this is Max inactive age. This is will control the specification by default is one hour, you can set it too long. So, that will be more than one hour.

So, you can find here max in active h as you can see, this is for one hour max in active age, you can change it to or increase it to something else. And you can sit time to live to be minus one Time To Live is not no longer has value, you can set it to be minus one. Okay? You can do this here, okay? After that you can insert it here, minus one, like this. So you can see it's a variable exists.

Okay, so now you know when your application will enter the best vision mode, if you set the timeout to be more than one hour without configuring Time To Live and user would configure on max inactive, H to be big number, large, large number and you can see this to barometer as well. Okay, so anyway, I have a documentation. I will go with you now for this documentation. And I will tell you about all of this parameter in this documentation. Okay, how I can configure my application to avoid it. revision mode.

So, to avoid the best revision mode, you have to sit session timeout lose value listen what you said is the best efficient value. So, if you set the sufficient value here for two hours, so, you your session should be listen to our if you set the maximum active age for five hour, so your session should be reserved for an hour. So be sure that your session which you will sit here in XML should be less than what you configure in the inactive do in active age. This is be sure that your value you will enter here. For example, this is for five hours so you have here option to enter anything less than five hours. Okay, this is one I think so.

Hopefully this is this change will tell you how exactly you can avoid the less efficient mode negativity. I will go with you through a documentation which I wrote that what actually the configuration you can do in the application Bulik. The main ones are number of user who will use your if application. So see you next activity.