Closing connections to Teiid may result in a stack trace written to the server's log
file
-----------------------------------------------------------------------------------------
Key: TEIID-1269
URL:
https://jira.jboss.org/browse/TEIID-1269
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1
Reporter: Paul Nittel
Assignee: Steven Hawkins
Fix For: 7.1.1
It has been noticed by several people that the server will, on occasion, write a stack
trace (like the one below) to the server's log file. It appears to be benign and, so,
it is possible the exception should be noted at a severity less than ERROR.
Of course, eliminating it altogether might also be possible, once it's been
investigated.
2010-09-20 22:04:56,033 ERROR [org.teiid.TRANSPORT] (New I/O server worker #2-2) Unhandled
exception, closing client instance
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:251)
at sun.nio.ch.IOUtil.read(IOUtil.java:218)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:254)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:313)
at
org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:272)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:192)
at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira