RE: DiskPageStore file increasing to max size by only refreshing a HomePage
It's bookmarked pages that avoid new page creation isn't it? -Original Message- From: Matej Knopp [mailto:matej.kn...@gmail.com] Sent: Thursday, January 07, 2010 3:55 PM To: users@wicket.apache.org Subject: Re: DiskPageStore file increasing to max size by only refreshing a HomePage SetVersioned(false) does not help with new page instances being created. -Matej On Thu, Jan 7, 2010 at 9:46 PM, Wilhelmsen Tor Iver toriv...@arrive.no wrote: about unversioned, i have just done a quick test on wicket-examples helloworld, adding serialVersionUID (not informed in the examples) and the result is the same: pagestore file increasing to the infinite (max size of course :) I meant Wicket's setVersioned(false); the serialVersionUID is just for binary serialization, as long as the fields do not change the computed value the VM generates for you should be the same. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DiskPageStore file increasing to max size by only refreshing a HomePage
no just the opposite bookmarkable url will create a new page (which can be state full or stateless) On Fri, Jan 8, 2010 at 14:09, Loritsch, Berin C. berin.lorit...@gd-ais.comwrote: It's bookmarked pages that avoid new page creation isn't it? -Original Message- From: Matej Knopp [mailto:matej.kn...@gmail.com] Sent: Thursday, January 07, 2010 3:55 PM To: users@wicket.apache.org Subject: Re: DiskPageStore file increasing to max size by only refreshing a HomePage SetVersioned(false) does not help with new page instances being created. -Matej On Thu, Jan 7, 2010 at 9:46 PM, Wilhelmsen Tor Iver toriv...@arrive.no wrote: about unversioned, i have just done a quick test on wicket-examples helloworld, adding serialVersionUID (not informed in the examples) and the result is the same: pagestore file increasing to the infinite (max size of course :) I meant Wicket's setVersioned(false); the serialVersionUID is just for binary serialization, as long as the fields do not change the computed value the VM generates for you should be the same. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
DiskPageStore file increasing to max size by only refreshing a HomePage
Hi, - the scenario is this: jmeter stress-testing (10 simultaneous users with no ramp-up and an infinite-loop cycle) a wicket application (extends SpringWebApplication) by only refreshing the HomePage. - the result is: observing the disk, the pagemap file for each session (10 items), there is an infinite increasing (about 10kb each one) up to arriving the 10MB (default max size for diskpagestore). opening the pagemap file (text editor) there is a repetition of the same HomePage serialized infinite times til arriving the max size allowed for the file... - the question is: why is this happening? shouldn't the pagemap only store the new pages, but only conserving one reference to a page that was already serialized? why is it serializing the same page (HomePage) to the infinite?
Re: DiskPageStore file increasing to max size by only refreshing a HomePage
Just because it's the same page class it doesn't mean it's the same page instance. How does the URL that you invoke look like? -Matej On Thu, Jan 7, 2010 at 12:32 PM, manuelbarzi manuelba...@gmail.com wrote: Hi, - the scenario is this: jmeter stress-testing (10 simultaneous users with no ramp-up and an infinite-loop cycle) a wicket application (extends SpringWebApplication) by only refreshing the HomePage. - the result is: observing the disk, the pagemap file for each session (10 items), there is an infinite increasing (about 10kb each one) up to arriving the 10MB (default max size for diskpagestore). opening the pagemap file (text editor) there is a repetition of the same HomePage serialized infinite times til arriving the max size allowed for the file... - the question is: why is this happening? shouldn't the pagemap only store the new pages, but only conserving one reference to a page that was already serialized? why is it serializing the same page (HomePage) to the infinite? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DiskPageStore file increasing to max size by only refreshing a HomePage
the url is this: http://localhost:9090/test/
Re: DiskPageStore file increasing to max size by only refreshing a HomePage
if you constantly target exactly that url then that will be a new page everytime because thats just a bookmarkable url. not an instance url. On Thu, Jan 7, 2010 at 12:52, manuelbarzi manuelba...@gmail.com wrote: the url is this: http://localhost:9090/test/
Re: DiskPageStore file increasing to max size by only refreshing a HomePage
if this is the behaviour by default, then, how do you avoid a DoS attack? i mean, to put an example, if a simple app like this receives thousand of users just refreshing the home page, then the pagestore will be overloaded... may this become a disk I/O overhead and its other possible consequences.
Re: DiskPageStore file increasing to max size by only refreshing a HomePage
You have the exact same problem with every stateful application. If you want to avoid a DoS attack (which isn't really always possible) you need a good firewall. -Matej On Thu, Jan 7, 2010 at 2:29 PM, manuelbarzi manuelba...@gmail.com wrote: if this is the behaviour by default, then, how do you avoid a DoS attack? i mean, to put an example, if a simple app like this receives thousand of users just refreshing the home page, then the pagestore will be overloaded... may this become a disk I/O overhead and its other possible consequences. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DiskPageStore file increasing to max size by only refreshing a HomePage
hmmm... but we are talking about something very basic: the home page! there's no way to avoid repetition of this page in pagestore? i guess pagestore does not repeat other internal pages (with extended url - not home page - if their are correctly independent, no new object references inside on each reload and so on, let's say) by following internal rules (based on object state and references), why couldn't it be applied a similar mechanism for the home page? On Thu, Jan 7, 2010 at 2:31 PM, Matej Knopp matej.kn...@gmail.com wrote: You have the exact same problem with every stateful application. If you want to avoid a DoS attack (which isn't really always possible) you need a good firewall. -Matej On Thu, Jan 7, 2010 at 2:29 PM, manuelbarzi manuelba...@gmail.com wrote: if this is the behaviour by default, then, how do you avoid a DoS attack? i mean, to put an example, if a simple app like this receives thousand of users just refreshing the home page, then the pagestore will be overloaded... may this become a disk I/O overhead and its other possible consequences. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
SV: DiskPageStore file increasing to max size by only refreshing a HomePage
hmmm... but we are talking about something very basic: the home page! Have you set it unversioned? How about trying to make it stateless? - Tor Iver - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DiskPageStore file increasing to max size by only refreshing a HomePage
You can make your home page stateless. Of course that limits what components you can put on it. -Matej On Thu, Jan 7, 2010 at 2:42 PM, manuelbarzi manuelba...@gmail.com wrote: hmmm... but we are talking about something very basic: the home page! there's no way to avoid repetition of this page in pagestore? i guess pagestore does not repeat other internal pages (with extended url - not home page - if their are correctly independent, no new object references inside on each reload and so on, let's say) by following internal rules (based on object state and references), why couldn't it be applied a similar mechanism for the home page? On Thu, Jan 7, 2010 at 2:31 PM, Matej Knopp matej.kn...@gmail.com wrote: You have the exact same problem with every stateful application. If you want to avoid a DoS attack (which isn't really always possible) you need a good firewall. -Matej On Thu, Jan 7, 2010 at 2:29 PM, manuelbarzi manuelba...@gmail.com wrote: if this is the behaviour by default, then, how do you avoid a DoS attack? i mean, to put an example, if a simple app like this receives thousand of users just refreshing the home page, then the pagestore will be overloaded... may this become a disk I/O overhead and its other possible consequences. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DiskPageStore file increasing to max size by only refreshing a HomePage
Would it be a good idea to be able to specify the pagestore limits on a per-wicket-session base? So you could for example increase the page store limits once a user has successfully authenticated. DoS web clients usually don't go through the mess to authenticate first. Also multiple authentications of the same user could be easily detected. So DoS should be a little harder. Am 07.01.2010 um 17:05 schrieb Johan Compagner: what is the definition of an overloaded pagestore? if the page store can be overloaded (so more then it should load) then it is a bug of wicket. But even if you get a dos attack then max 10MB per user will be allocated yes, but thats not overloading in my point of view. you could always decrease it so thats it is not max 10MB On Thu, Jan 7, 2010 at 14:29, manuelbarzi manuelba...@gmail.com wrote: if this is the behaviour by default, then, how do you avoid a DoS attack? i mean, to put an example, if a simple app like this receives thousand of users just refreshing the home page, then the pagestore will be overloaded... may this become a disk I/O overhead and its other possible consequences. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DiskPageStore file increasing to max size by only refreshing a HomePage
that good be great! dos attack is very rude scenario? ok, a more realistic scenario would be - as happens here - an app that has a very huge amount of users during only one week per year (about 40k users connecting to this app for subscriptions and checking some personal information). let's say 1k users just have fun refreshing the site... would it be possible to control pagestore size based on session and loggged-in users?
Re: DiskPageStore file increasing to max size by only refreshing a HomePage
about unversioned, i have just done a quick test on wicket-examples helloworld, adding serialVersionUID (not informed in the examples) and the result is the same: pagestore file increasing to the infinite (max size of course :) stateless page is next, but limitations in this scenario should be taken into account, as expressed here in some post of this thread... On Thu, Jan 7, 2010 at 2:58 PM, Wilhelmsen Tor Iver toriv...@arrive.nowrote: hmmm... but we are talking about something very basic: the home page! Have you set it unversioned? How about trying to make it stateless? - Tor Iver - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
SV: DiskPageStore file increasing to max size by only refreshing a HomePage
about unversioned, i have just done a quick test on wicket-examples helloworld, adding serialVersionUID (not informed in the examples) and the result is the same: pagestore file increasing to the infinite (max size of course :) I meant Wicket's setVersioned(false); the serialVersionUID is just for binary serialization, as long as the fields do not change the computed value the VM generates for you should be the same. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DiskPageStore file increasing to max size by only refreshing a HomePage
SetVersioned(false) does not help with new page instances being created. -Matej On Thu, Jan 7, 2010 at 9:46 PM, Wilhelmsen Tor Iver toriv...@arrive.no wrote: about unversioned, i have just done a quick test on wicket-examples helloworld, adding serialVersionUID (not informed in the examples) and the result is the same: pagestore file increasing to the infinite (max size of course :) I meant Wicket's setVersioned(false); the serialVersionUID is just for binary serialization, as long as the fields do not change the computed value the VM generates for you should be the same. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
