So after some experimentation with the the ehcache.xml file we've discovered that if we set below timeToLive value to a non-zero value we get the behavior we expect, with changes reflected in user fragments etc.

<cache name="org.jasig.portal.layout.dlm.LAYOUT_CACHE"
timeToLiveSeconds="05"

It looks like the value has the following definition:

timeToLiveSeconds:
Sets the time to live for an element before it expires.
i.e. The maximum time between creation time and when an element expires.
Is only used if the element is not eternal.
Optional attribute. A value of 0 means that and Element can live for infinity.
The default value is 0.

Any reason this is set to zero?  Shouldn't a non-zero value be committed?

Eric would you mind sharing your ehcache.xml settings?



Eric Dalquist wrote:
The only thing I can think of is a caching issue somewhere, we're on about 3.1-M1 and I don't think we've seen this issue but I'll see if I can verify that tomorrow. I'll also look into any local modifications we might have that would change how things work with DLM fragments for us.

-Eric

Arlo White wrote:
We've encountered some severe issues with DLM and fragment-layouts. As we started testing fragment-layout changes in our customized portal we started noticing some strange behavior. After logging into a fragment-layout user and moving channels around, then logging out and back in those changes would revert. Sometimes refreshing once would bring these changes in. Sometimes switching to the customize screen would show the changes, then going back to the tab would show the changes that previously weren't visible.

If a fragment-layout is in this state users don't inherit the changes. However, if you restart the server and login as the fragment-layout user, the changes appear correctly and are inherited by users.

After encountering these issues I decided to confirm whether the bug is in uPortal trunk.

I just ran a complete initportal, with the default hsql database and default entities.

I moved a few channels around in the welcome-lo fragment. After I logged out and back in as welcome-lo the changes disappeared. When I went to Customize I saw those changes. At this point, if you click the Welcome tab, the changes won't be there. However, if you click "Back to Home" the changes will be in the welcome tab. Once you logout and back in the changes disappear again. If you login as a user they don't get the changes, if you revert the layout you can see the changes.

I presume that restarting the server would cause the user to inherit the changes without reverting layouts but the server shouldn't need to be restarted just because a fragment-layout changed.

Is DLM not functional in trunk? Are these known issues. Please reply as soon as possible as we're planning on rolling 3.1 to production this Sunday.



--
Darren Kraker
Software Engineer
Application Management / ITS
mailto:[email protected]
Office (805) 756-2696

--
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Reply via email to