]
Hasan Ceylan commented on JBREM-889:
------------------------------------
Please ignore the first patch. I have noticed I sent the file without resave in the editor
on my desktop.
If an exception occurs during invocation, usedPooled is not
decremented, thus leading into eventual remoting failures
----------------------------------------------------------------------------------------------------------------------
Key: JBREM-889
URL:
http://jira.jboss.com/jira/browse/JBREM-889
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.2.2.SP1
Environment: Should for all environments
Reporter: Hasan Ceylan
Attachments: remoting.patch, remoting.patch
Hello,
I guess this goes into Ron's area. Back in 2004 we had had a similar issue.
:)
In MicroSocketClientInvoker.transport(), having obtained a socket, if an exception occurs
during the invocation, the code that decrements usedPooled never gets called thus
inflating overtime. Eventually reaches 50, the hard limit which in turn, makes clients
unable to obtain a socket from pool or create a new one.
I guess, a try, finally block is needed starting right after successful socket acquired,
till where you decrement the usedPooled (marked with // Put socket back in pool for
reuse).
This will make sure the usedPooled is decremented.
I searched the JIRA and also found similar bug reports which I believe all should be
related.
Regards,
Hasan Ceylan
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: