[jira] [Resolved] (QPID-8442) [JMS AMQP 0-x] Release version 6.4.0 of Qpid JMS client for AMQP 0-x
[ https://issues.apache.org/jira/browse/QPID-8442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8442. -- Resolution: Fixed > [JMS AMQP 0-x] Release version 6.4.0 of Qpid JMS client for AMQP 0-x > > > Key: QPID-8442 > URL: https://issues.apache.org/jira/browse/QPID-8442 > Project: Qpid > Issue Type: Task > Components: JMS AMQP 0-x >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-client-0-x-6.4.0 > > > Release Qpid JMS AMQP 0-x client following instructions > [here|https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+JMS+AMQP+0-x] -- 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-2237) [python] Non-string message property keys not handled correctly
[ https://issues.apache.org/jira/browse/PROTON-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126098#comment-17126098 ] ASF subversion and git services commented on PROTON-2237: - Commit 65869963ea8b35927e6a0890052c08ca587da022 in qpid-proton's branch refs/heads/python-check-property-keys from Kim van der Riet [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=6586996 ] PROTON-2237: Alternative approach which converts all child classes of string/unicode to the base class, including proton symbol and char types. > [python] Non-string message property keys not handled correctly > --- > > Key: PROTON-2237 > URL: https://issues.apache.org/jira/browse/PROTON-2237 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Reporter: Kim van der Riet >Priority: Major > > The AMQP 1.0 spec allows only string keys for message properties. > Proton's Python binding has a method (_message.py:91 _check_property_keys()) > for checking message property keys, but it does not handle all cases > correctly: > # Proton types Symbol and Char are derived from string, and are allowed in > the test. This results in an illegal encoding. > # Because in Python 2, many coders carelessly use string literals without > the required u'' prefix (and thus results in a bytes type), bytes types are > converted to unicode string types. However, the encode() function is being > used, which simply returns a binary type in Python 2 and raises an error in > Python 3. This should probably be the decode() method, which returns a string > and works for both Python 2 and 3. -- 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-2239) epoll proactor race condition on connection teardown with heartbeats
[ https://issues.apache.org/jira/browse/PROTON-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125982#comment-17125982 ] Clifford Jansen commented on PROTON-2239: - The memory corruption angle tended to muddy the waters and obscure the cause of the crash. Eventually some core dumps identified timers as being in the mix. On a hunch, the following reproducer was attempted and provided identical stack traces. Even knowing what to look for, it is necessary to tune the timing of the peer's close operation to maximize the opportunity for expose the bug. > epoll proactor race condition on connection teardown with heartbeats > > > Key: PROTON-2239 > URL: https://issues.apache.org/jira/browse/PROTON-2239 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.28.0 >Reporter: Clifford Jansen >Assignee: Clifford Jansen >Priority: Major > Attachments: xxx.c > > > If a connection with heartbeats is closed at about the same time to when its > idle timeout timer fires, it is possible to have two threads believing they > are the last activity on the connection. Both threads proceed to free the > same resources leading to memory corruption and various crashes. > The existing code has guards for this exact situation, but there is an > Achilles heel somewhere. -- 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-2239) epoll proactor race condition on connection teardown with heartbeats
[ https://issues.apache.org/jira/browse/PROTON-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clifford Jansen updated PROTON-2239: Attachment: xxx.c > epoll proactor race condition on connection teardown with heartbeats > > > Key: PROTON-2239 > URL: https://issues.apache.org/jira/browse/PROTON-2239 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.28.0 >Reporter: Clifford Jansen >Assignee: Clifford Jansen >Priority: Major > Attachments: xxx.c > > > If a connection with heartbeats is closed at about the same time to when its > idle timeout timer fires, it is possible to have two threads believing they > are the last activity on the connection. Both threads proceed to free the > same resources leading to memory corruption and various crashes. > The existing code has guards for this exact situation, but there is an > Achilles heel somewhere. -- 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] (PROTON-2239) epoll proactor race condition on connection teardown with heartbeats
Clifford Jansen created PROTON-2239: --- Summary: epoll proactor race condition on connection teardown with heartbeats Key: PROTON-2239 URL: https://issues.apache.org/jira/browse/PROTON-2239 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: proton-c-0.28.0 Reporter: Clifford Jansen Assignee: Clifford Jansen Attachments: xxx.c If a connection with heartbeats is closed at about the same time to when its idle timeout timer fires, it is possible to have two threads believing they are the last activity on the connection. Both threads proceed to free the same resources leading to memory corruption and various crashes. The existing code has guards for this exact situation, but there is an Achilles heel somewhere. -- 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] (DISPATCH-1683) test_06_dynamic_reply_to_DC in system_tests_distribution is failing
[
https://issues.apache.org/jira/browse/DISPATCH-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125917#comment-17125917
]
ASF subversion and git services commented on DISPATCH-1683:
---
Commit b0ba0ae05e5fdef0ca1cdc95865afc8dfd3d5565 in qpid-dispatch's branch
refs/heads/master from Ganesh Murthy
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=b0ba0ae ]
DISPATCH-1683 - Used the correct sender to send messages. Also waited till
address propagated across routers. This closes #754
> test_06_dynamic_reply_to_DC in system_tests_distribution is failing
> ---
>
> Key: DISPATCH-1683
> URL: https://issues.apache.org/jira/browse/DISPATCH-1683
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Priority: Major
>
> {noformat}
> 36: ==
> 36: FAIL: test_06_dynamic_reply_to_DC
> (system_tests_distribution.DistributionTests)
> 36: --
> 36: Traceback (most recent call last):
> 36: File "/foo/qpid-dispatch/tests/system_test.py", line 820, in wrap
> 36: return f(*args, **kwargs)
> 36: File "/foo/qpid-dispatch/tests/system_tests_distribution.py", line 564,
> in test_06_dynamic_reply_to_DC
> 36: self.assertEqual ( None, test.error )
> 36: AssertionError: None != u'Timeout Expired: n_sent=0 received_by_server=0
> received_by_client=0'
> 36:
> 36: --
> 36: Ran 25 tests in 92.816s
> 36:
> 36: FAILED (failures=1, skipped=7)
> 36/67 Test #36: system_tests_distribution .***Failed
> 93.00 sec {noformat}
--
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] (DISPATCH-1683) test_06_dynamic_reply_to_DC in system_tests_distribution is failing
[
https://issues.apache.org/jira/browse/DISPATCH-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125918#comment-17125918
]
ASF GitHub Bot commented on DISPATCH-1683:
--
asfgit closed pull request #754:
URL: https://github.com/apache/qpid-dispatch/pull/754
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> test_06_dynamic_reply_to_DC in system_tests_distribution is failing
> ---
>
> Key: DISPATCH-1683
> URL: https://issues.apache.org/jira/browse/DISPATCH-1683
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Priority: Major
>
> {noformat}
> 36: ==
> 36: FAIL: test_06_dynamic_reply_to_DC
> (system_tests_distribution.DistributionTests)
> 36: --
> 36: Traceback (most recent call last):
> 36: File "/foo/qpid-dispatch/tests/system_test.py", line 820, in wrap
> 36: return f(*args, **kwargs)
> 36: File "/foo/qpid-dispatch/tests/system_tests_distribution.py", line 564,
> in test_06_dynamic_reply_to_DC
> 36: self.assertEqual ( None, test.error )
> 36: AssertionError: None != u'Timeout Expired: n_sent=0 received_by_server=0
> received_by_client=0'
> 36:
> 36: --
> 36: Ran 25 tests in 92.816s
> 36:
> 36: FAILED (failures=1, skipped=7)
> 36/67 Test #36: system_tests_distribution .***Failed
> 93.00 sec {noformat}
--
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
[GitHub] [qpid-dispatch] asfgit closed pull request #754: DISPATCH-1683 - Used the correct sender to send messages. Also waited…
asfgit closed pull request #754: URL: https://github.com/apache/qpid-dispatch/pull/754 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-1683) test_06_dynamic_reply_to_DC in system_tests_distribution is failing
[
https://issues.apache.org/jira/browse/DISPATCH-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-1683:
---
Assignee: Ganesh Murthy
> test_06_dynamic_reply_to_DC in system_tests_distribution is failing
> ---
>
> Key: DISPATCH-1683
> URL: https://issues.apache.org/jira/browse/DISPATCH-1683
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> 36: ==
> 36: FAIL: test_06_dynamic_reply_to_DC
> (system_tests_distribution.DistributionTests)
> 36: --
> 36: Traceback (most recent call last):
> 36: File "/foo/qpid-dispatch/tests/system_test.py", line 820, in wrap
> 36: return f(*args, **kwargs)
> 36: File "/foo/qpid-dispatch/tests/system_tests_distribution.py", line 564,
> in test_06_dynamic_reply_to_DC
> 36: self.assertEqual ( None, test.error )
> 36: AssertionError: None != u'Timeout Expired: n_sent=0 received_by_server=0
> received_by_client=0'
> 36:
> 36: --
> 36: Ran 25 tests in 92.816s
> 36:
> 36: FAILED (failures=1, skipped=7)
> 36/67 Test #36: system_tests_distribution .***Failed
> 93.00 sec {noformat}
--
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] [Resolved] (DISPATCH-1683) test_06_dynamic_reply_to_DC in system_tests_distribution is failing
[
https://issues.apache.org/jira/browse/DISPATCH-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1683.
-
Fix Version/s: 1.13.0
Resolution: Fixed
> test_06_dynamic_reply_to_DC in system_tests_distribution is failing
> ---
>
> Key: DISPATCH-1683
> URL: https://issues.apache.org/jira/browse/DISPATCH-1683
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> 36: ==
> 36: FAIL: test_06_dynamic_reply_to_DC
> (system_tests_distribution.DistributionTests)
> 36: --
> 36: Traceback (most recent call last):
> 36: File "/foo/qpid-dispatch/tests/system_test.py", line 820, in wrap
> 36: return f(*args, **kwargs)
> 36: File "/foo/qpid-dispatch/tests/system_tests_distribution.py", line 564,
> in test_06_dynamic_reply_to_DC
> 36: self.assertEqual ( None, test.error )
> 36: AssertionError: None != u'Timeout Expired: n_sent=0 received_by_server=0
> received_by_client=0'
> 36:
> 36: --
> 36: Ran 25 tests in 92.816s
> 36:
> 36: FAILED (failures=1, skipped=7)
> 36/67 Test #36: system_tests_distribution .***Failed
> 93.00 sec {noformat}
--
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
[ANNOUNCE] Apache Qpid Proton-J 0.33.5 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Proton-J 0.33.5. Apache Qpid Proton-J is a messaging library for the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org). It can be used in a wide range of messaging applications including brokers, clients, routers, bridges, proxies, and more. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-proton-j-0.33.5/release-notes.html Thanks to all involved, Robbie - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2238) qpid-proton doesn't build with OpenSSL 3.0.0
[
https://issues.apache.org/jira/browse/PROTON-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125619#comment-17125619
]
Vitezslav Cizek commented on PROTON-2238:
-
The deprecation of SSL_CTX_load_verify_locations has been recently reverted in
[https://github.com/openssl/openssl/commit/c7f837cfcc5b2e5cd8eeeff82e0245323f206d02.]
So the changes in pull request #257 are no longer necessary for now, but might
be useful in the future though.
> qpid-proton doesn't build with OpenSSL 3.0.0
>
>
> Key: PROTON-2238
> URL: https://issues.apache.org/jira/browse/PROTON-2238
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.31.0
>Reporter: Vitezslav Cizek
>Priority: Minor
>
> OpenSSL 3.0.0 deprecates {{}}{{SSL_CTX_load_verify_locations.}}
> As -Werror is turned on by default, the warning causes a build failure:
> qpid-proton-0.31.0/c/src/ssl/openssl.c:722:3: error:
> 'SSL_CTX_load_verify_locations' is deprecated
> [-Werror=deprecated-declarations]
> 722 | if (SSL_CTX_load_verify_locations( domain->ctx, file, dir ) != 1) {
--
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
