[DIRMINA-720] Hardware Flow Control Disables Serial Port on Windows Platform

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-M4, 2.0.0-M5, 2.0.0-M6, 2.0.0-RC1
• Fix Version/s: 2.0.0
• Component/s: Transport
• Environment: Windows, serial connections only; Specifically does NOT happen on Linux systems (others untested)
• Assignee: Julien Vermillard
• Reporter: boB Gage
• Created: 18/Jun/09 13:56
• Updated: 27/Feb/10 12:40
• Resolved: 12/Jan/10 17:53

Description

Attempting protocol discovery on single port – Most protocols use no flow control, one using RTS/CTS. Each protocol attempts connection, fails (because far end device turned off), then tries next protocol.

Test involves letting discovery fail through multiple cycles (ie test all available protocols) then eventually turn on device and see it get discovered when it's protocol cycles back around.

HOWEVER... test failed before first cycle completed, because first protocol using CTS/RTS flow control (via FlowControl.RTSCTS_OUT parameter to SerialAddress constructor) is the last one to successfully open the serial port.

While the protocol with RTS/CTS works (in that it properly fails), the next, and all following, protocols fail immediately as the port throws a PortInUseException on open attempt.

Changing FlowControl.RTSCTS_OUT to FlowControl.NONE makes this test run fine. It also, however, breaks that particular protocol because the far end device expects flow control that it does not see.