From issues at jboss.org Wed Dec 18 09:31:32 2013 From: issues at jboss.org (Doug Grove (JIRA)) Date: Wed, 18 Dec 2013 09:31:32 -0500 (EST) Subject: [jboss-remoting-issues] [JBoss JIRA] (JBREM-1326) Socket read timeout is not set on Control Thread/Socket In-Reply-To: References: Message-ID: Doug Grove created JBREM-1326: --------------------------------- Summary: Socket read timeout is not set on Control Thread/Socket Key: JBREM-1326 URL: https://issues.jboss.org/browse/JBREM-1326 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss EAP 5 Reporter: Doug Grove It is possible for an unhandled exception to be thrown from the EJB container that causes orphaned control threads to accumulate: "control: Socket[addr=127.0.0.1,port=45892,localport=51040]" daemon prio=3 tid=0x056c2800 nid=0x2002 runnable [0x5ba4f000] java.lang.Thread.State: RUNNABLE java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) java.net.SocketInputStream.read(SocketInputStream.java:182) java.io.FilterInputStream.read(FilterInputStream.java:66) The socket read blocks indefinitely as there is no timeout. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 18 09:31:33 2013 From: issues at jboss.org (Doug Grove (JIRA)) Date: Wed, 18 Dec 2013 09:31:33 -0500 (EST) Subject: [jboss-remoting-issues] [JBoss JIRA] (JBREM-1326) Socket read timeout is not set on Control Thread/Socket In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBREM-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Grove reassigned JBREM-1326: --------------------------------- Assignee: Ron Sigal > Socket read timeout is not set on Control Thread/Socket > ------------------------------------------------------- > > Key: JBREM-1326 > URL: https://issues.jboss.org/browse/JBREM-1326 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: JBoss EAP 5 > Reporter: Doug Grove > Assignee: Ron Sigal > > It is possible for an unhandled exception to be thrown from the EJB container that causes orphaned control threads to accumulate: > "control: Socket[addr=127.0.0.1,port=45892,localport=51040]" daemon prio=3 tid=0x056c2800 nid=0x2002 runnable [0x5ba4f000] > java.lang.Thread.State: RUNNABLE > java.net.SocketInputStream.socketRead0(Native Method) > java.net.SocketInputStream.read(SocketInputStream.java:129) > java.net.SocketInputStream.read(SocketInputStream.java:182) > java.io.FilterInputStream.read(FilterInputStream.java:66) > The socket read blocks indefinitely as there is no timeout. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira