[OODT-644] Protocol tests are extremely buggy and unstable

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.6
• Fix Version/s: 0.8
• Component/s: push pull framework
• Skill Level: Committer (Medium) - This is for regular contributors/committers
• Assignee: Tom Barber
• Reporter: Chris A. Mattmann
• Created: 08/Jul/13 17:25
• Updated: 06/Sep/14 21:22
• Resolved: 05/Sep/14 21:58

Description

The tests in:

• protocol-sftp
• protocol-ftp

Are pretty buggy and unstable. For example, the protocol-ftp starts up a server on port 9000 (the default file manager port – which if you have a file manager running, this will not pass, and it will hang and then I was only able to make it release the port by restarting my computer even though lsof and netstat didn't show anything). As another example, the protocol-sftp plugin starts up an SSH server on the seemingly default port of 12222 (since it's not provided a specific port value – though it seems to also start it up on 22?). These port conflicts would easily be eliminated by Mock objects, and I think they should be since we don't need to be grabbing ports for unit tests.

Issue Links

• incorporates: OODT-660 TestCogJGlobusFtpProtocol fails if another service is using TCP port 9000