[JBoss JIRA] Created: (JBREM-1282) ServerInvoker does not close StreamHandler in the case of "addstreamcallback"
9:56 p.m.
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.1 (Flounder)
Reporter: Ramesh Reddy
Attachments: 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
9:56 p.m.
New subject: [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...
]
Ramesh Reddy updated JBREM-1282:
--------------------------------
Attachment: JBossRemoting.patch
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.1 (Flounder)
Reporter: Ramesh Reddy
Attachments: 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
10:13 p.m.
New subject: [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:
-----------------------------
Assignee: Ron Sigal
Fix Version/s: 2.5.4.SP2
2.2.4.SP1
Affects Version/s: 2.5.4.SP1
2.2.4
(was: 2.5.1 (Flounder))
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: 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
10:15 p.m.
New subject: [JBoss JIRA] Commented: (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 commented on JBREM-1282:
----------------------------------
Hi Ramesh,
Wow, I didn't know anyone at JBoss was using the stream facility. Ok, I've
assigned fix version. It will be done.
-Ron
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: 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
1:42 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-1282) ServerInvoker does not close StreamHandler in the case of "addstreamcallback"
[
https://issues.jboss.org/browse/JBREM-1282?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on JBREM-1282:
-------------------------------------
I just use the "profile service" in the AS, in this it looks like it uses the
"jboss.remoting:service=Connector,transport=socket" in its DeploymentManager,
thus even though it is local to the VM, it starts making the calls over socket. I am not
sure how I can configure it to use "local" connection
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: 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
1:46 a.m.
New subject: [JBoss JIRA] Commented: (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 commented on JBREM-1282:
----------------------------------
Hmmm. Remoting should use a local connection by default to make an "intra-jvm"
invocation. What else can you tell my about the configuration?
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: 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
2:04 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-1282) ServerInvoker does not close StreamHandler in the case of "addstreamcallback"
[
https://issues.jboss.org/browse/JBREM-1282?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on JBREM-1282:
-------------------------------------
Look at server/default/conf/bootstrap/profile.xml, for "ProfileService"
See /server/default/deploy/profileservice-jboss-beans.xml, look for
"DeploymentManager", which is installed in ProfileService. This uses
"ConnectorMBean" which has the socket config.
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: 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
8:54 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-1282) ServerInvoker does not close StreamHandler in the case of "addstreamcallback"
[
https://issues.jboss.org/browse/JBREM-1282?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on JBREM-1282:
-------------------------------------
I tested deploying a WAR file using the admin-console it uses the same path, so you see
same issue if you deploy enough WAR files.
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: 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
6:05 a.m.
New subject: [JBoss JIRA] Commented: (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 commented on JBREM-1282:
----------------------------------
I don't think it's appropriate for ServerInvoker to close the StreamHandler, since
the StreamInvocationHandler application code might want to continue reading from the
stream on another thread. Actually, the StreamInvocationHandler should close the
StreamHandler. But a quick inspection of
org.jboss.deployment.services.DeploymentManagerService, which accesses the StreamHandler,
suggests that the StreamHandler is, in fact, being closed. I'll have to take a closer
look.
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: 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
6:14 a.m.
New subject: [JBoss JIRA] Commented: (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 commented on JBREM-1282:
----------------------------------
I think I see the problem. StreamHandler.close() should call streamClient.close(), which
would result in closing the socket pool. I'll play a bit to verify that that's
where the problem is.
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: 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
5:39 a.m.
New subject: [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
4:34 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-1282) ServerInvoker does not close StreamHandler in the case of "addstreamcallback"
[
https://issues.jboss.org/browse/JBREM-1282?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on JBREM-1282:
-------------------------------------
Ron, I replaced this jar with jar in 'common/lib", however the error still
exists. If you want to try deploy a war file through "admin-console" then do a
"lsof" using the PID of the process. Each time after a deploy a new localhost
socket is in LISTEN state.
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
9:44 p.m.
New subject: [JBoss JIRA] Commented: (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 commented on JBREM-1282:
----------------------------------
The discussion about this issue has been taking place on JBPAPP-6396, which was cloned
from this one. Please see that issue for more information. To summarize, though, the
real solution was to force the org.jboss.remoting.stream.StreamServer to use the local
transport for in-jvm connections. See JBREM-1288.
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
9:46 p.m.
New subject: [JBoss JIRA] Resolved: (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 resolved JBREM-1282.
------------------------------
Resolution: Done
On JBPAPP-6396, Ramesh Reddy confirmed the fix for JBREM-1288 fixed the problem.
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
10:44 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-1282) ServerInvoker does not close StreamHandler in the case of "addstreamcallback"
[
https://issues.jboss.org/browse/JBREM-1282?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on JBREM-1282:
-------------------------------------
Please remove this INFO line or make this as debug
20:38:58,535 INFO [ServerInvoker] SocketServerInvoker[localhost.localdomain:4446]
handler: org.jboss.profileservice.remoting.ProfileServiceInvocationHandler@f02d8f
20:38:58,545 INFO [ServerInvoker] SocketServerInvoker[localhost.localdomain:4446]
handler: org.jboss.profileservice.remoting.ProfileServiceInvocationHandler@f02d8f
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
11:22 p.m.
New subject: [JBoss JIRA] Commented: (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 commented on JBREM-1282:
----------------------------------
re: "Please remove this INFO line or make this as debug"
It doesn't exist in the released version.
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
4745
days inactive
4767
days old
15 comments
2 participants
participants (2)
-
Ramesh Reddy (JIRA) -
Ron Sigal (JIRA)