I recently found a bug in the ThemeFileManager class, which causes
changes in production themes to not propagate to clustered servers
under some circumstances.
This only happens when:
1. the production theme is changed for the first time after a server
restart
or
2. more than one theme has been changed since the last synchronization
or
3. there is at least one theme which has never been published
I have submitted a fix for this to the trunk (r981), and the 1.0.2
(r982) and 1.0.3 (r983) releases.
The only workaround is to delete the directory
$CCM_HOME/webapps/ccm-ldn-theme/__ccm__/themes-prod/<THEME_URL> and
invoke the URL /ccm/admin/themes/sync-theme.jsp?updateType=live to
force a synchronization. The deletion and the URL access have to be on
the same server for this to work.