Using Application Module in Stateless Mode

Question

Hello,
We have certain parts in our web application that is not coded using ADF-Faces, but need to use ADF-BC framework to do some data retrieving and manipulation. Our current approach is to instantiate the application module like the following:
Configuration.createRootApplicationModule(impl, config);
and after each usage we do:
Configuration.releaseRootApplicationModule(am, true);
However, the application module is not really released. We deployed pool statistic servlet from Steve Muench's "not yet documented examples" and realized that the supposed to be released application module is still in 'referenced' state and thus unavailable for usage by other session, or even other request in the same session as we dont know of anyway to tell ADFBC about current session and checkout referenced AM. As a consequence, the application is taking up DB resource so quickly and we have to restart the application every 5 minutes because it takes all available connection slot on our Oracle 10g server.
Do I instantiate and released the application module correctly? Or am I missed something?

Answer 1

In the reference you pointed, it is said that if I want the application module to be 'unmanaged' (assuming 'unmanaged' app module is what I need) I should:
"call the resetState() method on the DCDataControl class (in the oracle.adf.model.binding package)."
I'm not sure whether I'm getting this right, but I don't think I have a data control on the application module, because I instantiated it using Configuration.createRootApplicationModule().
How do I set an app module to have 'unmanaged' release level directly (not through a data control)?
Theres a resetState() in ApplicationModule class but it takes an int as an argument and Im not sure what to pass in.