Bugs item #637880, was opened at 2002-11-13 11:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=637880&group_id=22866
Category: JBossServer Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Jim Snyder (jdsnyderii) Assigned to: Nobody/Anonymous (nobody) Summary: RMI sockets not closed Initial Comment: RMI sockets for the RMIObjectPort on conatiner configurations are not being closed and consume huge numbers of sockets. We have been able to show that for all releases of 2.4.x that RMI connections are terminated rather than closed. For example, if I telnet to the RMI port and close the connection correctly, all the sockets go away correctly. A large question is why are all of these sockets being created in the first place if everything is in the same VM? Applies to jdks (1.3 and 1.4) Applies to Win2K and Linux ---------------------------------------------------------------------- >Comment By: Jim Snyder (jdsnyderii) Date: 2002-11-14 14:35 Message: Logged In: YES user_id=424928 The behavior is actually correct. ---------------------------------------------------------------------- Comment By: Jimmy Wan (jwan) Date: 2002-11-13 12:22 Message: Logged In: YES user_id=648382 I have also observed this behavior, even though all standardjboss.xml and jboss.xml container-configuration elements contained container-invoker-conf subelements where Optimized was "True". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=637880&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
