1. Sebastian Sebastian
  2. scm-manager

Issues

Issue #180 wontfix

Exceptions in Logfile

mrtent
created an issue

Hello,

I just had a look at the lof file and it is filled with exceptions. Everything SEEMS to run fine however.

This is from when i logon (i think):

14:20:18.191 [qtp1852565824-22] ERROR sonia.scm.util.IOUtil - null org.eclipse.jetty.io.EofException: null at org.eclipse.jetty.http.HttpGenerator.flushBuffer(HttpGenerator.java:952) ~[na:na] at org.eclipse.jetty.server.AbstractHttpConnection.flushResponse(AbstractHttpConnection.java:612) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.AbstractHttpConnection$Output.close(AbstractHttpConnection.java:1001) ~[na:na] at sonia.scm.util.IOUtil.close(IOUtil.java:119) [scm-core-1.16.jar:na] at sonia.scm.filter.GZipResponseStream.close(GZipResponseStream.java:155) [scm-core-1.16.jar:na] at sonia.scm.util.IOUtil.close(IOUtil.java:119) [scm-core-1.16.jar:na] at sonia.scm.filter.GZipResponseWrapper.finishResponse(GZipResponseWrapper.java:98) [scm-core-1.16.jar:na] at sonia.scm.filter.GZipFilter.doFilter(GZipFilter.java:112) [scm-core-1.16.jar:na] at sonia.scm.web.filter.HttpFilter.doFilter(HttpFilter.java:102) [scm-core-1.16.jar:na] at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163) [guice-servlet-3.0.jar:na] at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58) [guice-servlet-3.0.jar:na] at sonia.scm.filter.BaseUrlFilter.doFilter(BaseUrlFilter.java:100) [classes/:na] at sonia.scm.web.filter.HttpFilter.doFilter(HttpFilter.java:102) [scm-core-1.16.jar:na] at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163) [guice-servlet-3.0.jar:na] at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58) [guice-servlet-3.0.jar:na] at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118) [guice-servlet-3.0.jar:na] at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113) [guice-servlet-3.0.jar:na] at sonia.scm.boot.BootstrapFilter.doFilter(BootstrapFilter.java:104) [classes/:na] at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1332) [jetty-servlet-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:477) [jetty-servlet-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) [jetty-security-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1031) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:406) [jetty-servlet-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:965) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.Server.handle(Server.java:348) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:452) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:884) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:938) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:630) [jetty-http-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230) [jetty-http-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:77) [jetty-server-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.io.nio.SslConnection.handle(SslConnection.java:191) [jetty-io-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:620) [jetty-io-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:46) [jetty-io-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:603) [jetty-util-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:538) [jetty-util-7.6.4.v20120524.jar:7.6.4.v20120524] at java.lang.Thread.run(Unknown Source) [na:1.7.0_04] Caused by: java.nio.channels.ClosedChannelException: null at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(Unknown Source) ~[na:1.7.0_04] at sun.nio.ch.SocketChannelImpl.write(Unknown Source) ~[na:1.7.0_04] at org.eclipse.jetty.io.nio.ChannelEndPoint.flush(ChannelEndPoint.java:288) ~[na:na] at org.eclipse.jetty.io.nio.SelectChannelEndPoint.flush(SelectChannelEndPoint.java:355) [jetty-io-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.io.nio.SslConnection.process(SslConnection.java:332) [jetty-io-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.io.nio.SslConnection.access$900(SslConnection.java:43) [jetty-io-7.6.4.v20120524.jar:7.6.4.v20120524] at org.eclipse.jetty.io.nio.SslConnection$SslEndPoint.flush(SslConnection.java:673) ~[na:na] at org.eclipse.jetty.http.HttpGenerator.flushBuffer(HttpGenerator.java:888) ~[na:na] ... 42 common frames omitted

Any idea what is going wrong here?

Comments (6)

  1. mrtent reporter

    I'll try to describe my setup.. I have SCM-Manager running as a service on a Windows 7 professional 64-bit VM. The VM runs in vmware player on another Windows 7 professional 64-bit machine. The VM has it's own IP-adres in the local network. A router which is connected to the internet forwards port 8181 to this machine. I'm not sure if this qualifies as a reverse proxy. The router's internet addres is static, however there is no domain name pointing to it yet. I have set up SSL for SCM-Manager following your instructions for a self-signed certificate. As FQDN I used the static internet IP-address.

    I don't understand what you mean by 'using the webapp with an other application server'.

    I did find out the exact moment the exeption occurs: There should be no sessions active. All browsers closed. Then using IE9 (did not test other versions of IE) I go to https://staticinternetip:8181/scm. Now I get the warning that the cerificate is not trusted. I choose to continue anyway and exactly at this moment the exeption occurs. Even before I logon. It doesn't seem to happen with Chome or Opera. It also doesn't seem to happen on the SCM-Manager machine itself. Also I need to close all session for it to happen again.

    Hope this helps. If you need more information let me know.

  2. Sebastian Sebastian repo owner

    I've tried to reproduce this issue, but without success. I think the problem is related through your network setup. Sorry, but i can't setup a environment related to yours and i can not hide or fix the exception. The only thing you can do is to hide exceptions from sonia.scm.util.IOUtil. To hide the exceptions, edit the logging.xml file in the conf folder of the server and add the following line after the sonia.scm log level configuration:

      <logger name="sonia.scm.util.IOUtil" level="FATAL" />
    

    This is not a nice workaround, because you could miss relevant exceptions. You could try to check for network errors in your setup, but i can not help you to find such a error.

  3. Log in to comment