10g vs 11g: VO bind variable values stale on jbo.ampool.doampooling = false
Hi gang
(JDev 11g Build 5188)
I'm currently doing some testing as recommended by the Fusion 11g Guide to test the ADF BC state management with jbo.ampool.doampooling = false (see sections 36 and 37). I'm seeing different behaviour under 11g vs 10g.
I have a single updateable VO with a query restricted by a single bind variable. I have a single JSF page with the bind variable as an inputText control, the executeWithParams operation as a commandButton, and a table showing the results from the VO.
Under 10g I can:
1) Open the page
2) Enter a value (say X) for the bind variable, hit the executeWithParams button and correctly see results in the table matching bind variable value X.
3) Enter a different value for the bind variable (say Y), hit the executeWithParams button and correctly see results in the table matching value of the bind variable value Y.
Under 11g I get different behaviour for # 3. Instead when I press the executeWithParams button with the value set to Y, the table still show results for the previous bind variable value X?
It must be noted that if I set jbo.ampool.doampooling = true, the problem disappears, but presumably the error will reappear in a production system under load, so I need to track down what's happening here.
Possibly I'm seeing a bug, but given the large amount of 11g changes and large amount of documentation I need to read on state management, it could just be I've missed something vital for 11g.
Does anybody have any opinions what's happening here?
Thanks for your help in advance.
CM.