Hi,
On Fri, Oct 18, 2013 at 9:50 PM, uwe schaefer <u...@codesmell.de> wrote:
> On 18.10.2013 09:03, Martin Grigorov wrote:
>
> Hi Martin,
>
>
> Can you give more details about the setup and the problem ?
>>
>
> of course. we use two Tomcat6 with clustering enabled (Backup-Manager)
> with apache in front using sticky sessions.
>
> when redeploying, we restart tomcat.
>
> Now when one tomcat is restarted and the wicket initializes, there is a
> time-window in which wicket is not yet fully initialized (and our DataStore
> is not yet set), yet the application is already bound as an
> UnbindingListener.
>
> This is where we see sessionUnbound being called, which as i mentioned,
> causes a default datastore (disk) being wrapped in an AsyncDatastore and
> the damage is done:
> Application:478
> public void sessionUnbound(final String sessionId){
> internalGetPageManager().**sessionExpired(sessionId);
> }
>
> Application:1387
> pageManager = pageManagerProvider.get(**getPageManagerContext());
>
> DefaultPageManagerProvider:58
> if (dataStore.canBeAsynchronous()**)
> {
> int capacity = storeSettings.**getAsynchronousQueueCapacity()**;
> dataStore = new AsynchronousDataStore(**dataStore, capacity);
> }
>
> and then AsynchronousDataStore:97
> pageSavingThread.start();
>
> what other info in particular are you looking for?
i could create a quickstart and attach it to a jira issue.
I hope the ticket will describe better what "and the damage is done"
actually means.
I'm not sure whether it is just me (there are no other responses in this
thread) but your problem description emphasis more on Wicket's code than on
what really is the problem you face.
>
>
> cu uwe
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail:
> users-unsubscribe@wicket.**apache.org<users-unsubscr...@wicket.apache.org>
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
