Hi, On Wed, Jul 1, 2015 at 4:31 PM, Urbani, Edmund <[email protected]> wrote:
> It could be caused by serialization, IF the serialized object graph is > sufficiently large (even without causing additional database access). But > in that case too, you very, very likely have objects in there, that you do > not want to actually serialize. > > Check members variables of your pages, custom components, custom session > object. Make sure all models are properly detached, and don't keep > references to database managed objects (that's what those > LoadableDetachableModels are good for). > To automate these checks make use of the IObjectChecker's at https://github.com/apache/wicket/tree/master/wicket-core/src/main/java/org/apache/wicket/core/util/objects/checker Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov > > Kind regards, > Edmund > > > On 07/01/2015 03:09 PM, Francois Meillet wrote: > > There is very little chance that the problem come from the serialization. > > Do you use the Open Session in View pattern ? with some > OpensessionInViewFilter filter ? > I guess when the page is serialized, some requests are done against the > database > to load collections or initialize proxies that have been touched. (look at > your lazy entities relations) > > If not you should use the famous LoadableDetachableModel > see http://ci.apache.org/projects/wicket/guide/7.x/guide/modelsforms.html > > François > > > > > > > Le 1 juil. 2015 à 11:51, Jagan Josyula > <[email protected]> > <[email protected]> a écrit : > > > Dear All, > I have a wicket page in which I have master-detail table on click of master > table row the child table displays the information. I have a lot of delay to > display the child information, when I check the log I found that the reason > for this is page serialization, if I remove the page serialization then the > display was very fast. > Could you please let me know what will cause delay during serialization of > the page? > [Page.java : 871] - ending request for page [Page class = XXXXXXXXXXXXXX, id > = 2, render count = 1], request > org.apache.wicket.protocol.http.servlet.ServletWebRequest@d91ac0<mailto:org.apache.wicket.protocol.http.servlet.ServletWebRequest@d91ac0> > <org.apache.wicket.protocol.http.servlet.ServletWebRequest@d91ac0> > [Wicket-PageSavingThread] DEBUG AsynchronousDataStore$PageSavingRunnable > [AsynchronousDataStore.java : 354] - Saving asynchronously: Entry > [sessionId=29CC3779D18B34D21704ED659326E51F, pageId=2]... > [Wicket-PageSavingThread] DEBUG DiskDataStore [DiskDataStore.java : 186] - > Storing data for page with id '2' in session with id > '29CC3779D18B34D21704ED659326E51F' > ["http-bio-8080"-exec-1] DEBUG PageAccessSynchronizer > [PageAccessSynchronizer.java : 195] - '"http-bio-8080"-exec-1' released lock > to page with id '2' > ["http-bio-8080"-exec-1] DEBUG PageAccessSynchronizer > [PageAccessSynchronizer.java : 346] - '"http-bio-8080"-exec-1' notifying > blocked threads > > Thanks & Regards > > Jagan > > > From: Martin Grigorov > Sent: Wednesday, July 01, 2015 2:42 PM > To: Jagan Josyula > Cc: [email protected] > Subject: Re: Wicket page serialization what causes delay? > > Hi, > > Please use users@ mailing list. > There is no sensitive information in your email. > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consultinghttps://twitter.com/mtgrigorov > > On Wed, Jul 1, 2015 at 11:57 AM, Jagan Josyula > <[email protected]<mailto:[email protected]> > <[email protected]>> wrote: > Dear Martin, > > I have a wicket page in which I have master-detail table on click of master > table row the child table displays the information. I have a lot of delay to > display the child information, when I check the log I found that the reason > for this is page serialization, if I remove the page serialization then the > display was very fast. > Could you please let me know what will cause delay in order to serialize the > page? > > [Page.java : 871] - ending request for page [Page class = XXXXXXXXXXXXXX, id > = 2, render count = 1], request > org.apache.wicket.protocol.http.servlet.ServletWebRequest@d91ac0<mailto:org.apache.wicket.protocol.http.servlet.ServletWebRequest@d91ac0> > <org.apache.wicket.protocol.http.servlet.ServletWebRequest@d91ac0> > [Wicket-PageSavingThread] DEBUG AsynchronousDataStore$PageSavingRunnable > [AsynchronousDataStore.java : 354] - Saving asynchronously: Entry > [sessionId=29CC3779D18B34D21704ED659326E51F, pageId=2]... > [Wicket-PageSavingThread] DEBUG DiskDataStore [DiskDataStore.java : 186] - > Storing data for page with id '2' in session with id > '29CC3779D18B34D21704ED659326E51F' > ["http-bio-8080"-exec-1] DEBUG PageAccessSynchronizer > [PageAccessSynchronizer.java : 195] - '"http-bio-8080"-exec-1' released lock > to page with id '2' > ["http-bio-8080"-exec-1] DEBUG PageAccessSynchronizer > [PageAccessSynchronizer.java : 346] - '"http-bio-8080"-exec-1' notifying > blocked threads > > > Thanks & Regards > > Jagan > > ________________________________ > > DISCLAIMER: > > This email may contain confidential information and is intended only for the > use of the specific individual(s) to which it is addressed. If you are not > the intended recipient of this email, you are hereby notified that any > unauthorized use, dissemination or copying of this email or the information > contained in it or attached to it is strictly prohibited. If you received > this message in error, please immediately notify the sender at Cyient and > delete the original message. > > > > > -- > > Mit freundlichen Grüßen > Edmund Urbani > Liland IT Team > > Email: [email protected] <[email protected]> > > Liland IT GmbH ...does IT better > Tel: +43 463 220111 > Fax: +43 463 220111-33 > Tel(GER): +49 221 65028588 > > Find us at Facebook http://facebook.com/Lilandit > http://green-badges.com > http://iventcloud.com > http://Lilandit.com > > <http://www.LilandIT.com> <http://www.LilandIT.com> > > Copyright © 2015, Liland IT GmbH > > Diese Mail enthaelt vertrauliche und/oder rechtlich geschuetzte > Informationen. > Wenn Sie nicht der richtige Adressat sind oder diese Email irrtuemlich > erhalten haben, informieren Sie bitte sofort den Absender und vernichten > Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe > dieser Mail ist nicht gestattet. > > This email may contain confidential and/or privileged information. > If you are not the intended recipient (or have received this email in > error) please notify the sender immediately and destroy this email. Any > unauthorised copying, disclosure or distribution of the material in this > email is strictly forbidden. >
