Probably serialization issue? And the browser still holds some old serialized classes? Or somwhere saved old sessions with old classes?
just guess. Regards, Pavol On Mon, Oct 31, 2011 at 7:27 PM, Martin Grigorov <[email protected]>wrote: > I guess only IE is problematic ? > > Create a quickstart and attach it to Jira > > On Mon, Oct 31, 2011 at 7:26 PM, Peter Diefenthaeler <[email protected]> > wrote: > > Hallo, > > I tried to upgrade my wicket projects to the new wicket 1.5.2 release > and now my tree component crashes. > > Any Idea? > > Thanks, Peter > > > > ERROR [http-bio-8037-exec-9]: Connection lost, give up responding. > > at > org.apache.wicket.DefaultExceptionMapper.internalMap(DefaultExceptionMapper.java:105) > > org.apache.wicket.protocol.http.servlet.ResponseIOException: > ClientAbortException: java.net.SocketException: Connection reset by peer: > socket write error > > at > org.apache.wicket.protocol.http.servlet.ServletWebResponse.flush(ServletWebResponse.java:254) > > at > org.apache.wicket.protocol.http.HeaderBufferingWebResponse.flush(HeaderBufferingWebResponse.java:92) > > at > org.apache.wicket.request.resource.AbstractResource.setResponseHeaders(AbstractResource.java:611) > > at > org.apache.wicket.request.resource.AbstractResource.respond(AbstractResource.java:485) > > at > org.apache.wicket.request.handler.resource.ResourceRequestHandler.respond(ResourceRequestHandler.java:77) > > at > org.apache.wicket.request.handler.resource.ResourceReferenceRequestHandler.respond(ResourceReferenceRequestHandler.java:105) > > at > org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:750) > > at > org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64) > > at > org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:252) > > at > org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:209) > > at > org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:280) > > at > org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:162) > > at > org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:218) > > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224) > > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169) > > at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) > > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) > > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929) > > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:405) > > at > org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:964) > > at > org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:515) > > at > org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:302) > > at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown > Source) > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown > Source) > > at java.lang.Thread.run(Unknown Source) > > Caused by: ClientAbortException: java.net.SocketException: Connection > reset by peer: socket write error > > at > org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:333) > > at > org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:299) > > at > org.apache.catalina.connector.Response.flushBuffer(Response.java:560) > > at > org.apache.catalina.connector.ResponseFacade.flushBuffer(ResponseFacade.java:303) > > at > org.apache.wicket.protocol.http.servlet.ServletWebResponse.flush(ServletWebResponse.java:250) > > ... 28 more > > Caused by: java.net.SocketException: Connection reset by peer: socket > write error > > at java.net.SocketOutputStream.socketWrite0(Native Method) > > at java.net.SocketOutputStream.socketWrite(Unknown Source) > > at java.net.SocketOutputStream.write(Unknown Source) > > at > org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:216) > > at > org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:437) > > at > org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:119) > > at > org.apache.coyote.http11.AbstractHttp11Processor.action(AbstractHttp11Processor.java:758) > > at org.apache.coyote.Response.action(Response.java:170) > > at > org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:328) > > ... 32 more > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
