Hi all,
i'm writing this post hoping someone can help us to find the reason behind a weird behavior shown by ADF View Object (VO) instances in some of our Fusion Web Applications.
In short, what happens is that, in certain conditions (usually after redeployment of applications), the VO instances of our applications execute correctly the query associated to them returning all the rows you would expect, but all rows are empty, that is each row has all its attributes set to null values (even those attributes that cannot be null because their are defined as not nullable fields on the DB schema).
In our specific case, the issue is related to read-only VO and, as i said, it usually shows up after redeployment of application: until now, the only "solution" we find to solve the issue is to restart Weblogic server ; after rebooting the server the issue goes away and the application returns to work fine. The issue happens often in clustered environments, but sometimes it happens even in the JDeveloper integrated WebLogic server.
We are using JDeveloper 11.1.1.7 and applications run on Weblogic 10.3.6. Further, applications reference ADF shared libraries and some of these applications share a common "context-root prefix", that is the context-root of all these applications is in the form "/PREFIX/APP_i_CTX_ROOT", where PREFIX is a constant, while APP_i_CTX_ROOT is obviously a string specific to each application.
I don't know if these two peculiarities (referencing shared libraries and sharing a common context-root prefix) can cause the issue, but i mentioned them because we started using shared libraries only recently and is the first time that we have multiple applications with the same context-root prefix deployed on the same environment.
I hope someone of you has already faced this kind of issue and can come out with an explanation. Any kind of help will be appreciated.
Thank you.
Bye.
Fabio