[jira] [Commented] (PROTON-2141) [cpp] Make unit tests pass on ipv4 machine
[ https://issues.apache.org/jira/browse/PROTON-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16981463#comment-16981463 ] Ali Hadi commented on PROTON-2141: -- [~astitcher] in our host config we have : 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 Both solutions below resolve the problem : - Removing the second line with the ::1 - Replacing "localhost" by "127.0.0.1" in the tests makes them pass. > [cpp] Make unit tests pass on ipv4 machine > -- > > Key: PROTON-2141 > URL: https://issues.apache.org/jira/browse/PROTON-2141 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.29.0 >Reporter: Rabih Mourad >Priority: Major > Attachments: errors.log > > > There are test failure when running unit tests on an ipv4 machine. > So we propose the pull request below. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2141) [cpp] Make unit tests pass on ipv4 machine
[ https://issues.apache.org/jira/browse/PROTON-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980378#comment-16980378 ] Ali Hadi commented on PROTON-2141: -- The two tests that are failing on our CI machine are test_not_reconnecting and test_reconnect. This is our machine config : uname -a : Linux 2.6.32-358.el6.x86_64 #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64 x86_64 x86_64 GNU/Linux ifconfig : eth0 Link encap:Ethernet HWaddr 00:50:56:xx:xx:xx inet addr:10.26.xx.xx Bcast:10.26.xx.255 Mask:255.255.248.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Find attached the log errors. > [cpp] Make unit tests pass on ipv4 machine > -- > > Key: PROTON-2141 > URL: https://issues.apache.org/jira/browse/PROTON-2141 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.29.0 >Reporter: Rabih Mourad >Priority: Major > Attachments: errors.log > > > There are test failure when running unit tests on an ipv4 machine. > So we propose the pull request below. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2141) [cpp] Make unit tests pass on ipv4 machine
[ https://issues.apache.org/jira/browse/PROTON-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ali Hadi updated PROTON-2141: - Attachment: errors.log > [cpp] Make unit tests pass on ipv4 machine > -- > > Key: PROTON-2141 > URL: https://issues.apache.org/jira/browse/PROTON-2141 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.29.0 >Reporter: Rabih Mourad >Priority: Major > Attachments: errors.log > > > There are test failure when running unit tests on an ipv4 machine. > So we propose the pull request below. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2141) [cpp] Make unit tests pass on ipv4 machine
[ https://issues.apache.org/jira/browse/PROTON-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980080#comment-16980080 ] Ali Hadi commented on PROTON-2141: -- [https://github.com/apache/qpid-proton/pull/214] > [cpp] Make unit tests pass on ipv4 machine > -- > > Key: PROTON-2141 > URL: https://issues.apache.org/jira/browse/PROTON-2141 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.29.0 >Reporter: Rabih Mourad >Priority: Major > > There are test failure when running unit tests on an ipv4 machine. > So we propose this attached fix. > A pull request will be added too. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1294) Handling TTL in Dispatch Router
Ali Hadi created DISPATCH-1294: -- Summary: Handling TTL in Dispatch Router Key: DISPATCH-1294 URL: https://issues.apache.org/jira/browse/DISPATCH-1294 Project: Qpid Dispatch Issue Type: New Feature Reporter: Ali Hadi See [http://mail-archives.apache.org/mod_mbox/qpid-users/201903.mbox/browser]. The usage of TTL in a cluster including a Dispatch Router with autolinks is not currently possible since the dispatch is prefetching messages from the broker. The aim of this feature is to handle a TTL logic on the dispatch router side. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1862) Idle timeout not working on Linux
[ https://issues.apache.org/jira/browse/PROTON-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16629993#comment-16629993 ] Ali Hadi commented on PROTON-1862: -- I tested it on proton 0.25.0 and it's not working. > Idle timeout not working on Linux > - > > Key: PROTON-1862 > URL: https://issues.apache.org/jira/browse/PROTON-1862 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.22.0 >Reporter: Jeremy >Priority: Critical > Labels: reproducer > Attachments: proton_1862_tests.txt, test_case.cpp > > > We faced an issue with the idle timeout on linux. On windows, it seems to > work. > In our proton feature test suite, we test the idle timeout feature by doing a > sleep in the method on_session_open. > This should trigger a connection timeout. It works on windows, and it used to > work with proton v0.16.0 on windows and linux. > Removing the sleep from the on_session_open and putting it in > on_connection_open, yields the same result. > See attached file to reproduce. > Machines: > * Windows machine > ** OS: Windows 7 > ** Compiler: MSVC 2013 Version 12 Update 5 > * Linux machine > ** OS: Red Hat Enterprise Linux Server release 6.4 (Santiago) > ** Compiler: g++491 (GCC) 4.9.2 20150212 (Red Hat 4.9.2-6) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (PROTON-1862) Idle timeout not working on Linux
[ https://issues.apache.org/jira/browse/PROTON-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627391#comment-16627391 ] Ali Hadi edited comment on PROTON-1862 at 9/26/18 8:51 AM: --- Hello, We analysed this issue and we noticed that in the on_connection_open or on_session_open of the receiver, the connection with the server is not yet established and this is why the idle-timeout does not expire. Moving the sleep in the on_message causes the idle time-out to always expires. Therefore the problem is that the proton container on Linux is calling on_connection_open before the remote peer opened the connection, unlike stated in the documentation in messaging_handler.hpp. I will test it on the latest proton version. We must think of changing the issue title. Regards, Ali was (Author: alihadi): Hello, We analysed this issue and the behavior of the test is normal. In fact, in the on_connection_open or on_session_open of the receiver, the connection with the server is not yet established and this is why the idle-timeout does not expire. Moving the sleep in the on_message causes the idle time-out to always expires. That being said, the difference in behavior of windows is still an issue that needs to addressed. Regards, Ali > Idle timeout not working on Linux > - > > Key: PROTON-1862 > URL: https://issues.apache.org/jira/browse/PROTON-1862 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.22.0 >Reporter: Jeremy >Priority: Critical > Labels: reproducer > Attachments: proton_1862_tests.txt, test_case.cpp > > > We faced an issue with the idle timeout on linux. On windows, it seems to > work. > In our proton feature test suite, we test the idle timeout feature by doing a > sleep in the method on_session_open. > This should trigger a connection timeout. It works on windows, and it used to > work with proton v0.16.0 on windows and linux. > Removing the sleep from the on_session_open and putting it in > on_connection_open, yields the same result. > See attached file to reproduce. > Machines: > * Windows machine > ** OS: Windows 7 > ** Compiler: MSVC 2013 Version 12 Update 5 > * Linux machine > ** OS: Red Hat Enterprise Linux Server release 6.4 (Santiago) > ** Compiler: g++491 (GCC) 4.9.2 20150212 (Red Hat 4.9.2-6) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1862) Idle timeout not working on Linux
[ https://issues.apache.org/jira/browse/PROTON-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627391#comment-16627391 ] Ali Hadi commented on PROTON-1862: -- Hello, We analysed this issue and the behavior of the test is normal. In fact, in the on_connection_open or on_session_open of the receiver, the connection with the server is not yet established and this is why the idle-timeout does not expire. Moving the sleep in the on_message causes the idle time-out to always expires. That being said, the difference in behavior of windows is still an issue that needs to addressed. Regards, Ali > Idle timeout not working on Linux > - > > Key: PROTON-1862 > URL: https://issues.apache.org/jira/browse/PROTON-1862 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.22.0 >Reporter: Jeremy >Priority: Critical > Labels: reproducer > Attachments: proton_1862_tests.txt, test_case.cpp > > > We faced an issue with the idle timeout on linux. On windows, it seems to > work. > In our proton feature test suite, we test the idle timeout feature by doing a > sleep in the method on_session_open. > This should trigger a connection timeout. It works on windows, and it used to > work with proton v0.16.0 on windows and linux. > Removing the sleep from the on_session_open and putting it in > on_connection_open, yields the same result. > See attached file to reproduce. > Machines: > * Windows machine > ** OS: Windows 7 > ** Compiler: MSVC 2013 Version 12 Update 5 > * Linux machine > ** OS: Red Hat Enterprise Linux Server release 6.4 (Santiago) > ** Compiler: g++491 (GCC) 4.9.2 20150212 (Red Hat 4.9.2-6) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7885) [Java Broker] Support Java 9
[ https://issues.apache.org/jira/browse/QPID-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16613383#comment-16613383 ] Ali Hadi commented on QPID-7885: Hello, Since Java 9 JaxB APIs are no longer contained on the default classpath. In the Qpid BrokerJ code, one of JaxB's classes ( javax.xml.bind.DatatypeConverter ) is used multiple times. Is it possible to explicitly add the jaxb-api as a maven dependency in order to use the BrokerJ on newer java versions? > [Java Broker] Support Java 9 > > > Key: QPID-7885 > URL: https://issues.apache.org/jira/browse/QPID-7885 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Lorenz Quack >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > With the Java 9 on the horizon it is time to get Qpid's Java components ready. > * make sure component compile with JDK9 > * make sure components run with JRE9 > * take advantage of the new Java Module System -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
