You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Bushby <mi...@yahoo.com> on 2007/09/26 03:42:55 UTC
Page Expired Clustering?
I am having trouble with a wicket application returning page expired when any
link or button is clicked on. When the application is deployed on a server
with an Apache Weblogic integration the application works fine. When the
application is deployed on a server with an Apache Weblogic cluster all
links and buttons return page expired. I am using Wicket 1.2.6 and JDK 1.4.
The wicket application is also integrated with hibernate and Spring. Any
help would be greatly appreciated.
--
View this message in context: http://www.nabble.com/Page-Expired-Clustering--tf4519473.html#a12892290
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: Page Expired Clustering?
Posted by wicket21 <ko...@yahoo.com>.
Hi,
does anyone know what is the equivelant of this solution that would work
with tomcat?
We have the same problem using Wicket 1.2.6 with Tomcat 5.5.25, and the info
at http://cwiki.apache.org/WICKET/tomcat-clustering.html doesn't really
work.
We do a simple test with 2 tomcats behind an Apache (using mod_jk) and
sessions do not replicate correctly from one tomcat to the other.
Any help would be welcome...
Bushby wrote:
>
> Thanks for the push in the right direction. I believe we have the problem
> solved. We needed to add a session-descriptor in the weblogic.xml file.
>
> <session-param>
> <param-name>PersistentStoreType</param-name>
> <param-value>replicated_if_clustered</param-value>
> </session-param>
>
> Again thanks for the quick response. You helped save the wicket project.
> It was hours from going to struts because of time issues.
>
>
>
> Bushby wrote:
>>
>> The home page gets displayed and the only 2 things on the page are links
>> to other pages. One of the links goes to a page with 2 TextFields, 2
>> DatePickers, and a button. The other page has fields to capture typical
>> credit card information. The form for this page has a Spring service but
>> it does not hold reference. It asks the application for the bean. All
>> pojo's are Serializable.
>>
>>
>>
>> Matej Knopp-2 wrote:
>>>
>>> Also, are you sure everything on you page and in session is
>>> serializable?
>>>
>>> -Matej
>>>
>>> On 9/26/07, Eelco Hillenius <ee...@gmail.com> wrote:
>>>> > I am having trouble with a wicket application returning page expired
>>>> when any
>>>> > link or button is clicked on. When the application is deployed on a
>>>> server
>>>> > with an Apache Weblogic integration the application works fine. When
>>>> the
>>>> > application is deployed on a server with an Apache Weblogic cluster
>>>> all
>>>> > links and buttons return page expired. I am using Wicket 1.2.6 and
>>>> JDK 1.4.
>>>> > The wicket application is also integrated with hibernate and Spring.
>>>> Any
>>>> > help would be greatly appreciated.
>>>>
>>>> Do you use sticky sessions? Make sure the HttpSession gets replicated.
>>>>
>>>> Eelco
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>>>
>>>
>>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Page-Expired-Clustering--tp12892290p15306703.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: Page Expired Clustering?
Posted by Bushby <mi...@yahoo.com>.
Thanks for the push in the right direction. I believe we have the problem
solved. We needed to add a session-descriptor in the weblogic.xml file.
<session-param>
<param-name>PersistentStoreType</param-name>
<param-value>replicated_if_clustered</param-value>
</session-param>
Again thanks for the quick response. You helped save the wicket project.
It was hours from going to struts because of time issues.
Bushby wrote:
>
> The home page gets displayed and the only 2 things on the page are links
> to other pages. One of the links goes to a page with 2 TextFields, 2
> DatePickers, and a button. The other page has fields to capture typical
> credit card information. The form for this page has a Spring service but
> it does not hold reference. It asks the application for the bean. All
> pojo's are Serializable.
>
>
>
> Matej Knopp-2 wrote:
>>
>> Also, are you sure everything on you page and in session is serializable?
>>
>> -Matej
>>
>> On 9/26/07, Eelco Hillenius <ee...@gmail.com> wrote:
>>> > I am having trouble with a wicket application returning page expired
>>> when any
>>> > link or button is clicked on. When the application is deployed on a
>>> server
>>> > with an Apache Weblogic integration the application works fine. When
>>> the
>>> > application is deployed on a server with an Apache Weblogic cluster
>>> all
>>> > links and buttons return page expired. I am using Wicket 1.2.6 and
>>> JDK 1.4.
>>> > The wicket application is also integrated with hibernate and Spring.
>>> Any
>>> > help would be greatly appreciated.
>>>
>>> Do you use sticky sessions? Make sure the HttpSession gets replicated.
>>>
>>> Eelco
>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Page-Expired-Clustering--tf4519473.html#a12902031
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: Page Expired Clustering?
Posted by Bushby <mi...@yahoo.com>.
The home page gets displayed and the only 2 things on the page are links to
other pages. One of the links goes to a page with 2 TextFields, 2
DatePickers, and a button. The other page has fields to capture typical
credit card information. The form for this page has a Spring service but it
does not hold reference. It asks the application for the bean. All pojo's
are Serializable.
Matej Knopp-2 wrote:
>
> Also, are you sure everything on you page and in session is serializable?
>
> -Matej
>
> On 9/26/07, Eelco Hillenius <ee...@gmail.com> wrote:
>> > I am having trouble with a wicket application returning page expired
>> when any
>> > link or button is clicked on. When the application is deployed on a
>> server
>> > with an Apache Weblogic integration the application works fine. When
>> the
>> > application is deployed on a server with an Apache Weblogic cluster all
>> > links and buttons return page expired. I am using Wicket 1.2.6 and JDK
>> 1.4.
>> > The wicket application is also integrated with hibernate and Spring.
>> Any
>> > help would be greatly appreciated.
>>
>> Do you use sticky sessions? Make sure the HttpSession gets replicated.
>>
>> Eelco
>>
>> ---------------------------------------------------------------------
>> 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
>
>
>
--
View this message in context: http://www.nabble.com/Page-Expired-Clustering--tf4519473.html#a12901368
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: Page Expired Clustering?
Posted by Matej Knopp <ma...@gmail.com>.
Also, are you sure everything on you page and in session is serializable?
-Matej
On 9/26/07, Eelco Hillenius <ee...@gmail.com> wrote:
> > I am having trouble with a wicket application returning page expired when any
> > link or button is clicked on. When the application is deployed on a server
> > with an Apache Weblogic integration the application works fine. When the
> > application is deployed on a server with an Apache Weblogic cluster all
> > links and buttons return page expired. I am using Wicket 1.2.6 and JDK 1.4.
> > The wicket application is also integrated with hibernate and Spring. Any
> > help would be greatly appreciated.
>
> Do you use sticky sessions? Make sure the HttpSession gets replicated.
>
> Eelco
>
> ---------------------------------------------------------------------
> 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: Page Expired Clustering?
Posted by Bushby <mi...@yahoo.com>.
I am pretty certain we use sticky sessions. I am checking with our server
admins.
Eelco Hillenius wrote:
>
>> I am having trouble with a wicket application returning page expired when
>> any
>> link or button is clicked on. When the application is deployed on a
>> server
>> with an Apache Weblogic integration the application works fine. When the
>> application is deployed on a server with an Apache Weblogic cluster all
>> links and buttons return page expired. I am using Wicket 1.2.6 and JDK
>> 1.4.
>> The wicket application is also integrated with hibernate and Spring. Any
>> help would be greatly appreciated.
>
> Do you use sticky sessions? Make sure the HttpSession gets replicated.
>
> Eelco
>
> ---------------------------------------------------------------------
> 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/Page-Expired-Clustering--tf4519473.html#a12901809
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: Page Expired Clustering?
Posted by Eelco Hillenius <ee...@gmail.com>.
> I am having trouble with a wicket application returning page expired when any
> link or button is clicked on. When the application is deployed on a server
> with an Apache Weblogic integration the application works fine. When the
> application is deployed on a server with an Apache Weblogic cluster all
> links and buttons return page expired. I am using Wicket 1.2.6 and JDK 1.4.
> The wicket application is also integrated with hibernate and Spring. Any
> help would be greatly appreciated.
Do you use sticky sessions? Make sure the HttpSession gets replicated.
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org