Query Region Rendering Issue between RUP4 and RUP5 Env.

Question

Dear OAF gurus
We currently face an issue with a custom built OAF query region, where the regions works perfectly well, i.e. the page renders in a timely fashion with all its fields in one Apps environment (Dev) and then “Hangs and eventually times-out” in another environment (SysTest).
Clearly this leads us to believe that there must be an issue with the environment configuration and/or patch/product levels, namely the OAF tech-stack.
The Development Env. where this is working:
===========================================
OAF Version : 11.5.10 RUP 4.
MDS Version : 9.0.5.4.89 (build 555)
UIX Version : 2.2.24
BC4J Version: 9.0.3.13.93
The System Test Env. where this is NOT working:
===========================================
OAF Version : 11.5.10 RUP 5.
MDS Version : 9.0.5.4.89 (build 555)
UIX Version : 2.2.24.1.0
BC4J Version: 9.0.3.13.97
As you can see there are differences in Rollup Patches and OAF platform.
The System Test Environment is clearly a head of the Development environment and this is where we are facing the issue. If we patch the Development environment to the same level as the Test, then the issue will manifest itself in both environments. The client will be going live with RUP5 or higher.
The offending region is has the following structure:
The parent/root page is : XxxMyQueyRegionRN, which is a “defaultSingleColumn” Region Style with its own controller class.
Immediately under the above region there is a “query” region style child, which has the following attributes:
Construction Mode : resultBasedSearch
Include Simple Panel : False
Include Views Panel : False
Include Advanced Panel : True
Initial Panel : advanced
Show Views Panel Control: True
The above Query Region has underneath it a “table” region style, which essentially is the results table.
This table node has a number of “messageStyledText” fields under it. Each field is mapped to a VO and VO attribute.
A number of these items have their “Search Allowed” property set to True, which means that are search-able fields in the Search Panel.
There is nothing special or extraordinary about the above region and yet it renders in one environment and then hangs (i.e. the page times-out) in another. How do I know it is this specific region that causes the time-out? well when I take it out of the parent Page, the page works fine in both environments and as soon as include it, it times-out.
Has anyone encountered this issue before? Has the OAF technology changed between RUP 4 and RUP5 sufficiently, so that certain custom pages will have to be re-developed?
Any help and Guidance is appreciated.
Thanks
Patrice.

Answer 1

Patrick,
Check the apache log to see if contains any error or whether it lists the process which is taking so much time to lead to timeouts.
In case you have a blind query based search result table population on page rendering, try to render the page without the query execution.
--Shiv