SRDemo with application pooling disabled

Question

Hi Steve,
We are building an ADF BC/JSF application that can potentially have a high
number of visitors simultaneously.
So i took your advice on your blog
(http://radio.weblogs.com/0118231/2005/05/09.html) and tested our search
page with application pooling disabled. Unfortunately some functions of the
search page stopped working.
Then I tested the SRDemo application (ADF BC/JSF version) with application
pooling disabled. When application pooling is disabled the SRDemo
application does not work properly either.
So I am wondering...Is there a sample application that works with
application pooling disabled? Among others, I am particularly interested how
the following scenario would work:
1. The user enters a search criteria hits the search button and retrieves a
list of rows in a JSF table.
2. The user clicks one row in the table and he is navigated to a page where
he can view the details of the row he clicked
3. He hits the browsers back button
4. He clicks another row in the table.
5. He is navigated to a page where he can view the details of the last row i
clicked
6. He goes to step 3 and repeats the process as many times as he desires.
This simple scenario works in SRDemo in one context when application pooling
is enabled. It gives a row currency error in another at step 4. When
application pooling is disabled the application doesn't show any errors but
behaves incorrectly.
I would appreciate your insight on how to make this scenario work.
Thank you
Yalim

Answer 1

I am testing with 10.1.3.0. The change you suggested did not make any difference.The two scenarios I described in my previous post still do not behave correctly.
However I found out that the advanced search tab functions properly even without application pooling once the token validation is disabled. By that I mean that in the advanced search tab I can go through the 6 steps I described in my first post without getting any errors.
I also did some testing in 10.1.3.1. I downloaded SRDemo for ADF BC from the check for updates option in the menu. Then I ran the application with application pooling disabled. The 2 scenarios in my previous post did not behave correctly in 10.1.3.1 either. I must mention though; the behavior of the application was different.
On the other hand the advanced search tab seemed to be functioning properly.
It seems like when application module pooling is disabled, navigating to the details of a record in My Service Requests tab does not function properly whereas the same functionality works just fine in Advanced Search tab under the same condition.