You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Laura G <fo...@yahoo.com> on 2009/07/23 21:34:45 UTC
jboss 5, jdk 1.6, and wicket 1.3 disk space problem
Hi Everyone,
I'm evaluating wicket for a new project for my company. I started looking at the wicket-examples and dropped the wicket-examples-1.3.6.war into the jboss deploy directory. It deployed fine and I went through some of the examples.
My problem is that I left jboss running, and the next day came back and noticed restarting jboss took a really long time.
It turns out my /home partition (where jboss is running) was 95% full.
Clearing out the jboss tmp dir brought /home down to 9%. The jboss tmp I'm referring to is here:
/home/laura/jboss-5.0.0.GA/server/default/tmp/
I thought that the problem might be in one the examples, so I removed wicket-examples-1.3.6.war. I've been working on a simple example of my own using the markup inheritance example and the input form examples. I was planning on putting a page demo-ing the ajax functionality too.
So I've been playing around with this example and hot-deploying the war to jboss all day and I've noticed my /home has crept up to 45%.
Has anyone else had this problem? We have a lot of other web apps on jboss 5, but never had this problem before (none are based on wicket). Here's my exact details:
jboss-5.0.0.GA
jdk1.6.0_13
wicket 1.3.6
ubuntu 8.04, Hardy Heron
Thanks,
Laura
Re: jboss 5, jdk 1.6, and wicket 1.3 disk space problem
Posted by Jeremy Thomerson <je...@wickettraining.com>.
Google vfs-nested.tmp - returns what looks like some valid results for you.
http://www.google.com/search?q=vfs-nested.tmp
http://ourcraft.wordpress.com/2009/01/05/plague-of-jar-files/
--
Jeremy Thomerson
http://www.wickettraining.com
On Thu, Jul 23, 2009 at 2:51 PM, Laura G<fo...@yahoo.com> wrote:
> Inside the /tmp directory is another directory called vfs-nested.tmp.
>
> Inside that is a ton of jars. It looks like it's copying them over and over:
>
> 000209d4_wicket-extensions-1.3.6.jar
> 0008ddb0_wicket-datetime-1.3.6.jar
> 000f9baa_wicket-guice-1.3.6.jar
> 001782a9_wicket-extensions-1.3.6.jar
> 00189e19_velocity-dep-1.4.jar
> 001dac17_wicket-jmx-1.3.6.jar
> 0023cb17_wicket-auth-roles-1.3.6.jar
> 00256edd_wicket-ioc-1.3.6.jar
> 0025828e_wicket-jmx-1.3.6.jar
> 00289db1_wicket-jmx-1.3.6.jar
>
> --- On Thu, 7/23/09, Igor Vaynberg <ig...@gmail.com> wrote:
>
> From: Igor Vaynberg <ig...@gmail.com>
> Subject: Re: jboss 5, jdk 1.6, and wicket 1.3 disk space problem
> To: users@wicket.apache.org
> Date: Thursday, July 23, 2009, 2:41 PM
>
> what are the files/dirs created in that tmp dir?
>
> -igor
>
> On Thu, Jul 23, 2009 at 12:34 PM, Laura G<fo...@yahoo.com> wrote:
>> Hi Everyone,
>>
>> I'm evaluating wicket for a new project for my company. I started looking at the wicket-examples and dropped the wicket-examples-1.3.6.war into the jboss deploy directory. It deployed fine and I went through some of the examples.
>>
>> My problem is that I left jboss running, and the next day came back and noticed restarting jboss took a really long time.
>>
>> It turns out my /home partition (where jboss is running) was 95% full.
>>
>> Clearing out the jboss tmp dir brought /home down to 9%. The jboss tmp I'm referring to is here:
>>
>> /home/laura/jboss-5.0.0.GA/server/default/tmp/
>>
>> I thought that the problem might be in one the examples, so I removed wicket-examples-1.3.6.war. I've been working on a simple example of my own using the markup inheritance example and the input form examples. I was planning on putting a page demo-ing the ajax functionality too.
>>
>> So I've been playing around with this example and hot-deploying the war to jboss all day and I've noticed my /home has crept up to 45%.
>>
>> Has anyone else had this problem? We have a lot of other web apps on jboss 5, but never had this problem before (none are based on wicket). Here's my exact details:
>>
>> jboss-5.0.0.GA
>> jdk1.6.0_13
>> wicket 1.3.6
>> ubuntu 8.04, Hardy Heron
>>
>> Thanks,
>> Laura
>>
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jboss 5, jdk 1.6, and wicket 1.3 disk space problem
Posted by Laura G <fo...@yahoo.com>.
Inside the /tmp directory is another directory called vfs-nested.tmp.
Inside that is a ton of jars. It looks like it's copying them over and over:
000209d4_wicket-extensions-1.3.6.jar
0008ddb0_wicket-datetime-1.3.6.jar
000f9baa_wicket-guice-1.3.6.jar
001782a9_wicket-extensions-1.3.6.jar
00189e19_velocity-dep-1.4.jar
001dac17_wicket-jmx-1.3.6.jar
0023cb17_wicket-auth-roles-1.3.6.jar
00256edd_wicket-ioc-1.3.6.jar
0025828e_wicket-jmx-1.3.6.jar
00289db1_wicket-jmx-1.3.6.jar
--- On Thu, 7/23/09, Igor Vaynberg <ig...@gmail.com> wrote:
From: Igor Vaynberg <ig...@gmail.com>
Subject: Re: jboss 5, jdk 1.6, and wicket 1.3 disk space problem
To: users@wicket.apache.org
Date: Thursday, July 23, 2009, 2:41 PM
what are the files/dirs created in that tmp dir?
-igor
On Thu, Jul 23, 2009 at 12:34 PM, Laura G<fo...@yahoo.com> wrote:
> Hi Everyone,
>
> I'm evaluating wicket for a new project for my company. I started looking at the wicket-examples and dropped the wicket-examples-1.3.6.war into the jboss deploy directory. It deployed fine and I went through some of the examples.
>
> My problem is that I left jboss running, and the next day came back and noticed restarting jboss took a really long time.
>
> It turns out my /home partition (where jboss is running) was 95% full.
>
> Clearing out the jboss tmp dir brought /home down to 9%. The jboss tmp I'm referring to is here:
>
> /home/laura/jboss-5.0.0.GA/server/default/tmp/
>
> I thought that the problem might be in one the examples, so I removed wicket-examples-1.3.6.war. I've been working on a simple example of my own using the markup inheritance example and the input form examples. I was planning on putting a page demo-ing the ajax functionality too.
>
> So I've been playing around with this example and hot-deploying the war to jboss all day and I've noticed my /home has crept up to 45%.
>
> Has anyone else had this problem? We have a lot of other web apps on jboss 5, but never had this problem before (none are based on wicket). Here's my exact details:
>
> jboss-5.0.0.GA
> jdk1.6.0_13
> wicket 1.3.6
> ubuntu 8.04, Hardy Heron
>
> Thanks,
> Laura
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jboss 5, jdk 1.6, and wicket 1.3 disk space problem
Posted by Igor Vaynberg <ig...@gmail.com>.
what are the files/dirs created in that tmp dir?
-igor
On Thu, Jul 23, 2009 at 12:34 PM, Laura G<fo...@yahoo.com> wrote:
> Hi Everyone,
>
> I'm evaluating wicket for a new project for my company. I started looking at the wicket-examples and dropped the wicket-examples-1.3.6.war into the jboss deploy directory. It deployed fine and I went through some of the examples.
>
> My problem is that I left jboss running, and the next day came back and noticed restarting jboss took a really long time.
>
> It turns out my /home partition (where jboss is running) was 95% full.
>
> Clearing out the jboss tmp dir brought /home down to 9%. The jboss tmp I'm referring to is here:
>
> /home/laura/jboss-5.0.0.GA/server/default/tmp/
>
> I thought that the problem might be in one the examples, so I removed wicket-examples-1.3.6.war. I've been working on a simple example of my own using the markup inheritance example and the input form examples. I was planning on putting a page demo-ing the ajax functionality too.
>
> So I've been playing around with this example and hot-deploying the war to jboss all day and I've noticed my /home has crept up to 45%.
>
> Has anyone else had this problem? We have a lot of other web apps on jboss 5, but never had this problem before (none are based on wicket). Here's my exact details:
>
> jboss-5.0.0.GA
> jdk1.6.0_13
> wicket 1.3.6
> ubuntu 8.04, Hardy Heron
>
> Thanks,
> Laura
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Questions about Wicket sessions
Posted by "Ames, Tim" <Ti...@ProMedica.org>.
Question #2 can be muddy depending on how the new window was launched.
In my experience (Using IE 6) if you click on a link (i.e target="_blank") that launches an application and log in, then go back and click that link again to open a new window to the same application, you will be using the same wicket session - and http-session.
In the above scenerio, multi-window support does not work. If you were to launch a new window or new tab from the WICKET app browser itself, then multi-window does work and you get different sessions.
So, a link opening a new window i.e. target="_blank" and physically opening a new window using the browser can get different results.
-----Original Message-----
From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
Sent: Sunday, July 26, 2009 2:50 PM
To: users@wicket.apache.org
Subject: Re: Questions about Wicket sessions
On Sun, Jul 26, 2009 at 8:53 AM, David Chang<da...@yahoo.com> wrote:
> 1. If I open another tab on the same browser (IE or FF), visitor activities on the same Wicket app are considered in the same session?
same session, this is why we provide browser auto-multiwindow support, so we can detect a new tab/window being open and the app still works fine.
> 2. If I start IE or FF in another window, visitor activities on the same Wicket app are considered in the same or different session?
always a different sessions, browsers do not share sessions.
> 3. If dirty() is called within a method of custom session object, then it is the developer's responsibility to implement dirty() to synchronize with other clustered web servers, correct?
no, your responsibility is only to call dirty() when you change your custom state in session. the servlet container will take care of replicating session across the cluster.
-igor
>
> Thanks!
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
EMAIL CONFIDENTIALITY NOTICE
This Email message, and any attachments, may contain confidential
patient health information that is legally protected. This information
is intended only for the use of the individual or entity named above.
The authorized recipient of this information is prohibited from disclosing
this information to any other party unless required to do so by law
or regulation and is required to destroy the information after its stated
need has been fulfilled. If you are not the intended recipient, you are
hereby notified that any disclosure, copying, distribution, or action
taken in reliance on the contents of this message is strictly prohibited.
If you have received this information in error, please notify
the sender immediately by replying to this message and delete the
message from your system.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Questions about Wicket sessions
Posted by morbo <ri...@gmail.com>.
Sorry for jumping into this issue again, but I am still a bit confused. I
need a definitive answer for this as I have to document it in my diploma
thesis.
In my app I have a requirement that a new page has to be opened in a popup
window, which is pretty easy with wicket using the popupsettings object and
bookmarkable pages. I made a tiny test app and implemented this scenario but
have problems to access the former user session from the newly opened page.
It seems that a new session is generated.
So I am using the same browser but a new window/instance of it. So is there
a way to access the wicket session where this window was opened from?
Considering the above answers I think there is no way, right? If I am right
this problem is not a problem of wicket (architecture) but of (modern)
browsers implementing it this way, right?
Regards,
richard
Erik van Oosten wrote:
>
>
> Igor Vaynberg wrote:
>>> 2. If I start IE or FF in another window, visitor activities on the same
>>> Wicket app are considered in the same or different session?
>>>
>>
>> always a different sessions, browsers do not share sessions.
>>
> I think it depends on what David meant by 'another window'. I assumed it
> to be the 'open in new window' function. Then you still have the same
> browser, but another window.
>
> Regards.
> Erik.
>
>
> --
> Erik van Oosten
> http://day-to-day-stuff.blogspot.com/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
View this message in context: http://old.nabble.com/jboss-5%2C-jdk-1.6%2C-and-wicket-1.3-disk-space-problem-tp24633011p27173781.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Questions about Wicket sessions
Posted by Erik van Oosten <e....@grons.nl>.
Igor Vaynberg wrote:
>> 2. If I start IE or FF in another window, visitor activities on the same Wicket app are considered in the same or different session?
>>
>
> always a different sessions, browsers do not share sessions.
>
I think it depends on what David meant by 'another window'. I assumed it
to be the 'open in new window' function. Then you still have the same
browser, but another window.
Regards.
Erik.
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Questions about Wicket sessions
Posted by Igor Vaynberg <ig...@gmail.com>.
On Sun, Jul 26, 2009 at 8:53 AM, David Chang<da...@yahoo.com> wrote:
> 1. If I open another tab on the same browser (IE or FF), visitor activities on the same Wicket app are considered in the same session?
same session, this is why we provide browser auto-multiwindow support,
so we can detect a new tab/window being open and the app still works
fine.
> 2. If I start IE or FF in another window, visitor activities on the same Wicket app are considered in the same or different session?
always a different sessions, browsers do not share sessions.
> 3. If dirty() is called within a method of custom session object, then it is the developer's responsibility to implement dirty() to synchronize with other clustered web servers, correct?
no, your responsibility is only to call dirty() when you change your
custom state in session. the servlet container will take care of
replicating session across the cluster.
-igor
>
> Thanks!
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Questions about Wicket sessions
Posted by Martijn Dashorst <ma...@gmail.com>.
Not only multiple tabs, but also resources can access the session, and
will attach and detach the session during request processing. So
session.onAttach() can be called twice before session.onDetach() is
called.
Martijn
On Sun, Jul 26, 2009 at 10:23 PM, Igor Vaynberg<ig...@gmail.com> wrote:
> no, incorrect. multiple browser tabs can be used to access the same
> session instance simultaneously.
>
> -igor
>
> On Sun, Jul 26, 2009 at 1:17 PM, David Chang<da...@yahoo.com> wrote:
>>
>>
>> Erik, thanks for your input.
>>
>>> Please note "Sessions are not thread-safe" in Wicket
>>> context means that the Session /object/ is not thread-safe.
>>> Note that requests that fall within a session (except for
>>> resources) are handled serially. Only when you use session
>>> clustering this guarantee can not be made.
>>
>> So if I dont use clustered web servers, custom methods on a custom session object do not need be "synchronized". Put it another way, Wicket session is thread-safe in case of a single web server. Correct?
>>
>> Cheers.
>>
>>
>> --- On Sun, 7/26/09, Erik van Oosten <e....@grons.nl> wrote:
>>
>>> From: Erik van Oosten <e....@grons.nl>
>>> Subject: Re: Questions about Wicket sessions
>>> To: users@wicket.apache.org
>>> Date: Sunday, July 26, 2009, 2:08 PM
>>> David,
>>>
>>> Please note "Sessions are not thread-safe" in Wicket
>>> context means that the Session /object/ is not thread-safe.
>>> Note that requests that fall within a session (except for
>>> resources) are handled serially. Only when you use session
>>> clustering this guarantee can not be made.
>>>
>>> 1. It depends on the browser. All modern browsers will make
>>> it one session.
>>>
>>> 2. Same answer.
>>>
>>> 3. No. Wicket does this for you.
>>>
>>> Regarding your question on session storage: you'll be hard
>>> pressed to find a more performant solution to Wicket's http
>>> session disk store. Perhaps that memory solutions would work
>>> better.
>>>
>>> Regards,
>>> Erik.
>>>
>>>
>>> David Chang wrote:
>>> > Reading <<Wicket in Action>> to learn
>>> Wicket, I understand that sessions are not thread-safe. I
>>> have the following questions about a Wicket app:
>>> >
>>> > 1. If I open another tab on the same browser (IE or
>>> FF), visitor activities on the same Wicket app are
>>> considered in the same session?
>>> >
>>> > 2. If I start IE or FF in another window, visitor
>>> activities on the same Wicket app are considered in the same
>>> or different session?
>>> >
>>> > 3. If dirty() is called within a method of custom
>>> session object, then it is the developer's responsibility to
>>> implement dirty() to synchronize with other clustered web
>>> servers, correct?
>>> >
>>> > Thanks!
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Questions about Wicket sessions
Posted by David Chang <da...@yahoo.com>.
Igor, thank you for the correction. Really appreciated. Thanks!
--- On Sun, 7/26/09, Igor Vaynberg <ig...@gmail.com> wrote:
> From: Igor Vaynberg <ig...@gmail.com>
> Subject: Re: Questions about Wicket sessions
> To: users@wicket.apache.org
> Date: Sunday, July 26, 2009, 4:23 PM
> no, incorrect. multiple browser tabs
> can be used to access the same
> session instance simultaneously.
>
> -igor
>
> On Sun, Jul 26, 2009 at 1:17 PM, David Chang<da...@yahoo.com>
> wrote:
> >
> >
> > Erik, thanks for your input.
> >
> >> Please note "Sessions are not thread-safe" in
> Wicket
> >> context means that the Session /object/ is not
> thread-safe.
> >> Note that requests that fall within a session
> (except for
> >> resources) are handled serially. Only when you use
> session
> >> clustering this guarantee can not be made.
> >
> > So if I dont use clustered web servers, custom methods
> on a custom session object do not need be "synchronized".
> Put it another way, Wicket session is thread-safe in case of
> a single web server. Correct?
> >
> > Cheers.
> >
> >
> > --- On Sun, 7/26/09, Erik van Oosten <e....@grons.nl>
> wrote:
> >
> >> From: Erik van Oosten <e....@grons.nl>
> >> Subject: Re: Questions about Wicket sessions
> >> To: users@wicket.apache.org
> >> Date: Sunday, July 26, 2009, 2:08 PM
> >> David,
> >>
> >> Please note "Sessions are not thread-safe" in
> Wicket
> >> context means that the Session /object/ is not
> thread-safe.
> >> Note that requests that fall within a session
> (except for
> >> resources) are handled serially. Only when you use
> session
> >> clustering this guarantee can not be made.
> >>
> >> 1. It depends on the browser. All modern browsers
> will make
> >> it one session.
> >>
> >> 2. Same answer.
> >>
> >> 3. No. Wicket does this for you.
> >>
> >> Regarding your question on session storage: you'll
> be hard
> >> pressed to find a more performant solution to
> Wicket's http
> >> session disk store. Perhaps that memory solutions
> would work
> >> better.
> >>
> >> Regards,
> >> Erik.
> >>
> >>
> >> David Chang wrote:
> >> > Reading <<Wicket in Action>> to
> learn
> >> Wicket, I understand that sessions are not
> thread-safe. I
> >> have the following questions about a Wicket app:
> >> >
> >> > 1. If I open another tab on the same browser
> (IE or
> >> FF), visitor activities on the same Wicket app
> are
> >> considered in the same session?
> >> >
> >> > 2. If I start IE or FF in another window,
> visitor
> >> activities on the same Wicket app are considered
> in the same
> >> or different session?
> >> >
> >> > 3. If dirty() is called within a method of
> custom
> >> session object, then it is the developer's
> responsibility to
> >> implement dirty() to synchronize with other
> clustered web
> >> servers, correct?
> >> >
> >> > Thanks!
> >> >
> >> >
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Questions about Wicket sessions
Posted by Igor Vaynberg <ig...@gmail.com>.
no, incorrect. multiple browser tabs can be used to access the same
session instance simultaneously.
-igor
On Sun, Jul 26, 2009 at 1:17 PM, David Chang<da...@yahoo.com> wrote:
>
>
> Erik, thanks for your input.
>
>> Please note "Sessions are not thread-safe" in Wicket
>> context means that the Session /object/ is not thread-safe.
>> Note that requests that fall within a session (except for
>> resources) are handled serially. Only when you use session
>> clustering this guarantee can not be made.
>
> So if I dont use clustered web servers, custom methods on a custom session object do not need be "synchronized". Put it another way, Wicket session is thread-safe in case of a single web server. Correct?
>
> Cheers.
>
>
> --- On Sun, 7/26/09, Erik van Oosten <e....@grons.nl> wrote:
>
>> From: Erik van Oosten <e....@grons.nl>
>> Subject: Re: Questions about Wicket sessions
>> To: users@wicket.apache.org
>> Date: Sunday, July 26, 2009, 2:08 PM
>> David,
>>
>> Please note "Sessions are not thread-safe" in Wicket
>> context means that the Session /object/ is not thread-safe.
>> Note that requests that fall within a session (except for
>> resources) are handled serially. Only when you use session
>> clustering this guarantee can not be made.
>>
>> 1. It depends on the browser. All modern browsers will make
>> it one session.
>>
>> 2. Same answer.
>>
>> 3. No. Wicket does this for you.
>>
>> Regarding your question on session storage: you'll be hard
>> pressed to find a more performant solution to Wicket's http
>> session disk store. Perhaps that memory solutions would work
>> better.
>>
>> Regards,
>> Erik.
>>
>>
>> David Chang wrote:
>> > Reading <<Wicket in Action>> to learn
>> Wicket, I understand that sessions are not thread-safe. I
>> have the following questions about a Wicket app:
>> >
>> > 1. If I open another tab on the same browser (IE or
>> FF), visitor activities on the same Wicket app are
>> considered in the same session?
>> >
>> > 2. If I start IE or FF in another window, visitor
>> activities on the same Wicket app are considered in the same
>> or different session?
>> >
>> > 3. If dirty() is called within a method of custom
>> session object, then it is the developer's responsibility to
>> implement dirty() to synchronize with other clustered web
>> servers, correct?
>> >
>> > Thanks!
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Questions about Wicket sessions
Posted by David Chang <da...@yahoo.com>.
Erik, thanks for your input.
> Please note "Sessions are not thread-safe" in Wicket
> context means that the Session /object/ is not thread-safe.
> Note that requests that fall within a session (except for
> resources) are handled serially. Only when you use session
> clustering this guarantee can not be made.
So if I dont use clustered web servers, custom methods on a custom session object do not need be "synchronized". Put it another way, Wicket session is thread-safe in case of a single web server. Correct?
Cheers.
--- On Sun, 7/26/09, Erik van Oosten <e....@grons.nl> wrote:
> From: Erik van Oosten <e....@grons.nl>
> Subject: Re: Questions about Wicket sessions
> To: users@wicket.apache.org
> Date: Sunday, July 26, 2009, 2:08 PM
> David,
>
> Please note "Sessions are not thread-safe" in Wicket
> context means that the Session /object/ is not thread-safe.
> Note that requests that fall within a session (except for
> resources) are handled serially. Only when you use session
> clustering this guarantee can not be made.
>
> 1. It depends on the browser. All modern browsers will make
> it one session.
>
> 2. Same answer.
>
> 3. No. Wicket does this for you.
>
> Regarding your question on session storage: you'll be hard
> pressed to find a more performant solution to Wicket's http
> session disk store. Perhaps that memory solutions would work
> better.
>
> Regards,
> Erik.
>
>
> David Chang wrote:
> > Reading <<Wicket in Action>> to learn
> Wicket, I understand that sessions are not thread-safe. I
> have the following questions about a Wicket app:
> >
> > 1. If I open another tab on the same browser (IE or
> FF), visitor activities on the same Wicket app are
> considered in the same session?
> >
> > 2. If I start IE or FF in another window, visitor
> activities on the same Wicket app are considered in the same
> or different session?
> >
> > 3. If dirty() is called within a method of custom
> session object, then it is the developer's responsibility to
> implement dirty() to synchronize with other clustered web
> servers, correct?
> >
> > Thanks!
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Questions about Wicket sessions
Posted by Erik van Oosten <e....@grons.nl>.
David,
Please note "Sessions are not thread-safe" in Wicket context means that
the Session /object/ is not thread-safe. Note that requests that fall
within a session (except for resources) are handled serially. Only when
you use session clustering this guarantee can not be made.
1. It depends on the browser. All modern browsers will make it one session.
2. Same answer.
3. No. Wicket does this for you.
Regarding your question on session storage: you'll be hard pressed to
find a more performant solution to Wicket's http session disk store.
Perhaps that memory solutions would work better.
Regards,
Erik.
David Chang wrote:
> Reading <<Wicket in Action>> to learn Wicket, I understand that sessions are not thread-safe. I have the following questions about a Wicket app:
>
> 1. If I open another tab on the same browser (IE or FF), visitor activities on the same Wicket app are considered in the same session?
>
> 2. If I start IE or FF in another window, visitor activities on the same Wicket app are considered in the same or different session?
>
> 3. If dirty() is called within a method of custom session object, then it is the developer's responsibility to implement dirty() to synchronize with other clustered web servers, correct?
>
> Thanks!
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Questions about Wicket sessions
Posted by David Chang <da...@yahoo.com>.
Another question:
By default, Wicket's SessionStore stores older pages to a temporary directory. It is stored as files, correct? In case of a large website demanding high performance, it should be stored in a high-performance database, correct?
Thanks!
--- On Sun, 7/26/09, David Chang <da...@yahoo.com> wrote:
> From: David Chang <da...@yahoo.com>
> Subject: Questions about Wicket sessions
> To: users@wicket.apache.org
> Date: Sunday, July 26, 2009, 11:53 AM
>
>
>
> Reading <<Wicket in Action>> to learn Wicket, I
> understand that sessions are not thread-safe. I have the
> following questions about a Wicket app:
>
> 1. If I open another tab on the same browser (IE or FF),
> visitor activities on the same Wicket app are considered in
> the same session?
>
> 2. If I start IE or FF in another window, visitor
> activities on the same Wicket app are considered in the same
> or different session?
>
> 3. If dirty() is called within a method of custom session
> object, then it is the developer's responsibility to
> implement dirty() to synchronize with other clustered web
> servers, correct?
>
> Thanks!
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Questions about Wicket sessions
Posted by David Chang <da...@yahoo.com>.
Reading <<Wicket in Action>> to learn Wicket, I understand that sessions are not thread-safe. I have the following questions about a Wicket app:
1. If I open another tab on the same browser (IE or FF), visitor activities on the same Wicket app are considered in the same session?
2. If I start IE or FF in another window, visitor activities on the same Wicket app are considered in the same or different session?
3. If dirty() is called within a method of custom session object, then it is the developer's responsibility to implement dirty() to synchronize with other clustered web servers, correct?
Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org