What do you mean it will leak the refresh thread? Won't the thread
complete and then die? I didn't think the thread lived on forever, but
only for as long as it took to refresh the group tree one time.
But I agree, if quartz is available, that's what quartz is good at and
I'd strongly advocate for using it instead. I'm not sure how I missed
knowing that got added to uPortal in the past. *shrug* Now I do.
---- Cris J H
On 08/06/2010 10:59 AM, Eric Dalquist wrote:
The change set for SmartLdap will leak the refresh thread when the
portal webapp is reloaded.
If possible this refresh process should be a periodic trigger managed by
the quartz scheduler that already exists in 3.x. Using the schedule
guarantees correct thread handling and configuration level manageability
of the refresh rate.
https://developer.jasig.org/source/changelog/jasigsvn/uPortal?cs=21422
-Eric
--
You are currently subscribed to uportal-dev@lists.ja-sig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
