JDeveloper Team: How Do I minimize the number of Oracle Sessions using Data Tags?

Question

I am trying to create a stateful application thru my JSP pages. Everytime there is a reference to the application module using the data tag, it looks like it creates a new Oracle Session. But thats not what I want to do.
I have a module in which my first JSP page allows viewing of the data and in subsequent pages I allow insert, update, delete, commit etc.
My Questions:
1) The problem that I am encountering is that every new page that I go to creates a new Oracle session even though I specify the "Stateful" release mode.
How do I avoid this?
It looks like , if one browser user can potentially create 10-20 oracle sessions thru one module, imagine what the impact will be when we have hundreds of users.
2) The sample JSP pages I saw has the username and password hard coded in it every time. Why? For a stateful application can I not specify the username and password just once and have the other JSP pages use the same userid and password.
What are the pros and cons? I thought if I don't use the username and password in all the JSP pages then it probably will not create additional Oracle sessions but that is not true!!
3) If it creates several Oracle sessions , will it not cause locking problems? If so, How do I minimize locking problems in a stateful application.
JDeveloper Team Please advise!!
AM I missing something? I would appreciate if someone can help me out!
null

Answer 1

Thanks a lot for the information. That thread was indeed very helpful. But it still didn't answer all my questions:
1) In the thread you mentioned, it mostly talks about Web beans. In a jsp page (using Web bean) we need to first invoke setReleaseApplicationResources(true) and then invoke releaseApplicationResources().
Does this apply to data tags? I mean I have a tag <jbo:ReleasePageResources releasemode="Stateful" />. Is this enough to release the application module back to the pool or do I have to have something equivalent of setReleaseApplicationResources(true)?
2. In a stateful application, the state of an application is maintained between requests via a browser cookie. For each browser, you can have one state per application module class. I was attempting to run "several browser sessions from the same machine" and the end result was that I got errors and unpredictable results ie it returned me far fewer rows then I saw originally. Should I be actually be running the browser session from different machines?
3. In JDeveloper Documentation (section About Application Module pooling) there is a note section : "If the application module is not recycled the data stays the same. However if the application module was recycled and then activated through a failover, the activation logic re-executes the view objects, so it may bring in more or less rows then originally seen by the clients due to any database updates that have occured."
This is exactly what is happening to me? How do I get rid of this problem? I want to be able to see all the original rows + any new rows That have been committed. Please advise!
4. Are the JDBC connections tied to application module instances? Is it one JDBC connection per application module instance? So, in a stateful JSP, if I end up using a different application I also get a different JDBC connection. IS this true?
5. Does the no of application module instances depend on the no of available JDBC connections? Because it looks like if you set the max no of connections to "5" and set the max no of application module instances to "10", It will be able to instantiate only "5" application module instances due to the limitation set by connection pool.
6. At times I get errors which indicates that the row in view object does not exist. Is this something familiar? Or is it the same problem that John discussed in his thread.
Thanks in advance!