qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Preston (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PROTON-811) [PATCH] proton-j: no way to implement idle timeout of a connection
Date Tue, 03 Feb 2015 16:52:34 GMT

     [ https://issues.apache.org/jira/browse/PROTON-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Adrian Preston updated PROTON-811:
    Attachment: 0001-proton-j-updates-for-idle-timeout-mk4.patch

Reworked the patch to fix formatting, remove dependencies on Java 7 features and move the
getters / setters for timeouts into Transport.java.  I also had some success in enabling additional
jython tests - but ran into difficulties with tests.engine.IdleTimeoutTest.testTimeout (which
requires pn_transport_get_frames_input to be implemented) and also proton_tests.engine.ServerTest.testIdleTimeout
and proton_tests.engine.ServerTest.testKeepalive which both need un-implemented frame counting
functions and appear to suffer from some difference between SASL implementations (a bit of
digging suggests that the Python wrappers for the SASL object always set SASL client mode
when run against the Java shims, and this breaks the TestServer - but my lack of Python expertise
stopped me getting any further).

> [PATCH] proton-j: no way to implement idle timeout of a connection
> ------------------------------------------------------------------
>                 Key: PROTON-811
>                 URL: https://issues.apache.org/jira/browse/PROTON-811
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-j
>    Affects Versions: 0.8
>            Reporter: Adrian Preston
>         Attachments: 0001-idle_timeout.patch, 0001-proton-j-updates-for-idle-timeout-mk3.patch,
0001-proton-j-updates-for-idle-timeout-mk4.patch, 0001-proton-j-updates-for-idle-timeout.patch
> Proton-J does not provide access to idle timeout values and there appears to be no way
to send a empty frame (as per section 2.4.5 of the AMQP 1.0 standard)

This message was sent by Atlassian JIRA

View raw message