[ http://issues.apache.org/jira/browse/NET-145?page=all ]
Rory Winston closed NET-145. ---------------------------- Fix Version/s: 2.0 Resolution: Fixed This issue is fixed in 2.0. > Deadlock in TelnetInputStream > ----------------------------- > > Key: NET-145 > URL: http://issues.apache.org/jira/browse/NET-145 > Project: Commons Net > Issue Type: Bug > Affects Versions: 1.4 Final > Environment: Heavy mutlithreaded environment using Jakarta VFS (which > uses Commons Net) for ftp file transfers > Reporter: Norbert Seekircher > Fix For: 2.0 > > > "Sometimes" single threads of our application (each thread transfering data > from ftp servers) get locked forever. When monitoring our tool with JConsole, > I can see that such a thread usually hangs at > org.apache.commons.net.telnet.TelnetInputStream, line 339. > This line contains the statement > __queue.wait(); > Unfortunately I haven't found a way to reproduce this issue, it just happens > about once a day (while running 24 hours and transfering about 50000 files). > As a quick and dirty workaround: What do you think about replacing this line > with something like > long startTime = System.currentTimeMillis(); > __queue.wait(60000); > if ((System.currentTimeMillis() - startTime) > 55000) { > throw new InterruptedException("Unknown strange and nasty blocker > detected"); > } > So at least it would not just block the thread. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]