Good question, not too many in here use Weblogic (most people usually
either are on a plain Tomcat setup)
Which strategies do you use for storing the pagination data, do you use
own own datamodel, which basically delivers one page after the other,
or do you store everything in a big datastructure served to the
datatable immediately.
If you do the second, your data structure might become to big for in
memory delivery. I do not know Weblogic, but is there a change
that the app server caches some of that stuff into a physical swap file,
or is there a chance that serialisation, it also could be that
serialisation needs longer on Beas server.
Try following strategies,
a) Increase the mem of the app server
b) Try a different data serving strategy, moving to an explicit
page serving data model might be exactly what you need (one request
per page with the exact number of elements displayed in the page)
There is a wiki entry on how to implement such a datamodel in the
myfaces wiki.
c) If nothing works out, you have to start the good ole profiler to
see what is going on.
Werner
Emily Gu schrieb:
Hi,
I have a <t:dataTable> deployed on Weblogic 8.1 sp4. The table is
bounded to a backing bean in session. It is so slow when I click to next
page. The data should be in memory already. It took no time in Tomcat
when paginating to the next page. But Weblogic 8.1 sp4 is thinking very
long to get to next page. Do you know anything I could be done wrong in
server setup in causing this? I know my question is off topic. But BEA
seems have the worse support. I have never gotten any answers from them.
Any help is very much appreciated.
Thanks,
Emily
