Stateless with Session Affinity and set jbo.ampool.maxpoolsize = 1

Question

Hi,
I would like to know more about "Stateless with Session Affinity".
If I set
jbo.ampool.maxpoolsize = 1
jbo.ampool.minavailablesize = 1
jbo.ampool.maxavailablesize = 1
in application module configuration
and have two browser clients at different computers.
If I update some values and post changed data to database without commit
at one browser
some updates using jdbc prepared statements through database connection
with following code snippet in application module
Implementation:
private Connection getCurrentConnection() throws SQLException {
PreparedStatement st = getDBTransaction().createPreparedStatement("commit",1);
Connection conn = st.getConnection();
st.close();
return conn;
, will the other web client see these post changed data with the only one
application module through the only one database connection (ignores PS_TXN connection)?
If the answer is "no", can someone explain why bc4j can do this?

Answer 1

Hi,
It's not clear to me from your post what you are trying to test. Generally speaking, every HttpSession (~browser) is assocated with a pooled AM that is associated with a single transaction context that is associated with a single "application" JDBC connection.
HttpSession->AM->Txn->Connection
The session affinity features of the BC4J framework maintain this logical dependency for you without necessarily having to tie up the physical resources at each layer.
Now, if one session posts but does not commit then the other sessions will not "see" those changes (different AMx, Txns, Connections). Once a session does commit then those changes will be visible to other sessions. However, if those other sessions have already queried/cached the modified data then those sessions will not "see" it until their caches are refreshed. Please see the documentation for a description of BC4J caching and refreshing caches. The standard technique to refresh a VO cache is to invoke executeQuery.
Hope this helps,
JR