Hi Uta,
the log entry is created in
info.magnolia.module.templatingkit.resources.Resource - in case there's been
any Exception in #getFarFutureCachingTimeStamp.
Checking out the code I'd say it's neither a caching nor a access right
problems. The cases that the node or the lastModification date are 'null' are
explicitly treated so my guess is your uri2RepositoryManager is or has been
null. It's initialized via IoC - see core.xml:
<component>
<type>info.magnolia.cms.beans.config.URI2RepositoryManager</type>
<workspace>config</workspace>
<path>/server/URI2RepositoryMapping</path>
<observed>true</observed>
<scope>singleton</scope>
</component>
I never heard about this problem before - also I didn't find any JIRA issue
about it. Maybe that node had temporarily been misconfigured?
In case it shows up again, I'd recommend checking the
/server/URI2RepositoryMapping node in the config workspace.
Regards
Daniel
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=054c2fa4-451b-41d4-b7d1-17f55a280a58
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
