Screen redraw problems after issuing plugins.rawSQL.flushAll

Classic Servoy
1

I am getting lockups of Servoy Developer and screen redraw problems in a tabpanel with a table view form after I iterate through the foundset in the table view form. The offending line of code where it always bombs is this:

plugins.rawSQL.flushAllClientsCache('user_data', 'myTable')

If I comment this line out, it works fine. It redraws the table view form within the tabpanel using other portions of the screen. As soon as I click on another record, it redraws correctly. Sometimes it will crash Servoy Developer and I have to open taskmanager to kill it.

I’ve used this line of code in other places without trouble. Anyone know of any issues with this plugin?

Java 1.6_11 (same thing on 1.6_05)
Servoy 3.5.7 Developer
Windows XP
2GB Ram
NVidia integrated graphics adapter
Mysql 5.0.x
No other software apps running

2

You broadcast the flush to all clients.

Is there a difference in # clients?

3

Happens with just one client or with several. Happens consistently on other servers too (all windows).

4

Hi Jason, one question: why are you flushing the cache inside a loop block? Flushing all clients cache is an expansive operation (think about 20 clients that receive the flush msg and try to read again all the data from the db, think about doing that once every iteration of the loop for, let’s say 100 times…).
Wouldn’t be enough to flush the cache just once at the end of the loop?
Having said that I think you should create a case in the support system for this issue, maybe there is something wrong or maybe such a usage of this function is simply not allowed.

5

I have to run flushcache because the Fedex software running at their place updates a table in my database. To get the latest shipping records, I have to flush the cache.

I only run it once at the end of the loop, and this only gets run once or twice a day. Shouldn’t have too big of an impact.

Not sure if there’s a better way to do this. If I have to check hundreds of records one at a time to update them, to avoid the flush, that seems more expensive than just one hit for the whole table.

6

Oh, sorry, I misunderstood your post.
I think the right thing to do is to create a case in the support system for this issue.