ADF, ADF Exceptions

JBO-25058: Definition vc_temp_1 of type Variable is not found in …

“JBO-25058: Definition vc_temp_1 of type Variable is not found in …”.
What can be the reason?
ADF creates/reuses application module (AM) instance for each user request. It is passivated (saved) after each HTTP request (if configured accordingly). When in application there are used some queries with view criteria, filter variables are passivated  for according AM as well. During the next HTTP request of the same user it is recalled and used in processing.
But… There are couple important AM parameters:

  • Idle Instance Timeout (s) = 600 (default)
  • Pool Polling Interval (s) = 600 (default)

In my case I’ve got JBO-25058 error when trying to re-execute query with view criteria after 600s. Simply my referenced AM module with view criteria variable was purged before…
So the fix was simple – just increased mentioned AM parameters to 1800s. I’ve choosed such period because session timeout in my app is the same. That means user will not experience such error because session simply ends before.

2 thoughts on “JBO-25058: Definition vc_temp_1 of type Variable is not found in …

  1. Hi Mosta!

    Thanks for a comment! I'm sorry this did't help. This is kind of pretty generic error and reasons of course can be of wide range. Also it can be related to datatype used for bind variable or attribute it is mapped to.
    Though if its application module configuration related issue, would recommend to do one more test:
    * Ensure particular AM properties are set like this:
    ** jbo.txn.disconnect_level=1
    ** jbo.ampool.timetolive=-1 ()
    ** jbo.ampool.maxavailablesize and jbo.recyclethreshold are set both to equal value, i.e. 10
    * Those settings will ensure to keep AM instances alive and referenced to DB (reserved DB connections). Btw be sure you have available free DB connection of amount set in either jbo.ampool.maxavailablesize and jbo.recyclethreshold properties.
    * Try now whether your issue still persists. If yes, probably thats not AM configuration related issue…

Leave a Reply

Your email address will not be published.