I'm working on application in ADF (ADF BC, ADF Faces) with JDeveloper 188.8.131.52 (application deployed on customer's site in Weblogic Server 10.3.6)
and in one page I'm having a button behind which is a code to execute a query against a table whose data is going to be shown in popup window.
Query limits the number of records to be shown to 100 (in query: rownum <= 100).
In my development environment this works fine, but there is a problem on customer's site.
For the query to execute it takes about 20 seconds at the site of customer. After that in backing bean there is a code to show popup.
In the page - popup starts showing (it means that query ended) but never fetching data in the table (all the time there is a message - "Fetching data" like framework is retrieving it but nothing happens).
I have tested a query in SQL*plus - it returns data.
I couldn't find out what is the reason for such behaviour.
Do you have any suggestions what to try?
Hi, JDeveloper 184.108.40.206 (application deployed on customer's site in Weblogic Server 10.3.6)
Have you upgraded the application to JDeveloper 220.127.116.11 before deploying it to WLS 10.3.6? Note that the requirement is that JDeveloper versions and WLS versions must match
Regarding the problem, its hard to say for us what the problem is as there seems to be custom code involved that we don't know about. One difference could be that your customer site has more data to query than during building the application. It doesn't matter if only the first 100 rows are queried if the SQL itself filters a million data to determine the first 100
I've found the reason for not populating table in popup.
Although there is a limitation to the number of rows displayed in table in the form of additional where clause: "rownum <=n" this part of where clause is added to the VO in overridden method: executeQueryForCollection.
Before executing this method framework is executing: getEstimatedRowCount which when executed for the first time through method getQueryHitCount executes a query against the database (select count(1) from... without my rowum <=n which is added to the query afterwards in above mentioned method executeQueryForCollection).
My question is: if I don't want to add rownum <= n at design-time, where it would be the best place to add it to the query so to avoid above described situation and to have that rownum <= n in place for the count query as well?