BUG? Application Module State Management

Question

I have 2 read-only view objects VO1 & VO2 with a View Link that links them by a primary key field. VO1 (master) is on the first .jspx page and VO2 (detail) is on the 2nd .jspx page. VO1 has a SQL query, but is populated programmatically in an App Module Service method that sets the where clause parameters. VO2 is on a separate .jspx page. VO2 has one bind variable in its SQL query that is populated when the user clicks a commandLink on a row within VO1 - this takes the user to the 2nd .jspx page to view VO2 table results.
The issue is that when the user navigates back to the first .jspx page containing VO1, a duplicate row is added to the end the data table (or as the first record on the second page of results if there are multiple pages.) If I re-query VO1, re-sort the data using the column headings, or passivate the data (see below), the duplicate row goes away. Note I have tried using the same iterator on both pages and this same issue occurs.
Ok - after 5 days of troubleshooting, here is the potential bug. If Application Pooling is enabled on the Application Module, I experience the issue above. If I don't enale Application Pooling, and Passivate state for the App Module, this issue does not occur (see below):
Application Module Settings - Error Occurs if Pooling is enabled
(unchecked) Failover Transaction State Upon Managed Release
(unchecked) Disconnect Application Module Upon Release
(checked) Support Dynamic JDBC Credentials
(checked) Reset Non-Transcational State Upon Unmanaged Release
(checked) Enable Application Module Pooing
If I un-check Enable Application Module Pooling the error does NOT occur. Note I've experimented with many combinations, and its only the Application Module Pooling that affects the behavior.
Note both view objects are set to Passivate state (but not for transient values, though tested passivating those as well and there was no difference.)
Can someone please advise? This is a showstopper for implementing our application to production. See the threads below for more information. Finally note that I have not yet been able to replicate this in a simple test case, but there is some specific characteristics about my current application causing this behavior (and it appears others have experienced as well.)
Duplicate rows displayed in list
Need help  - Duplicate Rows being added to View Object?
Thanks.
Here is the code on the AM service method to populate the rows for VO1 (no insert or create rows - only executing the query):
ViewObject vo1 = findViewObject("VO1");
vo1.setMaxFetchSize(250); // set max fetch size 250
vo1.setWhereClauseParam(0, x0);
vo1.setWhereClauseParam(1, x1);
vo1.setWhereClauseParam(2, x2);
vo1.setWhereClauseParam(3, x3);
vo1.setWhereClauseParam(4, x4);
vo1.setWhereClauseParam(5, x5);
vo1.setWhereClauseParam(6, x6);
vo1.setWhereClauseParam(7, x7);
vo1.setWhereClauseParam(8, x8);
vo1.setWhereClauseParam(9, x9);
vo1.setWhereClauseParam(10, x10);
vo1.executeQuery();
Message was edited by:
javaX

Answer 1

More information on this issue:
After further testing, I discovered that the 'Disconnect Application Module Upon Release' also plays a factor with this issue.
If 'Enable Application Module Pooling' is unchecked the issue does not occur because the view object is passivated.
If 'Enable Application Module Pooling' is checked (jbo.ampool.doampooling=true), then the issue occurs UNLESS I also set 'Disconnect Application Module Upon Release' (jbo.doconnnectionpooling=true). If I set the latter to true, then I do not experience the duplicate row issue. I would rather not have to enable jbo.doconnectionpooling=true because of the performance impacts as recommended in the dev guide. Any Suggestions?
-- updated on 10/1/06 ----
Setting jbo.doconnectionpooling=true only fixes this issue when I use a ViewLink as the mechanism to pass the row Id from VO1 (master on .jspx page #1) to VO2 (detail on page #2.) If I use an actionListener to pass the value from page #1 to page #2, setting jbo.doconnectionpooling=true does not fix the issue.
<af:commandLink actionListener="#{bindings.setCurrentRowWithKey.execute}"
action="page2" text="#{row.Name}">
<af:setActionListener from="#{row.Id}" to="#{backing_bean_page2.rowid}"/>
</af:commandLink>
Message was edited by:
javaX