[jboss-jira] [JBoss JIRA] Updated: (JBREM-1282) ServerInvoker does not close StreamHandler in the case of "addstreamcallback"
[
https://issues.jboss.org/browse/JBREM-1282?page=com.atlassian.jira.plugin...
]
Ron Sigal updated JBREM-1282:
-----------------------------
Attachment: jboss-remoting.jar
I've verified that StreamHandler.close() leaves open connections in the
MicroSocketClientInvoker connection pool. I've added a call to
streamClient.disconnect();
to StreamHandler.close(), which results in the destruction of the MicroSocketClientInvoker
and its connection pool.
Ramesh, could you see if the attached jboss-remoting.jar solves your problem? Thanks.
ServerInvoker does not close StreamHandler in the case of
"addstreamcallback"
-----------------------------------------------------------------------------
Key: JBREM-1282
URL: https://issues.jboss.org/browse/JBREM-1282
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.5.4.SP1, 2.2.4
Reporter: Ramesh Reddy
Assignee: Ron Sigal
Fix For: 2.5.4.SP2, 2.2.4.SP1
Attachments: jboss-remoting.jar, JBossRemoting.patch
This started out http://community.jboss.org/thread/163742 and in Teiid project we created
a JIRA for this https://issues.jboss.org/browse/TEIID-1511
while debugging for this issue, I found that in ServerInvoker, for
"AddStreamCallback" block in the "handleInternalInvocation" method it
does not close the stream handler once it is done. This results in open socket connection.
I am not sure if this connection closes after some idle time, but in our case user is
rapidly going through deploy and undeploy action, results in too many open files. I
created a patch and tested with our usecase, the problem no longer exists. Please find
attached patch
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira