[Building Sakai] course site session dropdown

[Ron Peterson]

2010-09-15_09:22:34-0400 Ron Peterson <rpeterso at mtholyoke.edu>:
> 2010-09-10_15:42:52-0400 Ron Peterson <rpeterso at mtholyoke.edu>:
> > 2010-09-10_12:13:53-0400 Zhen Qian <zqian at umich.edu>:
> > > 
> > > Do you have your own implementation of CourseManagementService?
> > 
> > Nope.  I double checked that my codebase matches what you show below
> > exactly, and it does.
> > 
> > This is the data in my table.  The only term that shows up when I create
> > a new site is Spring 2010, even though the is_current field for that
> > term is 0, and the date range does not include today's date.
> 
> This is still broken for me.
> 
> A clue, perhaps.  A later read of this same table shows that the value
> of the IS_CURRENT field has reverted to the values present before my SQL
> update - w/ a one for my Summer_2010 row, and zeroes elsewhere.

I've tried this several times now, always with the same result.  Last
night, I updated these values during our 4 AM maintainance window, while
tomcat was shut down.  After I restarted Sakai, the database values
held, but the dropdown still showed the single incorrect value.  Several
hours later now, the database has again reverted to it's previous
values.  Very frustrating.

If Sakai persists these values even when the app server is shut down,
they must be serialized to disk somewhere, or stored in the database
elsewhere, no?  How/where does Sakai save state between reboots?
Knowing that, I could perhaps clear Sakai's memory manually.

-Ron-