Yes, but in my example, I was referring to how 2 different apps with
different cookies are both running on localhost with different ports. I get
this issue all the time on chromium when I test multiple apps all on
location with different ports. I keep having to login whenever I refresh a
different
-Original Message-
From: Paul Bors [mailto:p...@bors.ws]
Sent: Friday, September 27, 2013 5:51 PM
To: users@wicket.apache.org
Cc: d...@wicket.apache.org
Subject: RE: Bunch of Page Expired exceptions in Wicket 6.10.0
(GlassFish
v3 and v4)
I tested with the proposed
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0 (GlassFish
v3 and v4)
I think both suggestions should be applied.
The intentions are more clear, IMO.
But let's wait Paul to explain what problem he faced. I don't expect
problems with session timeouts because this is managed by the web
, September 28, 2013 3:44 AM
To: users@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
(GlassFish v3 and v4)
I think both suggestions should be applied.
The intentions are more clear, IMO.
But let's wait Paul to explain what problem he faced. I don't expect
problems
,
Paul Bors
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Saturday, September 28, 2013 3:44 AM
To: users@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
(GlassFish v3 and v4)
I think both suggestions should be applied
@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
(GlassFish v3 and v4)
I think both suggestions should be applied.
The intentions are more clear, IMO.
But let's wait Paul to explain what problem he faced. I don't expect
problems with session timeouts because
...@apache.org]
Sent: Saturday, September 28, 2013 3:44 AM
To: users@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
(GlassFish v3 and v4)
I think both suggestions should be applied.
The intentions are more clear, IMO.
But let's wait Paul to explain what
implementation breaks the session timeout.
~ Thank you,
Paul Bors
-Original Message-
From: Paul Bors [mailto:p...@bors.ws]
Sent: Friday, September 27, 2013 5:51 PM
To: users@wicket.apache.org
Cc: d...@wicket.apache.org
Subject: RE: Bunch of Page Expired exceptions in Wicket 6.10.0 (GlassFish v3
: Friday, September 27, 2013 5:51 PM
To: users@wicket.apache.org
Cc: d...@wicket.apache.org
Subject: RE: Bunch of Page Expired exceptions in Wicket 6.10.0 (GlassFish
v3 and v4)
I tested with the proposed o.a.w.p.PageStoreManager.**
PersistentRequestAdapter#**getSessionEntry() new implementation
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Saturday, September 28, 2013 3:44 AM
To: users@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0 (GlassFish v3
and v4)
I think both suggestions should be applied.
The intentions are more
by tabs do you mean browser tabs?
if you have 2 tabs:
http://localhost:8080/Foo
and
http://localhost:8081/Bar
then reloading each tab will often invalidate the previous tab. the session
cookie is overwritten.
--
View this message in context:
On Fri, Sep 27, 2013 at 8:20 AM, miguel mig...@thedeanda.com wrote:
by tabs do you mean browser tabs?
if you have 2 tabs:
http://localhost:8080/Foo
and
http://localhost:8081/Bar
then reloading each tab will often invalidate the previous tab. the session
cookie is overwritten.
This
-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Thursday, September 26, 2013 5:01 PM
To: users@wicket.apache.org
Cc: Sven Meier
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
The problem seems to be caused by
http://issues.apache.org/jira/browse/WICKET-5164
With this change
,
Paul Bors
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Thursday, September 26, 2013 5:01 PM
To: users@wicket.apache.org
Cc: Sven Meier
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
The problem seems to be caused by
http
: Bunch of Page Expired exceptions in Wicket 6.10.0
The problem seems to be caused by
http://issues.apache.org/jira/**browse/WICKET-5164http://issues.apache.org/jira/browse/WICKET-5164
With this change any kind of attribute added to the http session causes
total removal of all data from the disk store
: Sven Meier
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
The problem seems to be caused by
http://issues.apache.org/jira/browse/WICKET-5164http://issues.apache.org/jira/**browse/WICKET-5164
http://**issues.apache.org/jira/browse/**WICKET-5164http://issues.apache.org/jira
of Page Expired exceptions in Wicket 6.10.0
by tabs do you mean browser tabs?
if you have 2 tabs:
http://localhost:8080/Foo
and
http://localhost:8081/Bar
then reloading each tab will often invalidate the previous tab. the session
cookie is overwritten.
--
View this message in context:
http
Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Friday, September 27, 2013 10:09 AM
To: users@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
I created a simple app and tested it on these 3 servers + Jetty 8.1.13.
The app shows that SessionEntry
,
but that'll really be a nice to have at this point.
~ Thank you,
Paul Bors
-Original Message-
From: Paul Bors [mailto:p...@bors.ws]
Sent: Friday, September 27, 2013 11:04 AM
To: users@wicket.apache.org
Subject: RE: Bunch of Page Expired exceptions in Wicket 6.10.0
I so knew it! It also affects
Created https://java.net/jira/browse/GLASSFISH-20828
HttpSessionBindingListener.valueUnbound() is always called right after
valueBound() with a null HttpSessionBindingEvent.getValue()
Let's see what becomes of this...
-
~ Thank you,
p...@bors.ws
--
View this message in context:
Reading your ticket against GF I think GF behaves correctly. But I wonder
why Tomcat/Jetty don't do this.
So here is what happens:
org.apache.wicket.page.PageStoreManager.PersistentRequestAdapter#getSessionEntry
looks like :
private SessionEntry getSessionEntry(boolean create)
{
SessionEntry
HttpSessionListener instead is
cleaner.
~ Thank you,
Paul Bors
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Friday, September 27, 2013 4:09 PM
To: users@wicket.apache.org
Cc: d...@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
of Page Expired exceptions in Wicket 6.10.0 (GlassFish v3
and v4)
Reading your ticket against GF I think GF behaves correctly. But I wonder why
Tomcat/Jetty don't do this.
So here is what happens:
org.apache.wicket.page.PageStoreManager.PersistentRequestAdapter#getSessionEntry
looks like :
private
Hi,
DEBUG: 09/25 17:35:40.956: PageAccessSynchronizer: http-thread-pool-5311(4)
acquired lock to page 53
DEBUG: 09/25 17:35:40.957: DiskDataStore: Removing data for pages in session
with id '702b17085b39e8a599d07e81df51'
DEBUG: 09/25 17:35:40.960: DiskDataStore: Returning data(null) for page
, September 26, 2013 3:13 AM
To: users@wicket.apache.org
Cc: Paul Bors
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
Hi,
DEBUG: 09/25 17:35:40.956: PageAccessSynchronizer: http-thread-pool-5311(4)
acquired lock to page 53
DEBUG: 09/25 17:35:40.957: DiskDataStore: Removing data
advise.
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Thursday, September 26, 2013 3:13 AM
To: users@wicket.apache.org
Cc: Paul Bors
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
Hi,
DEBUG: 09/25 17:35:40.956: PageAccessSynchronizer: http-thread-pool-5311(4
:)
~ Thank you,
Paul Bors
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Thursday, September 26, 2013 5:01 PM
To: users@wicket.apache.org
Cc: Sven Meier
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
The problem seems to be caused by
http
Hey guys,
Just wondering what could be the cause of the many page expired exceptions I
am running into with this webapp whenever the user changes tabs and then
selects the browser's Back button or whenever the user downloads a
resource via a button and the form is being submitted a second
I think I found my answer here:
https://cwiki.apache.org/confluence/display/WICKET/Page+Storage
I'll grab the Wicket sources tomorrow and hook my IntelliJ IDEA debugger to the
DiskDataStore and work it backwards to see what happens.
Stay tuned... ;)
Have a great day,
Paul Bors
On Sep 25,
29 matches
Mail list logo