Could not render css /eXoResources/skin/MySkin-lt.css

[jferreyram]

Hi everyone and thank you for your answers

I've developed a portal using GateIn, but it fails and show me the follow message in log:

2010-05-26 21:43:26,759 ERROR [org.exoplatform.portal.

application.ResourceRequestFilter]  Could not render css /eXoResources/skin/MySkin-lt.css
ClientAbortException:  java.net.SocketException: Connection reset
     at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:399)
     at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:449)
     at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349)
     at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:422)
     at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:411)
     at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:89)
     at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:83)
     at org.exoplatform.portal.application.ResourceRequestFilter$1.write(ResourceRequestFilter.java:98)
     at org.exoplatform.portal.resource.CachedStylesheet.writeTo(CachedStylesheet.java:71)
     at org.exoplatform.portal.resource.SkinService.renderCSS(SkinService.java:345)
     at org.exoplatform.portal.application.ResourceRequestFilter.doFilter(ResourceRequestFilter.java:127)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
     at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
     at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
     at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
     at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
     at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:436)
     at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:384)
     at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
     at java.lang.Thread.run(Thread.java:619)
Caused by: java.net.SocketException: Connection reset
    at  java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96)
     at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
     at org.apache.coyote.ajp.AjpProcessor$SocketOutputBuffer.doWrite(AjpProcessor.java:1236)
     at org.apache.coyote.Response.doWrite(Response.java:567)
     at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:394)
     ... 30 more

This exception throws many times during portal loading, but I don't know why. Can anyone help me, please?

[trong.tran]

Normally this exception should not prevent the GateIn to work ( can you confirm in your side ? ), it often occurs while server is trying to send data to a client's HTTP connection which has been closed. In this case, GateIn could ignore to keep it silent and does not annoy the log anyway

I'm not sure how this problem can be exactly in your case but let try to check the HTTP session timeout setting in your Tomcat web server