It's not possible to help you without knowing seeing more code. What are the items you are creating? It's probably the models itself that cause the outofmemory error, you are likely to be loading someting huge.
-Matej On Dec 17, 2007 6:12 AM, kenixwong <[EMAIL PROTECTED]> wrote: > > hi, anyone can help ? > > i was using the Eclipse 3.2.2, jdk1.6.0, jetty 6.0.2, wicket 1.2.4. Once i > loop a report page, the eclipse console and page return the error as above. > How can i solve it .... > > I had tryed to reset the eclispe.ini > (http://bugs.sakaiproject.org/confluence/display/ARW/Eclipse+startup+memory+settings) > too. > > > > here is the error > > ... > ... > ... > at > wicket.extensions.markup.html.repeater.refreshing.RefreshingView$1.newItem(RefreshingView.java:108) > at > wicket.extensions.markup.html.repeater.refreshing.DefaultItemReuseStrategy$1.next(DefaultItemReuseStrategy.java:73) > at > wicket.extensions.markup.html.repeater.refreshing.RefreshingView.addItems(RefreshingView.java:191) > at > wicket.extensions.markup.html.repeater.refreshing.RefreshingView.internalOnAttach(RefreshingView.java:117) > at wicket.Component.internalAttach(Component.java:2579) > at wicket.MarkupContainer.internalAttach(MarkupContainer.java:341) > at wicket.MarkupContainer.internalAttach(MarkupContainer.java:354) > at wicket.MarkupContainer.internalAttach(MarkupContainer.java:354) > at wicket.Page.renderPage(Page.java:383) > at > wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:160) > at > wicket.request.target.component.PageRequestTarget.respond(PageRequestTarget.java:60) > at > wicket.request.compound.DefaultResponseStrategy.respond(DefaultResponseStrategy.java:49) > at > wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond(AbstractCompoundRequestCycleProcessor.java:66) > at > wicket.RequestCycle.doProcessEventsAndRespond(RequestCycle.java:902) > at wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:929) > at wicket.RequestCycle.step(RequestCycle.java:1010) > at wicket.RequestCycle.steps(RequestCycle.java:1084) > at wicket.RequestCycle.request(RequestCycle.java:454) > at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:219) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:459) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:231) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:629) > at > org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:453) > > > Any solution ?? > > > thanks in advance.. > -- > View this message in context: > http://www.nabble.com/java.lang.OutOfMemoryError%3A-Java-heap-space-tp14370078p14370078.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
