Java Development Tools

I have an Entity based on a GLOBAL temp table. I have a ViewObject based on the Entity. A stored procedure is called from the client that populates the GLOBAL temp table and then calls executeQuery on the ViewObject. The first time the user does this, all rows display fine. When the user changes the selection criteria and clicks a button a 2nd time, the same procedure is called which clears the GLOBAL temp table and repopulates it with the new data. An exception occurs, however, stating that there are too many rows that match the key. The problem seems to be that the Enity has cached the rows from the first execute, but those rows aren't flushed when the 2nd execute is called, which makes sense. It seems that I just need to force the Entity to clear it's cache after my procedure is called, but before the executeQuery is called. I have tried that from the client side by calling clearCache on the view AND clearEntityCache on the transaction, but they don't seem to do anything. I have also called clear cache on the app module side in the method that calls the stored procedure, but it doesn't seem to do anything either. I also turned on the JBO debugging messages and I can't see any message stating that the Entity or View cache was cleared. It appears that these calls do nothing.

Is there a way to work around this to make the Entity/View chaches completely refresh from the database?

Thanks
Erik