You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "boB Gage (JIRA)" <ji...@apache.org> on 2009/10/09 17:30:32 UTC

[jira] Created: (DIRMINA-740) Serial Hardware Flow Control is not working

Serial Hardware Flow Control is not working
-------------------------------------------

                 Key: DIRMINA-740
                 URL: https://issues.apache.org/jira/browse/DIRMINA-740
             Project: MINA
          Issue Type: Bug
    Affects Versions: 2.0.0-M6
         Environment: Very different behaviours seen on Linux and Windows environments.   Issues may be related, or may just both coincidentally happen on hardware flow controlled ports.
            Reporter: boB Gage


Linux machines:

Attempting to connect to a device using hardware flow control (RTS/CTS) fails to accumulate any incoming data regardless of the FlowControl constant sent to the SerialAddress constructor.    

External program (old C++ version of same application) confirms device does respond to requests after port opened as 19200 8E1 with RTS/CTS flow control -- Mina-based Java app fails to get any incoming data at all.  [ This may be because it has not sent the data it thinks it has, as the far end will only respond, not initiate. ]


Windows machines:

Attempting to connect to a port using hardware flow control disables the port for subsequent connections during same execution.    [ IOW, once a port is opened with hardware flow control turned on, no non-flow control protocol is possible on that port. ]     This is especially bad if the hardware-flow-requiring device driver is attempted on a port connected to a device not matching the driver (as the proper driver will not be able to open the port ).


This may or may not be two symptoms of the same root cause.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (DIRMINA-740) Serial Hardware Flow Control is not working

Posted by "boB Gage (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRMINA-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

boB Gage closed DIRMINA-740.
----------------------------


Verified.  Julien's fix has fixed the Linux hardware flow control symptom completely.

THANKS!!

> Serial Hardware Flow Control is not working
> -------------------------------------------
>
>                 Key: DIRMINA-740
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-740
>             Project: MINA
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M6
>         Environment: Very different behaviours seen on Linux and Windows environments.   Issues may be related, or may just both coincidentally happen on hardware flow controlled ports.
>            Reporter: boB Gage
>            Assignee: Julien Vermillard
>
> Linux machines:
> Attempting to connect to a device using hardware flow control (RTS/CTS) fails to accumulate any incoming data regardless of the FlowControl constant sent to the SerialAddress constructor.    
> External program (old C++ version of same application) confirms device does respond to requests after port opened as 19200 8E1 with RTS/CTS flow control -- Mina-based Java app fails to get any incoming data at all.  [ This may be because it has not sent the data it thinks it has, as the far end will only respond, not initiate. ]
> Windows machines:
> Attempting to connect to a port using hardware flow control disables the port for subsequent connections during same execution.    [ IOW, once a port is opened with hardware flow control turned on, no non-flow control protocol is possible on that port. ]     This is especially bad if the hardware-flow-requiring device driver is attempted on a port connected to a device not matching the driver (as the proper driver will not be able to open the port ).
> This may or may not be two symptoms of the same root cause.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (DIRMINA-740) Serial Hardware Flow Control is not working

Posted by "Julien Vermillard (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRMINA-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julien Vermillard resolved DIRMINA-740.
---------------------------------------

    Resolution: Fixed
      Assignee: Julien Vermillard

> Serial Hardware Flow Control is not working
> -------------------------------------------
>
>                 Key: DIRMINA-740
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-740
>             Project: MINA
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M6
>         Environment: Very different behaviours seen on Linux and Windows environments.   Issues may be related, or may just both coincidentally happen on hardware flow controlled ports.
>            Reporter: boB Gage
>            Assignee: Julien Vermillard
>
> Linux machines:
> Attempting to connect to a device using hardware flow control (RTS/CTS) fails to accumulate any incoming data regardless of the FlowControl constant sent to the SerialAddress constructor.    
> External program (old C++ version of same application) confirms device does respond to requests after port opened as 19200 8E1 with RTS/CTS flow control -- Mina-based Java app fails to get any incoming data at all.  [ This may be because it has not sent the data it thinks it has, as the far end will only respond, not initiate. ]
> Windows machines:
> Attempting to connect to a port using hardware flow control disables the port for subsequent connections during same execution.    [ IOW, once a port is opened with hardware flow control turned on, no non-flow control protocol is possible on that port. ]     This is especially bad if the hardware-flow-requiring device driver is attempted on a port connected to a device not matching the driver (as the proper driver will not be able to open the port ).
> This may or may not be two symptoms of the same root cause.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.