[Building Sakai] tomcat restart

[Aaron Zeckoski]

The current service (2.9+) already exposes the entire set of known
config settings and has hooks for updating them and for listeners to
be notified when they change. I don't think this reflection is
necessary anymore unless you are talking about older versions of Sakai
(or I am missing a use case).

-AZ

On Thu, Jan 31, 2013 at 11:09 PM, John Bush <john.bush at rsmart.com> wrote:
> We've made some progress right ?  This piece is done,
> https://jira.sakaiproject.org/browse/SAK-22313
>
> I was actually planning on looking at this and what the next steps are
> as soon as I free up a bit.
>
> I went back and read that suggestion from Chuck again, which I imagine
> in some cases is probably safe, but you'd really have to know what you
> are doing.  Crazy that Java reflection lets you access private things
> like that, but that comes in handy when you are in a pinch.  I wish I
> hadn't read that actually, cause pretty sure I'll be writing a web
> service to expose that tomorrow, its just too handy to not have there
> when you need it.
>
> On Thu, Jan 31, 2013 at 11:15 AM, Matthew Jones <matthew at longsight.com> wrote:
>> This has been discussed over the years, but nobody has done any serious work
>> in this area for awhile. Many properties that read everytime from
>> ServerConfigurationService, you can change with this type of jsp manually.
>>
>> http://collab.sakaiproject.org/pipermail/sakai-dev/2011-May/012455.html
>>
>> This is the majority of properties. However, some properties in Sakai are
>> set via bean properties or are read only at init() so those aren't
>> changeable this way.
>>
>> Here is a jira tracking the issue, but it hasn't had much activity.
>> https://jira.sakaiproject.org/browse/KNL-739
>>
>> It's basically writing or modifying some existing IU (Like config editor) to
>> set and possibly persist the properties for the ones that are changeable,
>> and fixing all of the tools that are caching the properties so they can be
>> changed.
>>
>>
>> On Thu, Jan 31, 2013 at 1:04 PM, Sanghyun Jeon <euksa99 at gmail.com> wrote:
>>>
>>> Hello All,
>>>
>>> We have had some changes on sakai.properties and did (scheduled) restart
>>> tomcat (using cron). However, the new property setting is not affected
>>> properly.
>>> We've checked our tomcat log and tomcat indeed restarted properly (there
>>> are minor errors we always saw). Now we need another restart.  Restart
>>> tomcat is not a big deal if it is on our dev, but for production, we  have
>>> to follow our protocol: notify users one week in advance etc....really
>>> annoying
>>>
>>> When we have new war file, we do auto deploy, so that we can avoid
>>> restarting tomcat.
>>>
>>> Can anybody  know how we can avoid restart tomcat when we change our
>>> properties file?
>>>
>>> Sanghyun
>>>
>>>
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to
>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>> "unsubscribe"
>>
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
>> with a subject of "unsubscribe"
>
>
>
> --
> John Bush
> 602-490-0470
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"



-- 
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile