Server side changes not taking effect

[Segi]

Ever since the latest version of eBase was released, I've had a problem where I make a change to a client or server side script but the changes do not immediately go into effect after I reload the form.

Whenever I make a change to a form I reload the URL but the changes are obviously not present. When this happens, I can even confirm that this is the case by adding gibberish to the script. Rather than crashing the form (as it should do) it appears as if an older cached copy of the script is being used. When this happens the only way to resolve it is to restart the server which can be difficult to do at any given time since we always have users actively using an eBase application.

I have seen this error on both Firefox on Chrome and have deleted the browser cache on both browsers and still have this issue.

[Jon]

We are aware of this problem, but at the moment don't know what's causing it. Hopefully we'll get it sorted out in the next service pack. For anybody else viewing this post, steps to address this issue are:

1. Restart the server
2. If that doesn't work, delete all the cache files (*.data) in UfsServer/tomcat/work/Catalina/localhost/<webapp> then restart the server

[alexmcclune]

We have just encountered something very similar to this (we are running ebase 4.5.1) and deleting the tomcat /tmp files did the trick for us.

We have been making lots of changes without any problem until adding a grid to a page and programmatically hiding/unhiding it (we don't use many) - then the problems occurred - after tomcat restart (and /tmp files deletion) the problems went away.

We noticed the changes were picked up when running the form from Ebase but any other call to the form didn't pick the changes up.

[Segi]

I am still having this problem. I can't try Alex' solution since that temp folder is always empty.

Do you guys think that this issue will be resolved in 5.0 ?

[Jon]

Should be before V5.0. We would hope to fix this with a service pack release for V4.5.

[Segi]

What is the status of this bug ? Has it been addressed in one of the 4.5 service packs ? I am still experiencing this issue.

[Jon]

This was fixed in V4.5.3, released in February 2015.

[Segi]

Jon,

I am on 4.5.3.

I have a form that has a table that is initially hidden until after I call fetchTable. After fetchTable(). I do tables.mytable.control.setHidden(false);

The table does not appear after I display it. If I press F5 in the browser window, the table appears as it should. It sounds like the exact same behavior where there's caching going on.

[Jon]

Doesn't sound like a caching problem to me. Instead of tables.mytable.control.setHidden(false), you might try controls.TABLECONTROLNAME.setHidden(false).

[Segi]

Jon,

I have a somewhat similar issue where I have a button that is marked as Hidden and is not supposed to be displayed when my form is initially presented to the user but is still being displayed unless I call setHidden(true) in the Before Page event. This does sound like a caching issue to me.

By the way, I am on 4.5.3

[Jon]

Perhaps I should explain something about the caching problem that was fixed: the problem was that changes made in the designer were not being picked up by the server, and forms would continue to execute with an older version or some of the scripts might be older versions. These older versions were being loaded from a cache incorrectly. This problem could always be resolved by stopping the server, removing the cache files in tomcat/work/Catalina/localhost/webapp and restarting the server - this forces the system to ignore any cached entities and reload everything from the database.