Bug 779980 (SOA-2340) - Closing connections to Teiid may result in a stack trace written to the server's log file
Summary: Closing connections to Teiid may result in a stack trace written to the serve...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2340
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0.ER3
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-22 13:49 UTC by Len DiMaggio
Modified: 2010-10-21 19:04 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-21 19:04:52 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2340 0 Major Closed Closing connections to Teiid may result in a stack trace written to the server's log file 2013-11-18 16:57:32 UTC

Description Len DiMaggio 2010-09-22 13:49:47 UTC 
project_key: SOA

Platform JIRA for TEIID project JIRA: TEIID-1269
Comment 1 Len DiMaggio 2010-09-22 13:50:23 UTC 
Link: Added: This issue depends TEIID-1269
Comment 2 Len DiMaggio 2010-09-24 13:54:38 UTC 
One way to force the error is to halt (control/C) an adminshell session:

2010-09-24 09:51:11,017 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)
Comment 3 Van Halbert 2010-09-27 13:15:16 UTC 
Teiid has resolved this issue for ER2.
Comment 4 Len DiMaggio 2010-10-04 13:53:07 UTC 
Still an issue in ER2

2010-10-04 09:50:50,246 ERROR [org.teiid.TRANSPORT] (New I/O server worker #1-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:322)
        at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:281)
        at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)
        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)
Comment 5 Steven Hawkins 2010-10-05 15:55:29 UTC 
There was confusion about what build was taken for ER2.  The fix for this went in on the 24th.  ER2 was built off of 23rd.  So this won't be fixed until ER3.
Comment 6 Van Halbert 2010-10-05 16:58:24 UTC 
Mix up on when the change was committed to Teiid.  This change should be in ER3.
Comment 7 Len DiMaggio 2010-10-21 19:04:52 UTC 
Verified fixed in 5.1 ER3 build.
Note You need to log in before you can comment on or make changes to this bug.