With VPD I see other users results - problems with AM caching??

Question

I am using JDeveloper 11.1.1.0.2.
In my application I have 3 Appllication Modules (Admin, Store and Sale) and I use VPD and setcontext in every AM.
@Override
protected void prepareSession(Session session) {
super.prepareSession(session);
setVPDcontext();
private void setVPDcontext() {
String userName = getUserContext().getUserId();
String ind = "J";
String sql =
"begin xxx_context.set_context('" + userName +
"', '" + ind + "'); end;";
java.sql.CallableStatement stmt = null;
try {
stmt = getDBTransaction().createCallableStatement(sql, 0);
stmt.execute();
catch (SQLException se) {
throw new JboException(se.getMessage());
finally {
if (stmt != null) {
try {
stmt.close();
catch (SQLException e) {
throw new JboException(e);
The problem is that I see the results of previous VPD-queries.
3 testcases:
1. User1 has access to 3 AM (Admin, Store, Sale), if I log in I can see the correct results in the application (in Admin, Store and Sale).
User2 has only access to 1 AM (Store), If I log in as User2 I see the results of User1 in Store (wrong).
2. After restarting the weblogic server and logging in as User2 I see the correct results for User2!
If I log in as User1 I see the results of User2 in Store (wrong!!) and the correct results in Admin and Sale!
3. User1 has access to 3 AM (Admin, Store, Sale), if I login as user User1 I only use Admin and Sale (so there are no cached results for Store).
User3 has access to Sale and Store. If I login as User3 I see the results of User1 in Sale and the correct result in Store.
Conclusion: I see cached query results of the first user who logges in a Application Module. Only restarting the Weblogic Server makes the cache empty. The problem only occurs with queries with VPD.
How can I resolve this problem?

Answer 1

User,
I'm on a bind variable crusade today (not the answer to your question, unfortunately). Please please please please use bind variables instead of gluing literals together like that (use PreparedStatement instead of callable statement). You can also parse the PreparedStatement once and avoid the overhead of parsing on each call to prepareSession.
John