ablePageLink:fooLink-org.apache.wicket.markup.html.panel.Fragment:track-org.apache.wicket.markup.html.list.ListItem:14-my.company.FooListPanel$1:fooList-my.company.FooListPanel:foos-org.apache.wicket.markup.html.list.ListItem:0-my.company.BarListPanel$1:bars-my.company.FooListPanel:panel-my.company.boxes.BodyBox:2-org.apache.wicket.
of my pages.
> Let's say there are 5 possible positions, this would cause 2500 thousand
> cached entries, each with a key of 300+ characters plus some more
> characters
> for the cached message - feel free to do the maths. From a quick estimate
> I'd say: No wonder, thi
;>>> due
>>>>>>>> to
>>>>>>>> an OutOfMemoryError ("GC overhead limit exceeded" to be precise).
>>>>>>>> Using
>>>>>>>> jhat, the "175456 instances of class
>>>>
usic.FoobarPage:
43-de-null
Those numbers pretty much convinced me: The localizer cache has blown
away
my application.
Looking at this hash keys, I suspect the following problem: those
strings
are constructed from the "position" of a localized String on a page,
which
is quite a bad th
pOnOutOfMemoryError flag) of a recent application cache
>>>>>>>> due
>>>>>>>> to
>>>>>>>> an OutOfMemoryError ("GC overhead limit exceeded" to be precise).
>>>>>>>> Using
>>>>>>>> jhat, t
r-my.company.pages.music.FoobarPage:
43-de-null
Those numbers pretty much convinced me: The localizer cache has blown
away
my application.
Looking at this hash keys, I suspect the following problem: those
strings
are constructed from the "position" of a localized String on a page,
which
ig one: Localizer.cache has a hash table length
>>>>>> of
>>>>>> 262144, each of its 32 segments with about 5300 entries, where a hash
>>>>>> key
>>>>>> is
>>>>>> a string, sometimes longer than 500 characte
e.wicket.markup.html.list.ListItem:0-
my.company.BarListPanel$1:bars-my.company.FooListPanel:panel-
my.company.boxes.BodyBox:2-
org.apache.wicket.markup.repeater.RepeatingView:body-
my.company.layout.Border:border-my.company.pages.music.FoobarPage:
43-de-null
Those numbers pretty much convinced me: The
, sometimes longer than 500 charactes, similar to (see
>>>> Localizer.getCacheKey(String,Component)):
>>>>
>>>> fooTitle.bar-
>>>> org.apache.wicket.markup.html.link.BookmarkablePageLink:fooLink-
>>>> org.apache.wicket.markup.html.panel.Fra
el-
my.company.boxes.BodyBox:2-
org.apache.wicket.markup.repeater.RepeatingView:body-
my.company.layout.Border:border-my.company.pages.music.FoobarPage:
43-de-null
Those numbers pretty much convinced me: The localizer cache has
blown
away
my application.
Looking at this hash keys, I suspect the fol
:panel-my.company.boxes.BodyBox:2-org.apache.wicket.markup.repeater.RepeatingView:body-my.company.layout.Border:border-my.company.pages.music.FoobarPage:43-de-null
>>
>> Those numbers pretty much convinced me: The localizer cache has blown
>> away
>> my application.
>>
em:0-my.company.BarListPanel$1:bars-my.company.FooListPanel:panel-my.company.boxes.BodyBox:2-org.apache.wicket.markup.repeater.RepeatingView:body-my.company.layout.Border:border-my.company.pages.music.FoobarPage:43-de-null
>
> Those numbers pretty much convinced me: The localizer cache has blown away
&
es, each with a key of 300+ characters plus some more characters
for the cached message - feel free to do the maths. From a quick estimate
I'd say: No wonder, this has blown away my app.
As a quick fix, I'd suggest to regularly clear the localizer cache, use a
more sophisticated cache (t
ngs().getLocalizer().clearCache() might do
> > the trick.
> >
> > -Matej
> >
> > On Jan 4, 2008 9:00 PM, marcus dickerhof <[EMAIL PROTECTED]> wrote:
> > > Hello,
> > > is there a possiblity to globally clear the localizer cache?
> > > I ha
> is there a possiblity to globally clear the localizer cache?
> > I have a database stringresource, which might get updated.
> > If that happens I do not want to restart the application.
> > I want to have button with which I can c
Application.getResourceSettings().getLocalizer().clearCache() might do
the trick.
-Matej
On Jan 4, 2008 9:00 PM, marcus dickerhof <[EMAIL PROTECTED]> wrote:
> Hello,
> is there a possiblity to globally clear the localizer cache?
> I have a database stringresource, which might ge
Hello,
is there a possiblity to globally clear the localizer cache?
I have a database stringresource, which might get updated.
If that happens I do not want to restart the application.
I want to have button with which I can clear the cache.
Thanks!
Best regards
Marcus
There's a discussion on the JIRA whether or not to make the localizer
cache in development mode, but just for reference (and for other people
searching for localizer and cache), Juergen showed me how to get what I
want by adding the following code in the init() method of my application:
iting
> of your keys you can easily manually create a link to clear the
> localizer cache on demand on the production server. If you really want
> dynamic content I don't really know if the message mechanism is the
> right way to go?
>
> Regards,
> Sebastiaan
>
>
dy rendered the page once the cache is not cleared and it keeps
finding the key=null entry in the cache.
* if you add your own database string resource loader, the cache is
never flushed at all.
I know I can add a link to flush the localizer cache if and only if
we're in development mod
at to do with it?
I think it would be quite expensive generally not to cache if the
content is from the DB. It seems to me that if you allow content editing
of your keys you can easily manually create a link to clear the
localizer cache on demand on the production server. If you really want
dy
se string resource loader, the cache is
> never flushed at all.
>
> I know I can add a link to flush the localizer cache if and only if
> we're in development mode, but I think a Settings options could be nice
> to just turn off caching (my laptop is fast enough, I really
ey=null entry in the cache.
>
> * if you add your own database string resource loader, the cache is
> never flushed at all.
>
> I know I can add a link to flush the localizer cache if and only if
> we're in development mode, but I think a Settings options could be nice
> t
rties file for a page or component after you
already rendered the page once the cache is not cleared and it keeps
finding the key=null entry in the cache.
* if you add your own database string resource loader, the cache is
never flushed at all.
I know I can add a link to flush the localizer cac
24 matches
Mail list logo
