[ https://issues.apache.org/jira/browse/PROTON-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614454#comment-14614454 ]
ASF subversion and git services commented on PROTON-881: -------------------------------------------------------- Commit e2d23691541b09f4efc59a32705a5306b179a0b0 in qpid-proton's branch refs/heads/master from [~prestona] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=e2d2369 ] PROTON-881: Make connect a non-blocking operation Previously connecting was a blocking operation which meant that if the server being connected to took a long time to accept the connection this blocked all other work in an instance of the Reactor. This commit makes connect a non-blocking operation, allowing the reactor to continue processing other work while the connection is established (or not). Unfortunately, I've not found a satisfactory way to test this behavior in the test suite - because Java never blocks during connect if it is using the loopback adapter. Instead, to test the non-blocking connect code path, I had to configure firewall rules to drop all packets sent to a particular port. > Proton-j reactor implementation > ------------------------------- > > Key: PROTON-881 > URL: https://issues.apache.org/jira/browse/PROTON-881 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j > Affects Versions: 0.9 > Reporter: Adrian Preston > Priority: Minor > > To keep the proton-j codebase consistent with proton-c - there should be a > native Java port of the reactor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)