You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by rivkash1 <ri...@nite.org.il> on 2008/09/02 09:53:52 UTC
PageExpiredException on production
hello all,
We are working with Wicket (1.3.4) on production for a couple of months. It
runs within jetty 6.1.7.
For some weeks, we are experiencing a strange PageExpiredException which
happens only on production env.
It mostly happens on 2 main Pages in which the users submit the same form in
a rolling manner (i.e. fill the form fields, submit the form, the user is
redirected to the same page with a clean form and fills the form with new
data and so on repeatedly).
It isn't a problem of session expiration because our session timeout is set
to 10 hours, this is the setting in our web.xml file:
<session-config>
<session-timeout>600</session-timeout>
</session-config>
We changed the logging level of Wicket to DEBUG, I'm attaching only a little
fraction from our log file,
you can see the whole exception in the file attached to this post:
This message is printed in level of warning, yet it is just for tracing:
invoked resolve! RequestParameters:
[RequestParameters componentPath=4:registrationManagementForm
pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
iorListener componentId=null behaviorId=1 urlDepth=-1
parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
} onlyProcessIfPathActive=false]
-----------------------------------------------------
2008-09-01 15:18:47,372 [WARN ]
security.authentication.NiteWebRequestCycleProcessor -
===================== ENTER ==========
======================
This message is printed in level of warning, yet it is just for tracing:
invoked resolveRenderedPage! RequestParameters:
[RequestParameters componentPath=4:registrationManagementForm
pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
iorListener componentId=null behaviorId=1 urlDepth=-1
parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
} onlyProcessIfPathActive=false]
-----------------------------------------------------
2008-09-01 15:18:47,372 [DEBUG] apache.wicket.Session - Getting page [path
= 4:registrationManagementForm, versionNumber = 0]
2008-09-01 15:18:47,376 [WARN ]
security.authentication.NiteWebRequestCycleProcessor -
-----------------------------------------------------
completed resolveRenderedPage!======================== EXIT
=============================
2008-09-01 15:18:47,377 [WARN ]
security.authentication.NiteWebRequestCycleProcessor -
===================== ENTER ==========
======================
This message is printed in level of warning, yet it is just for tracing:
invoked respond(RuntimeException e, RequestCycle requestCycle)!
-----------------------------------------------------
2008-09-01 15:18:47,377 [WARN ]
security.authentication.NiteWebRequestCycleProcessor -
===================== ENTER ==========
======================
This message is printed in level of warning, yet it is just for tracing:
invoked onRuntimeException!
-----------------------------------------------------
2008-09-01 15:18:47,377 [ERROR]
security.authentication.NiteWebRequestCycleProcessor - onRuntimeException
stack:
org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
rendered page in session [pagemap=null,componentPath=4:r
egistrationManagementForm,versionNumber=0]
at
org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:181)
at
il.org.nite.frm.security.authentication.NiteWebRequestCycleProcessor.resolve
http://www.nabble.com/file/p19265678/prod_log.txt prod_log.txt
--
View this message in context: http://www.nabble.com/PageExpiredException-on-production-tp19265678p19265678.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: PageExpiredException on production
Posted by rivkash1 <ri...@nite.org.il>.
Hi.
we added this line:
getPageSettings().setAutomaticMultiWindowSupport(true);
to our web application class.
In our case the problem occurred when the user worked on 2 firefox tabs
simultaneously, So the above line solved the problem.
Rivka
nico.ptrs wrote:
>
> Have you had any progress with this problem? I'm experiencing exactly the
> same...
>
> Thanks
>
>
>
> rivkash1 wrote:
>>
>> hello all,
>>
>> We are working with Wicket (1.3.4) on production for a couple of months.
>> It runs within jetty 6.1.7.
>> For some weeks, we are experiencing a strange PageExpiredException which
>> happens only on production env.
>>
>> It mostly happens on 2 main Pages in which the users submit the same form
>> in a rolling manner (i.e. fill the form fields, submit the form, the user
>> is redirected to the same page with a clean form and fills the form with
>> new data and so on repeatedly).
>>
>> It isn't a problem of session expiration because our session timeout is
>> set to 10 hours, this is the setting in our web.xml file:
>>
>> <session-config>
>> <session-timeout>600</session-timeout>
>> </session-config>
>>
>> We changed the logging level of Wicket to DEBUG, I'm attaching only a
>> little fraction from our log file,
>> you can see the whole exception in the file attached to this post:
>>
>> This message is printed in level of warning, yet it is just for tracing:
>> invoked resolve! RequestParameters:
>> [RequestParameters componentPath=4:registrationManagementForm
>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>> iorListener componentId=null behaviorId=1 urlDepth=-1
>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>> } onlyProcessIfPathActive=false]
>> -----------------------------------------------------
>>
>> 2008-09-01 15:18:47,372 [WARN ]
>> security.authentication.NiteWebRequestCycleProcessor -
>> ===================== ENTER ==========
>> ======================
>> This message is printed in level of warning, yet it is just for tracing:
>> invoked resolveRenderedPage! RequestParameters:
>> [RequestParameters componentPath=4:registrationManagementForm
>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>> iorListener componentId=null behaviorId=1 urlDepth=-1
>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>> } onlyProcessIfPathActive=false]
>> -----------------------------------------------------
>>
>> 2008-09-01 15:18:47,372 [DEBUG] apache.wicket.Session - Getting page
>> [path = 4:registrationManagementForm, versionNumber = 0]
>> 2008-09-01 15:18:47,376 [WARN ]
>> security.authentication.NiteWebRequestCycleProcessor -
>> -----------------------------------------------------
>> completed resolveRenderedPage!======================== EXIT
>> =============================
>> 2008-09-01 15:18:47,377 [WARN ]
>> security.authentication.NiteWebRequestCycleProcessor -
>> ===================== ENTER ==========
>> ======================
>> This message is printed in level of warning, yet it is just for tracing:
>> invoked respond(RuntimeException e, RequestCycle requestCycle)!
>> -----------------------------------------------------
>>
>> 2008-09-01 15:18:47,377 [WARN ]
>> security.authentication.NiteWebRequestCycleProcessor -
>> ===================== ENTER ==========
>> ======================
>> This message is printed in level of warning, yet it is just for tracing:
>> invoked onRuntimeException!
>> -----------------------------------------------------
>>
>> 2008-09-01 15:18:47,377 [ERROR]
>> security.authentication.NiteWebRequestCycleProcessor -
>> onRuntimeException stack:
>> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
>> rendered page in session [pagemap=null,componentPath=4:r
>> egistrationManagementForm,versionNumber=0]
>> at
>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:181)
>> at
>> il.org.nite.frm.security.authentication.NiteWebRequestCycleProcessor.resolve
>>
>> http://www.nabble.com/file/p19265678/prod_log.txt prod_log.txt
>>
>
>
--
View this message in context: http://www.nabble.com/PageExpiredException-on-production-tp19265678p20360050.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: PageExpiredException on production
Posted by "nico.ptrs" <ni...@gmail.com>.
Have you had any progress with this problem? I'm experiencing exactly the
same...
Thanks
rivkash1 wrote:
>
> hello all,
>
> We are working with Wicket (1.3.4) on production for a couple of months.
> It runs within jetty 6.1.7.
> For some weeks, we are experiencing a strange PageExpiredException which
> happens only on production env.
>
> It mostly happens on 2 main Pages in which the users submit the same form
> in a rolling manner (i.e. fill the form fields, submit the form, the user
> is redirected to the same page with a clean form and fills the form with
> new data and so on repeatedly).
>
> It isn't a problem of session expiration because our session timeout is
> set to 10 hours, this is the setting in our web.xml file:
>
> <session-config>
> <session-timeout>600</session-timeout>
> </session-config>
>
> We changed the logging level of Wicket to DEBUG, I'm attaching only a
> little fraction from our log file,
> you can see the whole exception in the file attached to this post:
>
> This message is printed in level of warning, yet it is just for tracing:
> invoked resolve! RequestParameters:
> [RequestParameters componentPath=4:registrationManagementForm
> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
> iorListener componentId=null behaviorId=1 urlDepth=-1
> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
> } onlyProcessIfPathActive=false]
> -----------------------------------------------------
>
> 2008-09-01 15:18:47,372 [WARN ]
> security.authentication.NiteWebRequestCycleProcessor -
> ===================== ENTER ==========
> ======================
> This message is printed in level of warning, yet it is just for tracing:
> invoked resolveRenderedPage! RequestParameters:
> [RequestParameters componentPath=4:registrationManagementForm
> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
> iorListener componentId=null behaviorId=1 urlDepth=-1
> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
> } onlyProcessIfPathActive=false]
> -----------------------------------------------------
>
> 2008-09-01 15:18:47,372 [DEBUG] apache.wicket.Session - Getting page
> [path = 4:registrationManagementForm, versionNumber = 0]
> 2008-09-01 15:18:47,376 [WARN ]
> security.authentication.NiteWebRequestCycleProcessor -
> -----------------------------------------------------
> completed resolveRenderedPage!======================== EXIT
> =============================
> 2008-09-01 15:18:47,377 [WARN ]
> security.authentication.NiteWebRequestCycleProcessor -
> ===================== ENTER ==========
> ======================
> This message is printed in level of warning, yet it is just for tracing:
> invoked respond(RuntimeException e, RequestCycle requestCycle)!
> -----------------------------------------------------
>
> 2008-09-01 15:18:47,377 [WARN ]
> security.authentication.NiteWebRequestCycleProcessor -
> ===================== ENTER ==========
> ======================
> This message is printed in level of warning, yet it is just for tracing:
> invoked onRuntimeException!
> -----------------------------------------------------
>
> 2008-09-01 15:18:47,377 [ERROR]
> security.authentication.NiteWebRequestCycleProcessor - onRuntimeException
> stack:
> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
> rendered page in session [pagemap=null,componentPath=4:r
> egistrationManagementForm,versionNumber=0]
> at
> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:181)
> at
> il.org.nite.frm.security.authentication.NiteWebRequestCycleProcessor.resolve
>
> http://www.nabble.com/file/p19265678/prod_log.txt prod_log.txt
>
--
View this message in context: http://www.nabble.com/PageExpiredException-on-production-tp19265678p20338193.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: PageExpiredException on production
Posted by rivkash1 <ri...@nite.org.il>.
It is a problem to debug the process because the exception is happening only
on production and it's occurance is unpredictable.
The users don't use the back button in this senario.
They do, however, work on 2 windows of firefox simulatnously (same session)
where one window is usually the rolling input page i mentioned before, and
the other is a simple CRUD page.
Nino.Martinez wrote:
>
> Hmm, have you supervised the process where they timeout? Or could it be
> that a few users that click the back button until they reach a page
> which are no longer in the pagemap, I belive 15 are the default?
>
> rivkash1 wrote:
>> hello all,
>>
>> We are working with Wicket (1.3.4) on production for a couple of months.
>> It
>> runs within jetty 6.1.7.
>> For some weeks, we are experiencing a strange PageExpiredException which
>> happens only on production env.
>>
>> It mostly happens on 2 main Pages in which the users submit the same form
>> in
>> a rolling manner (i.e. fill the form fields, submit the form, the user is
>> redirected to the same page with a clean form and fills the form with new
>> data and so on repeatedly).
>>
>> It isn't a problem of session expiration because our session timeout is
>> set
>> to 10 hours, this is the setting in our web.xml file:
>>
>> <session-config>
>> <session-timeout>600</session-timeout>
>> </session-config>
>>
>> We changed the logging level of Wicket to DEBUG, I'm attaching only a
>> little
>> fraction from our log file,
>> you can see the whole exception in the file attached to this post:
>>
>> This message is printed in level of warning, yet it is just for tracing:
>> invoked resolve! RequestParameters:
>> [RequestParameters componentPath=4:registrationManagementForm
>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>> iorListener componentId=null behaviorId=1 urlDepth=-1
>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>> } onlyProcessIfPathActive=false]
>> -----------------------------------------------------
>>
>> 2008-09-01 15:18:47,372 [WARN ]
>> security.authentication.NiteWebRequestCycleProcessor -
>> ===================== ENTER ==========
>> ======================
>> This message is printed in level of warning, yet it is just for tracing:
>> invoked resolveRenderedPage! RequestParameters:
>> [RequestParameters componentPath=4:registrationManagementForm
>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>> iorListener componentId=null behaviorId=1 urlDepth=-1
>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>> } onlyProcessIfPathActive=false]
>> -----------------------------------------------------
>>
>> 2008-09-01 15:18:47,372 [DEBUG] apache.wicket.Session - Getting page
>> [path
>> = 4:registrationManagementForm, versionNumber = 0]
>> 2008-09-01 15:18:47,376 [WARN ]
>> security.authentication.NiteWebRequestCycleProcessor -
>> -----------------------------------------------------
>> completed resolveRenderedPage!======================== EXIT
>> =============================
>> 2008-09-01 15:18:47,377 [WARN ]
>> security.authentication.NiteWebRequestCycleProcessor -
>> ===================== ENTER ==========
>> ======================
>> This message is printed in level of warning, yet it is just for tracing:
>> invoked respond(RuntimeException e, RequestCycle requestCycle)!
>> -----------------------------------------------------
>>
>> 2008-09-01 15:18:47,377 [WARN ]
>> security.authentication.NiteWebRequestCycleProcessor -
>> ===================== ENTER ==========
>> ======================
>> This message is printed in level of warning, yet it is just for tracing:
>> invoked onRuntimeException!
>> -----------------------------------------------------
>>
>> 2008-09-01 15:18:47,377 [ERROR]
>> security.authentication.NiteWebRequestCycleProcessor -
>> onRuntimeException
>> stack:
>> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
>> rendered page in session [pagemap=null,componentPath=4:r
>> egistrationManagementForm,versionNumber=0]
>> at
>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:181)
>> at
>> il.org.nite.frm.security.authentication.NiteWebRequestCycleProcessor.resolve
>>
>> http://www.nabble.com/file/p19265678/prod_log.txt prod_log.txt
>>
>
> --
> -Wicket for love
>
> Nino Martinez Wael
> Java Specialist @ Jayway DK
> http://www.jayway.dk
> +45 2936 7684
>
>
> ---------------------------------------------------------------------
> 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://www.nabble.com/PageExpiredException-on-production-tp19265678p19273738.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: PageExpiredException on production
Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
Hmm, have you supervised the process where they timeout? Or could it be
that a few users that click the back button until they reach a page
which are no longer in the pagemap, I belive 15 are the default?
rivkash1 wrote:
> hello all,
>
> We are working with Wicket (1.3.4) on production for a couple of months. It
> runs within jetty 6.1.7.
> For some weeks, we are experiencing a strange PageExpiredException which
> happens only on production env.
>
> It mostly happens on 2 main Pages in which the users submit the same form in
> a rolling manner (i.e. fill the form fields, submit the form, the user is
> redirected to the same page with a clean form and fills the form with new
> data and so on repeatedly).
>
> It isn't a problem of session expiration because our session timeout is set
> to 10 hours, this is the setting in our web.xml file:
>
> <session-config>
> <session-timeout>600</session-timeout>
> </session-config>
>
> We changed the logging level of Wicket to DEBUG, I'm attaching only a little
> fraction from our log file,
> you can see the whole exception in the file attached to this post:
>
> This message is printed in level of warning, yet it is just for tracing:
> invoked resolve! RequestParameters:
> [RequestParameters componentPath=4:registrationManagementForm
> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
> iorListener componentId=null behaviorId=1 urlDepth=-1
> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
> } onlyProcessIfPathActive=false]
> -----------------------------------------------------
>
> 2008-09-01 15:18:47,372 [WARN ]
> security.authentication.NiteWebRequestCycleProcessor -
> ===================== ENTER ==========
> ======================
> This message is printed in level of warning, yet it is just for tracing:
> invoked resolveRenderedPage! RequestParameters:
> [RequestParameters componentPath=4:registrationManagementForm
> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
> iorListener componentId=null behaviorId=1 urlDepth=-1
> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
> } onlyProcessIfPathActive=false]
> -----------------------------------------------------
>
> 2008-09-01 15:18:47,372 [DEBUG] apache.wicket.Session - Getting page [path
> = 4:registrationManagementForm, versionNumber = 0]
> 2008-09-01 15:18:47,376 [WARN ]
> security.authentication.NiteWebRequestCycleProcessor -
> -----------------------------------------------------
> completed resolveRenderedPage!======================== EXIT
> =============================
> 2008-09-01 15:18:47,377 [WARN ]
> security.authentication.NiteWebRequestCycleProcessor -
> ===================== ENTER ==========
> ======================
> This message is printed in level of warning, yet it is just for tracing:
> invoked respond(RuntimeException e, RequestCycle requestCycle)!
> -----------------------------------------------------
>
> 2008-09-01 15:18:47,377 [WARN ]
> security.authentication.NiteWebRequestCycleProcessor -
> ===================== ENTER ==========
> ======================
> This message is printed in level of warning, yet it is just for tracing:
> invoked onRuntimeException!
> -----------------------------------------------------
>
> 2008-09-01 15:18:47,377 [ERROR]
> security.authentication.NiteWebRequestCycleProcessor - onRuntimeException
> stack:
> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
> rendered page in session [pagemap=null,componentPath=4:r
> egistrationManagementForm,versionNumber=0]
> at
> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:181)
> at
> il.org.nite.frm.security.authentication.NiteWebRequestCycleProcessor.resolve
>
> http://www.nabble.com/file/p19265678/prod_log.txt prod_log.txt
>
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: PageExpiredException on production
Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
It's on as default.. But checking the log for serializing errors will
help you find out what the problem are..
rivkash1 wrote:
> How do i check if the serializer is on/off? What's the defualt?
>
>
> Nino.Martinez wrote:
>
>> Did you actively turn serializer check off?
>>
>> rivkash1 wrote:
>>
>>> we set Wicket's logging level on production to DEBUG
>>> I don't see any non-serializable errors.
>>> How do i turn on the serializer check?
>>>
>>> thanks
>>> Rebecca
>>>
>>>
>>> Martijn Dashorst wrote:
>>>
>>>
>>>> Check your logs for non-serializable errors (or test your application
>>>> locally with development mode on, and make sure the serializer check
>>>> is not turned off). This is the most common case for page expired
>>>> errors.
>>>>
>>>> Martijn
>>>>
>>>> On Wed, Sep 3, 2008 at 10:45 AM, rivkash1 <ri...@nite.org.il> wrote:
>>>>
>>>>
>>>>> Hi Martijn
>>>>>
>>>>> NiteWebRequestCycleProcessor is a Class we added to the application 2
>>>>> days
>>>>> ago. It extends Wicket's WebRequestCycleProcessor and adds some
>>>>> messages
>>>>> to
>>>>> the log to get more information about the problem.
>>>>>
>>>>> The PageExpiredException is a problem that we have on production for a
>>>>> couple of weeks - long before the NiteWebRequestCycleProcessor class
>>>>> was
>>>>> created in the application.
>>>>>
>>>>> thanks
>>>>> Rebecca
>>>>>
>>>>>
>>>>> Martijn Dashorst wrote:
>>>>>
>>>>>
>>>>>> Sounds like a bug in your NiteWebRequestCycleProcessor
>>>>>>
>>>>>> Martijn
>>>>>>
>>>>>> On Wed, Sep 3, 2008 at 10:29 AM, rivkash1 <ri...@nite.org.il> wrote:
>>>>>>
>>>>>>
>>>>>>> Hello again,
>>>>>>>
>>>>>>> does someone have any more ideas about our problem?
>>>>>>> It is very problematic to work in production when the users are
>>>>>>> thrown
>>>>>>> out
>>>>>>> with exception each hour...
>>>>>>>
>>>>>>> thanks
>>>>>>> Rebecca
>>>>>>>
>>>>>>>
>>>>>>> rivkash1 wrote:
>>>>>>>
>>>>>>>
>>>>>>>> hello all,
>>>>>>>>
>>>>>>>> We are working with Wicket (1.3.4) on production for a couple of
>>>>>>>> months.
>>>>>>>> It runs within jetty 6.1.7.
>>>>>>>> For some weeks, we are experiencing a strange PageExpiredException
>>>>>>>> which
>>>>>>>> happens only on production env.
>>>>>>>>
>>>>>>>> It mostly happens on 2 main Pages in which the users submit the same
>>>>>>>> form
>>>>>>>> in a rolling manner (i.e. fill the form fields, submit the form, the
>>>>>>>> user
>>>>>>>> is redirected to the same page with a clean form and fills the form
>>>>>>>> with
>>>>>>>> new data and so on repeatedly).
>>>>>>>>
>>>>>>>> It isn't a problem of session expiration because our session timeout
>>>>>>>> is
>>>>>>>> set to 10 hours, this is the setting in our web.xml file:
>>>>>>>>
>>>>>>>> <session-config>
>>>>>>>> <session-timeout>600</session-timeout>
>>>>>>>> </session-config>
>>>>>>>>
>>>>>>>> We changed the logging level of Wicket to DEBUG, I'm attaching only
>>>>>>>> a
>>>>>>>> little fraction from our log file,
>>>>>>>> you can see the whole exception in the file attached to this post:
>>>>>>>>
>>>>>>>> This message is printed in level of warning, yet it is just for
>>>>>>>> tracing:
>>>>>>>> invoked resolve! RequestParameters:
>>>>>>>> [RequestParameters componentPath=4:registrationManagementForm
>>>>>>>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>>>>>>>> iorListener componentId=null behaviorId=1 urlDepth=-1
>>>>>>>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>>>>>>>> } onlyProcessIfPathActive=false]
>>>>>>>> -----------------------------------------------------
>>>>>>>>
>>>>>>>> 2008-09-01 15:18:47,372 [WARN ]
>>>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>>>> ===================== ENTER ==========
>>>>>>>> ======================
>>>>>>>> This message is printed in level of warning, yet it is just for
>>>>>>>> tracing:
>>>>>>>> invoked resolveRenderedPage! RequestParameters:
>>>>>>>> [RequestParameters componentPath=4:registrationManagementForm
>>>>>>>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>>>>>>>> iorListener componentId=null behaviorId=1 urlDepth=-1
>>>>>>>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>>>>>>>> } onlyProcessIfPathActive=false]
>>>>>>>> -----------------------------------------------------
>>>>>>>>
>>>>>>>> 2008-09-01 15:18:47,372 [DEBUG] apache.wicket.Session - Getting
>>>>>>>> page
>>>>>>>> [path = 4:registrationManagementForm, versionNumber = 0]
>>>>>>>> 2008-09-01 15:18:47,376 [WARN ]
>>>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>>>> -----------------------------------------------------
>>>>>>>> completed resolveRenderedPage!======================== EXIT
>>>>>>>> =============================
>>>>>>>> 2008-09-01 15:18:47,377 [WARN ]
>>>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>>>> ===================== ENTER ==========
>>>>>>>> ======================
>>>>>>>> This message is printed in level of warning, yet it is just for
>>>>>>>> tracing:
>>>>>>>> invoked respond(RuntimeException e, RequestCycle requestCycle)!
>>>>>>>> -----------------------------------------------------
>>>>>>>>
>>>>>>>> 2008-09-01 15:18:47,377 [WARN ]
>>>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>>>> ===================== ENTER ==========
>>>>>>>> ======================
>>>>>>>> This message is printed in level of warning, yet it is just for
>>>>>>>> tracing:
>>>>>>>> invoked onRuntimeException!
>>>>>>>> -----------------------------------------------------
>>>>>>>>
>>>>>>>> 2008-09-01 15:18:47,377 [ERROR]
>>>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>>>> onRuntimeException
>>>>>>>> stack:
>>>>>>>> org.apache.wicket.protocol.http.PageExpiredException: Cannot find
>>>>>>>> the
>>>>>>>> rendered page in session [pagemap=null,componentPath=4:r
>>>>>>>> egistrationManagementForm,versionNumber=0]
>>>>>>>> at
>>>>>>>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:181)
>>>>>>>> at
>>>>>>>> il.org.nite.frm.security.authentication.NiteWebRequestCycleProcessor.resolve
>>>>>>>>
>>>>>>>> http://www.nabble.com/file/p19265678/prod_log.txt prod_log.txt
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> :-((:-((:-((:-((:-((
>>>>>>> --
>>>>>>> View this message in context:
>>>>>>> http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285008.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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> --
>>>>>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>>>>>> Apache Wicket 1.3.4 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
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285219.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
>>>>>
>>>>>
>>>>>
>>>>>
>>>> --
>>>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>>>> Apache Wicket 1.3.4 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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>> --
>> -Wicket for love
>>
>> Nino Martinez Wael
>> Java Specialist @ Jayway DK
>> http://www.jayway.dk
>> +45 2936 7684
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>>
>
>
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: PageExpiredException on production
Posted by rivkash1 <ri...@nite.org.il>.
How do i check if the serializer is on/off? What's the defualt?
Nino.Martinez wrote:
>
> Did you actively turn serializer check off?
>
> rivkash1 wrote:
>> we set Wicket's logging level on production to DEBUG
>> I don't see any non-serializable errors.
>> How do i turn on the serializer check?
>>
>> thanks
>> Rebecca
>>
>>
>> Martijn Dashorst wrote:
>>
>>> Check your logs for non-serializable errors (or test your application
>>> locally with development mode on, and make sure the serializer check
>>> is not turned off). This is the most common case for page expired
>>> errors.
>>>
>>> Martijn
>>>
>>> On Wed, Sep 3, 2008 at 10:45 AM, rivkash1 <ri...@nite.org.il> wrote:
>>>
>>>> Hi Martijn
>>>>
>>>> NiteWebRequestCycleProcessor is a Class we added to the application 2
>>>> days
>>>> ago. It extends Wicket's WebRequestCycleProcessor and adds some
>>>> messages
>>>> to
>>>> the log to get more information about the problem.
>>>>
>>>> The PageExpiredException is a problem that we have on production for a
>>>> couple of weeks - long before the NiteWebRequestCycleProcessor class
>>>> was
>>>> created in the application.
>>>>
>>>> thanks
>>>> Rebecca
>>>>
>>>>
>>>> Martijn Dashorst wrote:
>>>>
>>>>> Sounds like a bug in your NiteWebRequestCycleProcessor
>>>>>
>>>>> Martijn
>>>>>
>>>>> On Wed, Sep 3, 2008 at 10:29 AM, rivkash1 <ri...@nite.org.il> wrote:
>>>>>
>>>>>> Hello again,
>>>>>>
>>>>>> does someone have any more ideas about our problem?
>>>>>> It is very problematic to work in production when the users are
>>>>>> thrown
>>>>>> out
>>>>>> with exception each hour...
>>>>>>
>>>>>> thanks
>>>>>> Rebecca
>>>>>>
>>>>>>
>>>>>> rivkash1 wrote:
>>>>>>
>>>>>>> hello all,
>>>>>>>
>>>>>>> We are working with Wicket (1.3.4) on production for a couple of
>>>>>>> months.
>>>>>>> It runs within jetty 6.1.7.
>>>>>>> For some weeks, we are experiencing a strange PageExpiredException
>>>>>>> which
>>>>>>> happens only on production env.
>>>>>>>
>>>>>>> It mostly happens on 2 main Pages in which the users submit the same
>>>>>>> form
>>>>>>> in a rolling manner (i.e. fill the form fields, submit the form, the
>>>>>>> user
>>>>>>> is redirected to the same page with a clean form and fills the form
>>>>>>> with
>>>>>>> new data and so on repeatedly).
>>>>>>>
>>>>>>> It isn't a problem of session expiration because our session timeout
>>>>>>> is
>>>>>>> set to 10 hours, this is the setting in our web.xml file:
>>>>>>>
>>>>>>> <session-config>
>>>>>>> <session-timeout>600</session-timeout>
>>>>>>> </session-config>
>>>>>>>
>>>>>>> We changed the logging level of Wicket to DEBUG, I'm attaching only
>>>>>>> a
>>>>>>> little fraction from our log file,
>>>>>>> you can see the whole exception in the file attached to this post:
>>>>>>>
>>>>>>> This message is printed in level of warning, yet it is just for
>>>>>>> tracing:
>>>>>>> invoked resolve! RequestParameters:
>>>>>>> [RequestParameters componentPath=4:registrationManagementForm
>>>>>>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>>>>>>> iorListener componentId=null behaviorId=1 urlDepth=-1
>>>>>>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>>>>>>> } onlyProcessIfPathActive=false]
>>>>>>> -----------------------------------------------------
>>>>>>>
>>>>>>> 2008-09-01 15:18:47,372 [WARN ]
>>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>>> ===================== ENTER ==========
>>>>>>> ======================
>>>>>>> This message is printed in level of warning, yet it is just for
>>>>>>> tracing:
>>>>>>> invoked resolveRenderedPage! RequestParameters:
>>>>>>> [RequestParameters componentPath=4:registrationManagementForm
>>>>>>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>>>>>>> iorListener componentId=null behaviorId=1 urlDepth=-1
>>>>>>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>>>>>>> } onlyProcessIfPathActive=false]
>>>>>>> -----------------------------------------------------
>>>>>>>
>>>>>>> 2008-09-01 15:18:47,372 [DEBUG] apache.wicket.Session - Getting
>>>>>>> page
>>>>>>> [path = 4:registrationManagementForm, versionNumber = 0]
>>>>>>> 2008-09-01 15:18:47,376 [WARN ]
>>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>>> -----------------------------------------------------
>>>>>>> completed resolveRenderedPage!======================== EXIT
>>>>>>> =============================
>>>>>>> 2008-09-01 15:18:47,377 [WARN ]
>>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>>> ===================== ENTER ==========
>>>>>>> ======================
>>>>>>> This message is printed in level of warning, yet it is just for
>>>>>>> tracing:
>>>>>>> invoked respond(RuntimeException e, RequestCycle requestCycle)!
>>>>>>> -----------------------------------------------------
>>>>>>>
>>>>>>> 2008-09-01 15:18:47,377 [WARN ]
>>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>>> ===================== ENTER ==========
>>>>>>> ======================
>>>>>>> This message is printed in level of warning, yet it is just for
>>>>>>> tracing:
>>>>>>> invoked onRuntimeException!
>>>>>>> -----------------------------------------------------
>>>>>>>
>>>>>>> 2008-09-01 15:18:47,377 [ERROR]
>>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>>> onRuntimeException
>>>>>>> stack:
>>>>>>> org.apache.wicket.protocol.http.PageExpiredException: Cannot find
>>>>>>> the
>>>>>>> rendered page in session [pagemap=null,componentPath=4:r
>>>>>>> egistrationManagementForm,versionNumber=0]
>>>>>>> at
>>>>>>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:181)
>>>>>>> at
>>>>>>> il.org.nite.frm.security.authentication.NiteWebRequestCycleProcessor.resolve
>>>>>>>
>>>>>>> http://www.nabble.com/file/p19265678/prod_log.txt prod_log.txt
>>>>>>>
>>>>>>>
>>>>>> :-((:-((:-((:-((:-((
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285008.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
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>>>>> Apache Wicket 1.3.4 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
>>>>>
>>>>>
>>>>>
>>>>>
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285219.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
>>>>
>>>>
>>>>
>>>
>>> --
>>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>>> Apache Wicket 1.3.4 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
>>>
>>>
>>>
>>>
>>
>>
>
> --
> -Wicket for love
>
> Nino Martinez Wael
> Java Specialist @ Jayway DK
> http://www.jayway.dk
> +45 2936 7684
>
>
> ---------------------------------------------------------------------
> 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://www.nabble.com/PageExpiredException-on-production-tp19265678p19289432.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: PageExpiredException on production
Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
Did you actively turn serializer check off?
rivkash1 wrote:
> we set Wicket's logging level on production to DEBUG
> I don't see any non-serializable errors.
> How do i turn on the serializer check?
>
> thanks
> Rebecca
>
>
> Martijn Dashorst wrote:
>
>> Check your logs for non-serializable errors (or test your application
>> locally with development mode on, and make sure the serializer check
>> is not turned off). This is the most common case for page expired
>> errors.
>>
>> Martijn
>>
>> On Wed, Sep 3, 2008 at 10:45 AM, rivkash1 <ri...@nite.org.il> wrote:
>>
>>> Hi Martijn
>>>
>>> NiteWebRequestCycleProcessor is a Class we added to the application 2
>>> days
>>> ago. It extends Wicket's WebRequestCycleProcessor and adds some messages
>>> to
>>> the log to get more information about the problem.
>>>
>>> The PageExpiredException is a problem that we have on production for a
>>> couple of weeks - long before the NiteWebRequestCycleProcessor class was
>>> created in the application.
>>>
>>> thanks
>>> Rebecca
>>>
>>>
>>> Martijn Dashorst wrote:
>>>
>>>> Sounds like a bug in your NiteWebRequestCycleProcessor
>>>>
>>>> Martijn
>>>>
>>>> On Wed, Sep 3, 2008 at 10:29 AM, rivkash1 <ri...@nite.org.il> wrote:
>>>>
>>>>> Hello again,
>>>>>
>>>>> does someone have any more ideas about our problem?
>>>>> It is very problematic to work in production when the users are thrown
>>>>> out
>>>>> with exception each hour...
>>>>>
>>>>> thanks
>>>>> Rebecca
>>>>>
>>>>>
>>>>> rivkash1 wrote:
>>>>>
>>>>>> hello all,
>>>>>>
>>>>>> We are working with Wicket (1.3.4) on production for a couple of
>>>>>> months.
>>>>>> It runs within jetty 6.1.7.
>>>>>> For some weeks, we are experiencing a strange PageExpiredException
>>>>>> which
>>>>>> happens only on production env.
>>>>>>
>>>>>> It mostly happens on 2 main Pages in which the users submit the same
>>>>>> form
>>>>>> in a rolling manner (i.e. fill the form fields, submit the form, the
>>>>>> user
>>>>>> is redirected to the same page with a clean form and fills the form
>>>>>> with
>>>>>> new data and so on repeatedly).
>>>>>>
>>>>>> It isn't a problem of session expiration because our session timeout
>>>>>> is
>>>>>> set to 10 hours, this is the setting in our web.xml file:
>>>>>>
>>>>>> <session-config>
>>>>>> <session-timeout>600</session-timeout>
>>>>>> </session-config>
>>>>>>
>>>>>> We changed the logging level of Wicket to DEBUG, I'm attaching only a
>>>>>> little fraction from our log file,
>>>>>> you can see the whole exception in the file attached to this post:
>>>>>>
>>>>>> This message is printed in level of warning, yet it is just for
>>>>>> tracing:
>>>>>> invoked resolve! RequestParameters:
>>>>>> [RequestParameters componentPath=4:registrationManagementForm
>>>>>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>>>>>> iorListener componentId=null behaviorId=1 urlDepth=-1
>>>>>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>>>>>> } onlyProcessIfPathActive=false]
>>>>>> -----------------------------------------------------
>>>>>>
>>>>>> 2008-09-01 15:18:47,372 [WARN ]
>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>> ===================== ENTER ==========
>>>>>> ======================
>>>>>> This message is printed in level of warning, yet it is just for
>>>>>> tracing:
>>>>>> invoked resolveRenderedPage! RequestParameters:
>>>>>> [RequestParameters componentPath=4:registrationManagementForm
>>>>>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>>>>>> iorListener componentId=null behaviorId=1 urlDepth=-1
>>>>>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>>>>>> } onlyProcessIfPathActive=false]
>>>>>> -----------------------------------------------------
>>>>>>
>>>>>> 2008-09-01 15:18:47,372 [DEBUG] apache.wicket.Session - Getting page
>>>>>> [path = 4:registrationManagementForm, versionNumber = 0]
>>>>>> 2008-09-01 15:18:47,376 [WARN ]
>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>> -----------------------------------------------------
>>>>>> completed resolveRenderedPage!======================== EXIT
>>>>>> =============================
>>>>>> 2008-09-01 15:18:47,377 [WARN ]
>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>> ===================== ENTER ==========
>>>>>> ======================
>>>>>> This message is printed in level of warning, yet it is just for
>>>>>> tracing:
>>>>>> invoked respond(RuntimeException e, RequestCycle requestCycle)!
>>>>>> -----------------------------------------------------
>>>>>>
>>>>>> 2008-09-01 15:18:47,377 [WARN ]
>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>> ===================== ENTER ==========
>>>>>> ======================
>>>>>> This message is printed in level of warning, yet it is just for
>>>>>> tracing:
>>>>>> invoked onRuntimeException!
>>>>>> -----------------------------------------------------
>>>>>>
>>>>>> 2008-09-01 15:18:47,377 [ERROR]
>>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>>> onRuntimeException
>>>>>> stack:
>>>>>> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
>>>>>> rendered page in session [pagemap=null,componentPath=4:r
>>>>>> egistrationManagementForm,versionNumber=0]
>>>>>> at
>>>>>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:181)
>>>>>> at
>>>>>> il.org.nite.frm.security.authentication.NiteWebRequestCycleProcessor.resolve
>>>>>>
>>>>>> http://www.nabble.com/file/p19265678/prod_log.txt prod_log.txt
>>>>>>
>>>>>>
>>>>> :-((:-((:-((:-((:-((
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285008.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
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>>>> Apache Wicket 1.3.4 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
>>>>
>>>>
>>>>
>>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285219.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
>>>
>>>
>>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.3.4 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
>>
>>
>>
>>
>
>
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: PageExpiredException on production
Posted by rivkash1 <ri...@nite.org.il>.
we set Wicket's logging level on production to DEBUG
I don't see any non-serializable errors.
How do i turn on the serializer check?
thanks
Rebecca
Martijn Dashorst wrote:
>
> Check your logs for non-serializable errors (or test your application
> locally with development mode on, and make sure the serializer check
> is not turned off). This is the most common case for page expired
> errors.
>
> Martijn
>
> On Wed, Sep 3, 2008 at 10:45 AM, rivkash1 <ri...@nite.org.il> wrote:
>>
>> Hi Martijn
>>
>> NiteWebRequestCycleProcessor is a Class we added to the application 2
>> days
>> ago. It extends Wicket's WebRequestCycleProcessor and adds some messages
>> to
>> the log to get more information about the problem.
>>
>> The PageExpiredException is a problem that we have on production for a
>> couple of weeks - long before the NiteWebRequestCycleProcessor class was
>> created in the application.
>>
>> thanks
>> Rebecca
>>
>>
>> Martijn Dashorst wrote:
>>>
>>> Sounds like a bug in your NiteWebRequestCycleProcessor
>>>
>>> Martijn
>>>
>>> On Wed, Sep 3, 2008 at 10:29 AM, rivkash1 <ri...@nite.org.il> wrote:
>>>>
>>>> Hello again,
>>>>
>>>> does someone have any more ideas about our problem?
>>>> It is very problematic to work in production when the users are thrown
>>>> out
>>>> with exception each hour...
>>>>
>>>> thanks
>>>> Rebecca
>>>>
>>>>
>>>> rivkash1 wrote:
>>>>>
>>>>> hello all,
>>>>>
>>>>> We are working with Wicket (1.3.4) on production for a couple of
>>>>> months.
>>>>> It runs within jetty 6.1.7.
>>>>> For some weeks, we are experiencing a strange PageExpiredException
>>>>> which
>>>>> happens only on production env.
>>>>>
>>>>> It mostly happens on 2 main Pages in which the users submit the same
>>>>> form
>>>>> in a rolling manner (i.e. fill the form fields, submit the form, the
>>>>> user
>>>>> is redirected to the same page with a clean form and fills the form
>>>>> with
>>>>> new data and so on repeatedly).
>>>>>
>>>>> It isn't a problem of session expiration because our session timeout
>>>>> is
>>>>> set to 10 hours, this is the setting in our web.xml file:
>>>>>
>>>>> <session-config>
>>>>> <session-timeout>600</session-timeout>
>>>>> </session-config>
>>>>>
>>>>> We changed the logging level of Wicket to DEBUG, I'm attaching only a
>>>>> little fraction from our log file,
>>>>> you can see the whole exception in the file attached to this post:
>>>>>
>>>>> This message is printed in level of warning, yet it is just for
>>>>> tracing:
>>>>> invoked resolve! RequestParameters:
>>>>> [RequestParameters componentPath=4:registrationManagementForm
>>>>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>>>>> iorListener componentId=null behaviorId=1 urlDepth=-1
>>>>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>>>>> } onlyProcessIfPathActive=false]
>>>>> -----------------------------------------------------
>>>>>
>>>>> 2008-09-01 15:18:47,372 [WARN ]
>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>> ===================== ENTER ==========
>>>>> ======================
>>>>> This message is printed in level of warning, yet it is just for
>>>>> tracing:
>>>>> invoked resolveRenderedPage! RequestParameters:
>>>>> [RequestParameters componentPath=4:registrationManagementForm
>>>>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>>>>> iorListener componentId=null behaviorId=1 urlDepth=-1
>>>>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>>>>> } onlyProcessIfPathActive=false]
>>>>> -----------------------------------------------------
>>>>>
>>>>> 2008-09-01 15:18:47,372 [DEBUG] apache.wicket.Session - Getting page
>>>>> [path = 4:registrationManagementForm, versionNumber = 0]
>>>>> 2008-09-01 15:18:47,376 [WARN ]
>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>> -----------------------------------------------------
>>>>> completed resolveRenderedPage!======================== EXIT
>>>>> =============================
>>>>> 2008-09-01 15:18:47,377 [WARN ]
>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>> ===================== ENTER ==========
>>>>> ======================
>>>>> This message is printed in level of warning, yet it is just for
>>>>> tracing:
>>>>> invoked respond(RuntimeException e, RequestCycle requestCycle)!
>>>>> -----------------------------------------------------
>>>>>
>>>>> 2008-09-01 15:18:47,377 [WARN ]
>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>> ===================== ENTER ==========
>>>>> ======================
>>>>> This message is printed in level of warning, yet it is just for
>>>>> tracing:
>>>>> invoked onRuntimeException!
>>>>> -----------------------------------------------------
>>>>>
>>>>> 2008-09-01 15:18:47,377 [ERROR]
>>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>>> onRuntimeException
>>>>> stack:
>>>>> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
>>>>> rendered page in session [pagemap=null,componentPath=4:r
>>>>> egistrationManagementForm,versionNumber=0]
>>>>> at
>>>>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:181)
>>>>> at
>>>>> il.org.nite.frm.security.authentication.NiteWebRequestCycleProcessor.resolve
>>>>>
>>>>> http://www.nabble.com/file/p19265678/prod_log.txt prod_log.txt
>>>>>
>>>> :-((:-((:-((:-((:-((
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285008.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
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>>> Apache Wicket 1.3.4 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
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285219.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
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.4 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
>
>
>
--
View this message in context: http://www.nabble.com/PageExpiredException-on-production-tp19265678p19287382.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: PageExpiredException on production
Posted by Martijn Dashorst <ma...@gmail.com>.
Check your logs for non-serializable errors (or test your application
locally with development mode on, and make sure the serializer check
is not turned off). This is the most common case for page expired
errors.
Martijn
On Wed, Sep 3, 2008 at 10:45 AM, rivkash1 <ri...@nite.org.il> wrote:
>
> Hi Martijn
>
> NiteWebRequestCycleProcessor is a Class we added to the application 2 days
> ago. It extends Wicket's WebRequestCycleProcessor and adds some messages to
> the log to get more information about the problem.
>
> The PageExpiredException is a problem that we have on production for a
> couple of weeks - long before the NiteWebRequestCycleProcessor class was
> created in the application.
>
> thanks
> Rebecca
>
>
> Martijn Dashorst wrote:
>>
>> Sounds like a bug in your NiteWebRequestCycleProcessor
>>
>> Martijn
>>
>> On Wed, Sep 3, 2008 at 10:29 AM, rivkash1 <ri...@nite.org.il> wrote:
>>>
>>> Hello again,
>>>
>>> does someone have any more ideas about our problem?
>>> It is very problematic to work in production when the users are thrown
>>> out
>>> with exception each hour...
>>>
>>> thanks
>>> Rebecca
>>>
>>>
>>> rivkash1 wrote:
>>>>
>>>> hello all,
>>>>
>>>> We are working with Wicket (1.3.4) on production for a couple of months.
>>>> It runs within jetty 6.1.7.
>>>> For some weeks, we are experiencing a strange PageExpiredException which
>>>> happens only on production env.
>>>>
>>>> It mostly happens on 2 main Pages in which the users submit the same
>>>> form
>>>> in a rolling manner (i.e. fill the form fields, submit the form, the
>>>> user
>>>> is redirected to the same page with a clean form and fills the form with
>>>> new data and so on repeatedly).
>>>>
>>>> It isn't a problem of session expiration because our session timeout is
>>>> set to 10 hours, this is the setting in our web.xml file:
>>>>
>>>> <session-config>
>>>> <session-timeout>600</session-timeout>
>>>> </session-config>
>>>>
>>>> We changed the logging level of Wicket to DEBUG, I'm attaching only a
>>>> little fraction from our log file,
>>>> you can see the whole exception in the file attached to this post:
>>>>
>>>> This message is printed in level of warning, yet it is just for tracing:
>>>> invoked resolve! RequestParameters:
>>>> [RequestParameters componentPath=4:registrationManagementForm
>>>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>>>> iorListener componentId=null behaviorId=1 urlDepth=-1
>>>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>>>> } onlyProcessIfPathActive=false]
>>>> -----------------------------------------------------
>>>>
>>>> 2008-09-01 15:18:47,372 [WARN ]
>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>> ===================== ENTER ==========
>>>> ======================
>>>> This message is printed in level of warning, yet it is just for tracing:
>>>> invoked resolveRenderedPage! RequestParameters:
>>>> [RequestParameters componentPath=4:registrationManagementForm
>>>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>>>> iorListener componentId=null behaviorId=1 urlDepth=-1
>>>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>>>> } onlyProcessIfPathActive=false]
>>>> -----------------------------------------------------
>>>>
>>>> 2008-09-01 15:18:47,372 [DEBUG] apache.wicket.Session - Getting page
>>>> [path = 4:registrationManagementForm, versionNumber = 0]
>>>> 2008-09-01 15:18:47,376 [WARN ]
>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>> -----------------------------------------------------
>>>> completed resolveRenderedPage!======================== EXIT
>>>> =============================
>>>> 2008-09-01 15:18:47,377 [WARN ]
>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>> ===================== ENTER ==========
>>>> ======================
>>>> This message is printed in level of warning, yet it is just for tracing:
>>>> invoked respond(RuntimeException e, RequestCycle requestCycle)!
>>>> -----------------------------------------------------
>>>>
>>>> 2008-09-01 15:18:47,377 [WARN ]
>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>> ===================== ENTER ==========
>>>> ======================
>>>> This message is printed in level of warning, yet it is just for tracing:
>>>> invoked onRuntimeException!
>>>> -----------------------------------------------------
>>>>
>>>> 2008-09-01 15:18:47,377 [ERROR]
>>>> security.authentication.NiteWebRequestCycleProcessor -
>>>> onRuntimeException
>>>> stack:
>>>> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
>>>> rendered page in session [pagemap=null,componentPath=4:r
>>>> egistrationManagementForm,versionNumber=0]
>>>> at
>>>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:181)
>>>> at
>>>> il.org.nite.frm.security.authentication.NiteWebRequestCycleProcessor.resolve
>>>>
>>>> http://www.nabble.com/file/p19265678/prod_log.txt prod_log.txt
>>>>
>>> :-((:-((:-((:-((:-((
>>> --
>>> View this message in context:
>>> http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285008.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
>>>
>>>
>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.3.4 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
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285219.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
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 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: PageExpiredException on production
Posted by rivkash1 <ri...@nite.org.il>.
Hi Martijn
NiteWebRequestCycleProcessor is a Class we added to the application 2 days
ago. It extends Wicket's WebRequestCycleProcessor and adds some messages to
the log to get more information about the problem.
The PageExpiredException is a problem that we have on production for a
couple of weeks - long before the NiteWebRequestCycleProcessor class was
created in the application.
thanks
Rebecca
Martijn Dashorst wrote:
>
> Sounds like a bug in your NiteWebRequestCycleProcessor
>
> Martijn
>
> On Wed, Sep 3, 2008 at 10:29 AM, rivkash1 <ri...@nite.org.il> wrote:
>>
>> Hello again,
>>
>> does someone have any more ideas about our problem?
>> It is very problematic to work in production when the users are thrown
>> out
>> with exception each hour...
>>
>> thanks
>> Rebecca
>>
>>
>> rivkash1 wrote:
>>>
>>> hello all,
>>>
>>> We are working with Wicket (1.3.4) on production for a couple of months.
>>> It runs within jetty 6.1.7.
>>> For some weeks, we are experiencing a strange PageExpiredException which
>>> happens only on production env.
>>>
>>> It mostly happens on 2 main Pages in which the users submit the same
>>> form
>>> in a rolling manner (i.e. fill the form fields, submit the form, the
>>> user
>>> is redirected to the same page with a clean form and fills the form with
>>> new data and so on repeatedly).
>>>
>>> It isn't a problem of session expiration because our session timeout is
>>> set to 10 hours, this is the setting in our web.xml file:
>>>
>>> <session-config>
>>> <session-timeout>600</session-timeout>
>>> </session-config>
>>>
>>> We changed the logging level of Wicket to DEBUG, I'm attaching only a
>>> little fraction from our log file,
>>> you can see the whole exception in the file attached to this post:
>>>
>>> This message is printed in level of warning, yet it is just for tracing:
>>> invoked resolve! RequestParameters:
>>> [RequestParameters componentPath=4:registrationManagementForm
>>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>>> iorListener componentId=null behaviorId=1 urlDepth=-1
>>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>>> } onlyProcessIfPathActive=false]
>>> -----------------------------------------------------
>>>
>>> 2008-09-01 15:18:47,372 [WARN ]
>>> security.authentication.NiteWebRequestCycleProcessor -
>>> ===================== ENTER ==========
>>> ======================
>>> This message is printed in level of warning, yet it is just for tracing:
>>> invoked resolveRenderedPage! RequestParameters:
>>> [RequestParameters componentPath=4:registrationManagementForm
>>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>>> iorListener componentId=null behaviorId=1 urlDepth=-1
>>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>>> } onlyProcessIfPathActive=false]
>>> -----------------------------------------------------
>>>
>>> 2008-09-01 15:18:47,372 [DEBUG] apache.wicket.Session - Getting page
>>> [path = 4:registrationManagementForm, versionNumber = 0]
>>> 2008-09-01 15:18:47,376 [WARN ]
>>> security.authentication.NiteWebRequestCycleProcessor -
>>> -----------------------------------------------------
>>> completed resolveRenderedPage!======================== EXIT
>>> =============================
>>> 2008-09-01 15:18:47,377 [WARN ]
>>> security.authentication.NiteWebRequestCycleProcessor -
>>> ===================== ENTER ==========
>>> ======================
>>> This message is printed in level of warning, yet it is just for tracing:
>>> invoked respond(RuntimeException e, RequestCycle requestCycle)!
>>> -----------------------------------------------------
>>>
>>> 2008-09-01 15:18:47,377 [WARN ]
>>> security.authentication.NiteWebRequestCycleProcessor -
>>> ===================== ENTER ==========
>>> ======================
>>> This message is printed in level of warning, yet it is just for tracing:
>>> invoked onRuntimeException!
>>> -----------------------------------------------------
>>>
>>> 2008-09-01 15:18:47,377 [ERROR]
>>> security.authentication.NiteWebRequestCycleProcessor -
>>> onRuntimeException
>>> stack:
>>> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
>>> rendered page in session [pagemap=null,componentPath=4:r
>>> egistrationManagementForm,versionNumber=0]
>>> at
>>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:181)
>>> at
>>> il.org.nite.frm.security.authentication.NiteWebRequestCycleProcessor.resolve
>>>
>>> http://www.nabble.com/file/p19265678/prod_log.txt prod_log.txt
>>>
>> :-((:-((:-((:-((:-((
>> --
>> View this message in context:
>> http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285008.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
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.4 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
>
>
>
--
View this message in context: http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285219.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: PageExpiredException on production
Posted by Martijn Dashorst <ma...@gmail.com>.
Sounds like a bug in your NiteWebRequestCycleProcessor
Martijn
On Wed, Sep 3, 2008 at 10:29 AM, rivkash1 <ri...@nite.org.il> wrote:
>
> Hello again,
>
> does someone have any more ideas about our problem?
> It is very problematic to work in production when the users are thrown out
> with exception each hour...
>
> thanks
> Rebecca
>
>
> rivkash1 wrote:
>>
>> hello all,
>>
>> We are working with Wicket (1.3.4) on production for a couple of months.
>> It runs within jetty 6.1.7.
>> For some weeks, we are experiencing a strange PageExpiredException which
>> happens only on production env.
>>
>> It mostly happens on 2 main Pages in which the users submit the same form
>> in a rolling manner (i.e. fill the form fields, submit the form, the user
>> is redirected to the same page with a clean form and fills the form with
>> new data and so on repeatedly).
>>
>> It isn't a problem of session expiration because our session timeout is
>> set to 10 hours, this is the setting in our web.xml file:
>>
>> <session-config>
>> <session-timeout>600</session-timeout>
>> </session-config>
>>
>> We changed the logging level of Wicket to DEBUG, I'm attaching only a
>> little fraction from our log file,
>> you can see the whole exception in the file attached to this post:
>>
>> This message is printed in level of warning, yet it is just for tracing:
>> invoked resolve! RequestParameters:
>> [RequestParameters componentPath=4:registrationManagementForm
>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>> iorListener componentId=null behaviorId=1 urlDepth=-1
>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>> } onlyProcessIfPathActive=false]
>> -----------------------------------------------------
>>
>> 2008-09-01 15:18:47,372 [WARN ]
>> security.authentication.NiteWebRequestCycleProcessor -
>> ===================== ENTER ==========
>> ======================
>> This message is printed in level of warning, yet it is just for tracing:
>> invoked resolveRenderedPage! RequestParameters:
>> [RequestParameters componentPath=4:registrationManagementForm
>> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
>> iorListener componentId=null behaviorId=1 urlDepth=-1
>> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
>> } onlyProcessIfPathActive=false]
>> -----------------------------------------------------
>>
>> 2008-09-01 15:18:47,372 [DEBUG] apache.wicket.Session - Getting page
>> [path = 4:registrationManagementForm, versionNumber = 0]
>> 2008-09-01 15:18:47,376 [WARN ]
>> security.authentication.NiteWebRequestCycleProcessor -
>> -----------------------------------------------------
>> completed resolveRenderedPage!======================== EXIT
>> =============================
>> 2008-09-01 15:18:47,377 [WARN ]
>> security.authentication.NiteWebRequestCycleProcessor -
>> ===================== ENTER ==========
>> ======================
>> This message is printed in level of warning, yet it is just for tracing:
>> invoked respond(RuntimeException e, RequestCycle requestCycle)!
>> -----------------------------------------------------
>>
>> 2008-09-01 15:18:47,377 [WARN ]
>> security.authentication.NiteWebRequestCycleProcessor -
>> ===================== ENTER ==========
>> ======================
>> This message is printed in level of warning, yet it is just for tracing:
>> invoked onRuntimeException!
>> -----------------------------------------------------
>>
>> 2008-09-01 15:18:47,377 [ERROR]
>> security.authentication.NiteWebRequestCycleProcessor - onRuntimeException
>> stack:
>> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
>> rendered page in session [pagemap=null,componentPath=4:r
>> egistrationManagementForm,versionNumber=0]
>> at
>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:181)
>> at
>> il.org.nite.frm.security.authentication.NiteWebRequestCycleProcessor.resolve
>>
>> http://www.nabble.com/file/p19265678/prod_log.txt prod_log.txt
>>
> :-((:-((:-((:-((:-((
> --
> View this message in context: http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285008.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
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 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: PageExpiredException on production
Posted by rivkash1 <ri...@nite.org.il>.
Hello again,
does someone have any more ideas about our problem?
It is very problematic to work in production when the users are thrown out
with exception each hour...
thanks
Rebecca
rivkash1 wrote:
>
> hello all,
>
> We are working with Wicket (1.3.4) on production for a couple of months.
> It runs within jetty 6.1.7.
> For some weeks, we are experiencing a strange PageExpiredException which
> happens only on production env.
>
> It mostly happens on 2 main Pages in which the users submit the same form
> in a rolling manner (i.e. fill the form fields, submit the form, the user
> is redirected to the same page with a clean form and fills the form with
> new data and so on repeatedly).
>
> It isn't a problem of session expiration because our session timeout is
> set to 10 hours, this is the setting in our web.xml file:
>
> <session-config>
> <session-timeout>600</session-timeout>
> </session-config>
>
> We changed the logging level of Wicket to DEBUG, I'm attaching only a
> little fraction from our log file,
> you can see the whole exception in the file attached to this post:
>
> This message is printed in level of warning, yet it is just for tracing:
> invoked resolve! RequestParameters:
> [RequestParameters componentPath=4:registrationManagementForm
> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
> iorListener componentId=null behaviorId=1 urlDepth=-1
> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
> } onlyProcessIfPathActive=false]
> -----------------------------------------------------
>
> 2008-09-01 15:18:47,372 [WARN ]
> security.authentication.NiteWebRequestCycleProcessor -
> ===================== ENTER ==========
> ======================
> This message is printed in level of warning, yet it is just for tracing:
> invoked resolveRenderedPage! RequestParameters:
> [RequestParameters componentPath=4:registrationManagementForm
> pageMapName=null versionNumber=0 interfaceName=IActivePageBehav
> iorListener componentId=null behaviorId=1 urlDepth=-1
> parameters={random=0.14328683405517095,amp;wicket:ignoreIfNotActive=true
> } onlyProcessIfPathActive=false]
> -----------------------------------------------------
>
> 2008-09-01 15:18:47,372 [DEBUG] apache.wicket.Session - Getting page
> [path = 4:registrationManagementForm, versionNumber = 0]
> 2008-09-01 15:18:47,376 [WARN ]
> security.authentication.NiteWebRequestCycleProcessor -
> -----------------------------------------------------
> completed resolveRenderedPage!======================== EXIT
> =============================
> 2008-09-01 15:18:47,377 [WARN ]
> security.authentication.NiteWebRequestCycleProcessor -
> ===================== ENTER ==========
> ======================
> This message is printed in level of warning, yet it is just for tracing:
> invoked respond(RuntimeException e, RequestCycle requestCycle)!
> -----------------------------------------------------
>
> 2008-09-01 15:18:47,377 [WARN ]
> security.authentication.NiteWebRequestCycleProcessor -
> ===================== ENTER ==========
> ======================
> This message is printed in level of warning, yet it is just for tracing:
> invoked onRuntimeException!
> -----------------------------------------------------
>
> 2008-09-01 15:18:47,377 [ERROR]
> security.authentication.NiteWebRequestCycleProcessor - onRuntimeException
> stack:
> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
> rendered page in session [pagemap=null,componentPath=4:r
> egistrationManagementForm,versionNumber=0]
> at
> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:181)
> at
> il.org.nite.frm.security.authentication.NiteWebRequestCycleProcessor.resolve
>
> http://www.nabble.com/file/p19265678/prod_log.txt prod_log.txt
>
:-((:-((:-((:-((:-((
--
View this message in context: http://www.nabble.com/PageExpiredException-on-production-tp19265678p19285008.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