[jira] [Assigned] (PROTON-2026) reconnect is broken
[ https://issues.apache.org/jira/browse/PROTON-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-2026: --- Assignee: Andrew Stitcher > reconnect is broken > --- > > Key: PROTON-2026 > URL: https://issues.apache.org/jira/browse/PROTON-2026 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.28.0 >Reporter: Gordon Sim >Assignee: Andrew Stitcher >Priority: Blocker > Fix For: proton-c-0.28.0 > > > E.g. try running simple_recv.py against a server that is not there. Up to > 0.27.0 it would keep trying, on master now it exists with a socket error. > Also, likely related, up to 0.27.0 you would always get an > on_transport_closed in this case, but on master you no longer do. -- 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] [Resolved] (PROTON-2028) [c++] Json config connect test gets port too early
[ https://issues.apache.org/jira/browse/PROTON-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2028. - Resolution: Fixed Fix Version/s: proton-c-0.28.0 > [c++] Json config connect test gets port too early > -- > > Key: PROTON-2028 > URL: https://issues.apache.org/jira/browse/PROTON-2028 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Reporter: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.28.0 > > > Instead of waiting for the bind to finish it tries to get the port > immediately. This works using the epoll/iocp proactors, but not the libuv > proactor. -- 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-2028) [c++] Json config connect test gets port too early
[ https://issues.apache.org/jira/browse/PROTON-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811280#comment-16811280 ] ASF subversion and git services commented on PROTON-2028: - Commit e56b27819b57ec30f4f065bc5cf05d7025ed9bb2 in qpid-proton's branch refs/heads/master from Andrew Stitcher [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=e56b278 ] PROTON-2028: [C++] Fix Json config connect test to correctly get connection port > [c++] Json config connect test gets port too early > -- > > Key: PROTON-2028 > URL: https://issues.apache.org/jira/browse/PROTON-2028 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Reporter: Andrew Stitcher >Priority: Major > > Instead of waiting for the bind to finish it tries to get the port > immediately. This works using the epoll/iocp proactors, but not the libuv > proactor. -- 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] [Created] (PROTON-2028) [c++] Json config connect test gets port too early
Andrew Stitcher created PROTON-2028: --- Summary: [c++] Json config connect test gets port too early Key: PROTON-2028 URL: https://issues.apache.org/jira/browse/PROTON-2028 Project: Qpid Proton Issue Type: Bug Components: cpp-binding Reporter: Andrew Stitcher Instead of waiting for the bind to finish it tries to get the port immediately. This works using the epoll/iocp proactors, but not the libuv proactor. -- 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] [Resolved] (PROTON-2025) Azure Pipeline build definition
[ https://issues.apache.org/jira/browse/PROTON-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2025. - Resolution: Fixed Fix Version/s: proton-c-0.28.0 > Azure Pipeline build definition > --- > > Key: PROTON-2025 > URL: https://issues.apache.org/jira/browse/PROTON-2025 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Reporter: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.28.0 > > > To get the widest possible exposure the wider the range of supported CIs the > better. -- 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] (DISPATCH-1313) Allow configuration of optional policy-vhost in listeners so different listeners can enforce different policies
[ https://issues.apache.org/jira/browse/DISPATCH-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811264#comment-16811264 ] ASF GitHub Bot commented on DISPATCH-1313: -- codecov-io commented on issue #482: DISPATCH-1313 - Added policyVhost attribute to the listener entity. … URL: https://github.com/apache/qpid-dispatch/pull/482#issuecomment-480424695 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=h1) Report > Merging [#482](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=desc) into [master](https://codecov.io/gh/apache/qpid-dispatch/commit/f574201c65b06697720a5dcd35085fae0638ae28?src=pr&el=desc) will **increase** coverage by `0.02%`. > The diff coverage is `100%`. [](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=tree) ```diff @@Coverage Diff @@ ## master #482 +/- ## == + Coverage86.9% 86.93% +0.02% == Files 85 85 Lines 1922019223 +3 == + Hits1670316711 +8 + Misses 2517 2512 -5 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=tree) | Coverage Δ | | |---|---|---| | [src/policy.c](https://codecov.io/gh/apache/qpid-dispatch/pull/482/diff?src=pr&el=tree#diff-c3JjL3BvbGljeS5j) | `86% <100%> (+0.06%)` | :arrow_up: | | [src/connection\_manager.c](https://codecov.io/gh/apache/qpid-dispatch/pull/482/diff?src=pr&el=tree#diff-c3JjL2Nvbm5lY3Rpb25fbWFuYWdlci5j) | `89.54% <100%> (+0.02%)` | :arrow_up: | | [src/parse.c](https://codecov.io/gh/apache/qpid-dispatch/pull/482/diff?src=pr&el=tree#diff-c3JjL3BhcnNlLmM=) | `88.13% <0%> (-0.03%)` | :arrow_down: | | [src/router\_core/router\_core.c](https://codecov.io/gh/apache/qpid-dispatch/pull/482/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL3JvdXRlcl9jb3JlLmM=) | `87.09% <0%> (+0.21%)` | :arrow_up: | | [src/remote\_sasl.c](https://codecov.io/gh/apache/qpid-dispatch/pull/482/diff?src=pr&el=tree#diff-c3JjL3JlbW90ZV9zYXNsLmM=) | `83.88% <0%> (+1.11%)` | :arrow_up: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=footer). Last update [f574201...c764bdb](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). 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 > Allow configuration of optional policy-vhost in listeners so different > listeners can enforce different policies > --- > > Key: DISPATCH-1313 > URL: https://issues.apache.org/jira/browse/DISPATCH-1313 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Container >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > > Add an attribute to the listener configuration for policyVhost. This > optional attribute, if supplied indicates the vhost to be used in looking up > access policy for connections arriving through the connector. > PolicyVhost is used only for policy lookup. It does not affect the behavior > of multi-tenancy. > -- 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
[GitHub] [qpid-dispatch] codecov-io commented on issue #482: DISPATCH-1313 - Added policyVhost attribute to the listener entity. …
codecov-io commented on issue #482: DISPATCH-1313 - Added policyVhost attribute to the listener entity. … URL: https://github.com/apache/qpid-dispatch/pull/482#issuecomment-480424695 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=h1) Report > Merging [#482](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=desc) into [master](https://codecov.io/gh/apache/qpid-dispatch/commit/f574201c65b06697720a5dcd35085fae0638ae28?src=pr&el=desc) will **increase** coverage by `0.02%`. > The diff coverage is `100%`. [](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=tree) ```diff @@Coverage Diff @@ ## master #482 +/- ## == + Coverage86.9% 86.93% +0.02% == Files 85 85 Lines 1922019223 +3 == + Hits1670316711 +8 + Misses 2517 2512 -5 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=tree) | Coverage Δ | | |---|---|---| | [src/policy.c](https://codecov.io/gh/apache/qpid-dispatch/pull/482/diff?src=pr&el=tree#diff-c3JjL3BvbGljeS5j) | `86% <100%> (+0.06%)` | :arrow_up: | | [src/connection\_manager.c](https://codecov.io/gh/apache/qpid-dispatch/pull/482/diff?src=pr&el=tree#diff-c3JjL2Nvbm5lY3Rpb25fbWFuYWdlci5j) | `89.54% <100%> (+0.02%)` | :arrow_up: | | [src/parse.c](https://codecov.io/gh/apache/qpid-dispatch/pull/482/diff?src=pr&el=tree#diff-c3JjL3BhcnNlLmM=) | `88.13% <0%> (-0.03%)` | :arrow_down: | | [src/router\_core/router\_core.c](https://codecov.io/gh/apache/qpid-dispatch/pull/482/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL3JvdXRlcl9jb3JlLmM=) | `87.09% <0%> (+0.21%)` | :arrow_up: | | [src/remote\_sasl.c](https://codecov.io/gh/apache/qpid-dispatch/pull/482/diff?src=pr&el=tree#diff-c3JjL3JlbW90ZV9zYXNsLmM=) | `83.88% <0%> (+1.11%)` | :arrow_up: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=footer). Last update [f574201...c764bdb](https://codecov.io/gh/apache/qpid-dispatch/pull/482?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). 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 With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8294) [Broker-J][Oracle Message Store] Batch delete fails for more than 1000 messages
[ https://issues.apache.org/jira/browse/QPID-8294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811255#comment-16811255 ] ASF GitHub Bot commented on QPID-8294: -- overmeulen commented on pull request #23: QPID-8294: [Broker-J][Oracle Message Store] Batch delete fails for more than 1000 messages URL: https://github.com/apache/qpid-broker-j/pull/23#discussion_r272744201 ## File path: broker-plugins/jdbc-store/src/main/java/org/apache/qpid/server/store/jdbc/AbstractJDBCMessageStore.java ## @@ -82,6 +82,8 @@ private static final String XID_TABLE_NAME_SUFFIX = "QPID_XIDS"; private static final String XID_ACTIONS_TABLE_NAME_SUFFIX = "QPID_XID_ACTIONS"; +private static final int MAX_DELETE_BATCH_SIZE = 1000; Review comment: Good idea. But to be consistent with the other system variables I propose "qpid.jdbcstore.inClauseMaxSize". I'm also changing the name to inClauseMaxSize because actually it's not really a batch here and it's not specific to the delete operation. WDYT? 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 > [Broker-J][Oracle Message Store] Batch delete fails for more than 1000 > messages > --- > > Key: QPID-8294 > URL: https://issues.apache.org/jira/browse/QPID-8294 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Olivier VERMEULEN >Priority: Critical > > When under high load, the Broker-J can end up having to delete more than 1000 > messages in a single batch. But some databases (and Oracle in particular) put > a limit to the number of elements you can have in the IN clause. So we end up > with the following exception: ORA-01795: maximum number of expressions in a > list is 1000 -- 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
[GitHub] [qpid-broker-j] overmeulen commented on a change in pull request #23: QPID-8294: [Broker-J][Oracle Message Store] Batch delete fails for more than 1000 messages
overmeulen commented on a change in pull request #23: QPID-8294: [Broker-J][Oracle Message Store] Batch delete fails for more than 1000 messages URL: https://github.com/apache/qpid-broker-j/pull/23#discussion_r272744201 ## File path: broker-plugins/jdbc-store/src/main/java/org/apache/qpid/server/store/jdbc/AbstractJDBCMessageStore.java ## @@ -82,6 +82,8 @@ private static final String XID_TABLE_NAME_SUFFIX = "QPID_XIDS"; private static final String XID_ACTIONS_TABLE_NAME_SUFFIX = "QPID_XID_ACTIONS"; +private static final int MAX_DELETE_BATCH_SIZE = 1000; Review comment: Good idea. But to be consistent with the other system variables I propose "qpid.jdbcstore.inClauseMaxSize". I'm also changing the name to inClauseMaxSize because actually it's not really a batch here and it's not specific to the delete operation. WDYT? 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 With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1313) Allow configuration of optional policy-vhost in listeners so different listeners can enforce different policies
[ https://issues.apache.org/jira/browse/DISPATCH-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811246#comment-16811246 ] ASF GitHub Bot commented on DISPATCH-1313: -- ted-ross commented on pull request #482: DISPATCH-1313 - Added policyVhost attribute to the listener entity. … URL: https://github.com/apache/qpid-dispatch/pull/482 …This optional field, if supplied, provides the vhost name to be used for policy lookup on connections arriving through the listener. It allows multiple listeners to use different policy settings. 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 > Allow configuration of optional policy-vhost in listeners so different > listeners can enforce different policies > --- > > Key: DISPATCH-1313 > URL: https://issues.apache.org/jira/browse/DISPATCH-1313 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Container >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > > Add an attribute to the listener configuration for policyVhost. This > optional attribute, if supplied indicates the vhost to be used in looking up > access policy for connections arriving through the connector. > PolicyVhost is used only for policy lookup. It does not affect the behavior > of multi-tenancy. > -- 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
[GitHub] [qpid-dispatch] ted-ross opened a new pull request #482: DISPATCH-1313 - Added policyVhost attribute to the listener entity. …
ted-ross opened a new pull request #482: DISPATCH-1313 - Added policyVhost attribute to the listener entity. … URL: https://github.com/apache/qpid-dispatch/pull/482 …This optional field, if supplied, provides the vhost name to be used for policy lookup on connections arriving through the listener. It allows multiple listeners to use different policy settings. 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 With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1313) Allow configuration of optional policy-vhost in listeners so different listeners can enforce different policies
[ https://issues.apache.org/jira/browse/DISPATCH-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-1313: --- Summary: Allow configuration of optional policy-vhost in listeners so different listeners can enforce different policies (was: Allow configuration of optional policy-vhost in listeners to different listeners can enforce different policies) > Allow configuration of optional policy-vhost in listeners so different > listeners can enforce different policies > --- > > Key: DISPATCH-1313 > URL: https://issues.apache.org/jira/browse/DISPATCH-1313 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Container >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > > Add an attribute to the listener configuration for policyVhost. This > optional attribute, if supplied indicates the vhost to be used in looking up > access policy for connections arriving through the connector. > PolicyVhost is used only for policy lookup. It does not affect the behavior > of multi-tenancy. > -- 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] [Created] (DISPATCH-1313) Allow configuration of optional policy-vhost in listeners to different listeners can enforce different policies
Ted Ross created DISPATCH-1313: -- Summary: Allow configuration of optional policy-vhost in listeners to different listeners can enforce different policies Key: DISPATCH-1313 URL: https://issues.apache.org/jira/browse/DISPATCH-1313 Project: Qpid Dispatch Issue Type: New Feature Components: Container Reporter: Ted Ross Assignee: Ted Ross Add an attribute to the listener configuration for policyVhost. This optional attribute, if supplied indicates the vhost to be used in looking up access policy for connections arriving through the connector. PolicyVhost is used only for policy lookup. It does not affect the behavior of multi-tenancy. -- 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
[ANNOUNCE] Apache Qpid Broker-J 7.1.2 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Broker-J 7.1.2. This is the latest release of pure java implementation of messaging broker supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org) and legacy AMQP protocols 0-10, 0-91, 0-9 and 0-8. Please visit Qpid project site for more details: http://qpid.apache.org/components/broker-j/index.html The release is available now from our website: http://qpid.apache.org/download.html Release notes can be found at: http://qpid.apache.org/releases/qpid-broker-j-7.1.2/release-notes.html Thanks to all involved, Alex - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8290) [Broker-J] Release Qpid Broker-J version 7.1.2
[ https://issues.apache.org/jira/browse/QPID-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8290. -- Resolution: Fixed > [Broker-J] Release Qpid Broker-J version 7.1.2 > -- > > Key: QPID-8290 > URL: https://issues.apache.org/jira/browse/QPID-8290 > Project: Qpid > Issue Type: Task > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.2 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.2 > > > Release Qpid Broker-J version 7.1.2 following instructions at > [https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Broker-J] -- 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] [Resolved] (QPID-8281) [Broker-J] Regenerate test keystores and trustores containing RSA 1024bit keys
[
https://issues.apache.org/jira/browse/QPID-8281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy resolved QPID-8281.
--
Resolution: Fixed
> [Broker-J] Regenerate test keystores and trustores containing RSA 1024bit keys
> --
>
> Key: QPID-8281
> URL: https://issues.apache.org/jira/browse/QPID-8281
> Project: Qpid
> Issue Type: Test
> Components: Java Tests
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.2,
> qpid-java-broker-7.0.8
>
>
> Unit and integration tests operating with pre-generated test key-stores are
> failing with newer JDKs like openjdk-1.8.0.201.b09-2 due to deprecation of
> RSA 1024bit keys:
> {noformat}
> Caused by: java.security.cert.CertPathValidatorException: Algorithm
> constraints check failed on keysize limits. RSA 1024bit key used with
> certificate: CN=MyRootCA, O=ACME, ST=Ontario, C=CA. Usage was tls server
> at
> sun.security.util.DisabledAlgorithmConstraints$KeySizeConstraint.permits(DisabledAlgorithmConstraints.java:817)
> at
> sun.security.util.DisabledAlgorithmConstraints$Constraints.permits(DisabledAlgorithmConstraints.java:419)
> at
> sun.security.util.DisabledAlgorithmConstraints.permits(DisabledAlgorithmConstraints.java:167)
> at
> sun.security.provider.certpath.AlgorithmChecker.check(AlgorithmChecker.java:332)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkAlgorithmConstraints(SSLContextImpl.java:1222)
> {noformat}
> Test kestores and key materials based on RSA 1024bit keys need to be
> re-created with stronger RSA keys
--
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] [Updated] (QPID-8290) [Broker-J] Release Qpid Broker-J version 7.1.2
[ https://issues.apache.org/jira/browse/QPID-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8290: - Status: Reviewable (was: In Progress) > [Broker-J] Release Qpid Broker-J version 7.1.2 > -- > > Key: QPID-8290 > URL: https://issues.apache.org/jira/browse/QPID-8290 > Project: Qpid > Issue Type: Task > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.2 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.2 > > > Release Qpid Broker-J version 7.1.2 following instructions at > [https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Broker-J] -- 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] [Resolved] (QPID-8286) [Broker-J] Add operation into priority queue to change message priority
[ https://issues.apache.org/jira/browse/QPID-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8286. -- Resolution: Fixed > [Broker-J] Add operation into priority queue to change message priority > --- > > Key: QPID-8286 > URL: https://issues.apache.org/jira/browse/QPID-8286 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.2 > > > The functionality to change message priority is required for some use case > scenarios involving priority queues. At the moment, in order to change the > priority, the messages need to be consumed (for example, using selector > 'JMSMessageID=ID:XYZ') and re-published with a different priority. I > management operation can be introduced on the priority queue which can simply > dequeue the message and re-enqueue it with a provided priority. -- 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-8294) [Broker-J][Oracle Message Store] Batch delete fails for more than 1000 messages
[
https://issues.apache.org/jira/browse/QPID-8294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811065#comment-16811065
]
ASF GitHub Bot commented on QPID-8294:
--
alex-rufous commented on pull request #23: QPID-8294: [Broker-J][Oracle Message
Store] Batch delete fails for more than 1000 messages
URL: https://github.com/apache/qpid-broker-j/pull/23#discussion_r272668667
##
File path:
broker-plugins/jdbc-store/src/main/java/org/apache/qpid/server/store/jdbc/AbstractJDBCMessageStore.java
##
@@ -82,6 +82,8 @@
private static final String XID_TABLE_NAME_SUFFIX = "QPID_XIDS";
private static final String XID_ACTIONS_TABLE_NAME_SUFFIX =
"QPID_XID_ACTIONS";
+private static final int MAX_DELETE_BATCH_SIZE = 1000;
Review comment:
I think it would be beneficial to set maximum delete batch size using JVM
system variable in case if other RDBMS have a lower limit. Something like below
`private static final int MAX_DELETE_BATCH_SIZE =
Integer.getInteger("qpid.jdbcStoreMaxDeleteBatchSize",1000);`
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
> [Broker-J][Oracle Message Store] Batch delete fails for more than 1000
> messages
> ---
>
> Key: QPID-8294
> URL: https://issues.apache.org/jira/browse/QPID-8294
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.0
>Reporter: Olivier VERMEULEN
>Priority: Critical
>
> When under high load, the Broker-J can end up having to delete more than 1000
> messages in a single batch. But some databases (and Oracle in particular) put
> a limit to the number of elements you can have in the IN clause. So we end up
> with the following exception: ORA-01795: maximum number of expressions in a
> list is 1000
--
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
[GitHub] [qpid-broker-j] alex-rufous commented on a change in pull request #23: QPID-8294: [Broker-J][Oracle Message Store] Batch delete fails for more than 1000 messages
alex-rufous commented on a change in pull request #23: QPID-8294:
[Broker-J][Oracle Message Store] Batch delete fails for more than 1000 messages
URL: https://github.com/apache/qpid-broker-j/pull/23#discussion_r272668667
##
File path:
broker-plugins/jdbc-store/src/main/java/org/apache/qpid/server/store/jdbc/AbstractJDBCMessageStore.java
##
@@ -82,6 +82,8 @@
private static final String XID_TABLE_NAME_SUFFIX = "QPID_XIDS";
private static final String XID_ACTIONS_TABLE_NAME_SUFFIX =
"QPID_XID_ACTIONS";
+private static final int MAX_DELETE_BATCH_SIZE = 1000;
Review comment:
I think it would be beneficial to set maximum delete batch size using JVM
system variable in case if other RDBMS have a lower limit. Something like below
`private static final int MAX_DELETE_BATCH_SIZE =
Integer.getInteger("qpid.jdbcStoreMaxDeleteBatchSize",1000);`
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
With regards,
Apache Git Services
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8295) Receiving a large message with a jms polling consumer with timeout of 1 sec can hang when the timeout is reached while message is in transfer.
Bas created QPID-8295: - Summary: Receiving a large message with a jms polling consumer with timeout of 1 sec can hang when the timeout is reached while message is in transfer. Key: QPID-8295 URL: https://issues.apache.org/jira/browse/QPID-8295 Project: Qpid Issue Type: Bug Components: Java Common Affects Versions: Future Environment: Windows Reporter: Bas Attachments: LargeJmsMessageConsumerTest.java Receiving a large message with a polling consumer with timeout of 1 sec can hang when the timeout is reached while message is in transfer. Message is not delivered and further polling is discontinued Test case included but timing maybe difficult when running on a different machine. Try chaning the sleep in the test case or increasing the message size. -- 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
[GitHub] [qpid-dispatch] asfgit closed pull request #481: DISPATCH_1309 - Prevent crash seen with connection close from the console
asfgit closed pull request #481: DISPATCH_1309 - Prevent crash seen with connection close from the console URL: https://github.com/apache/qpid-dispatch/pull/481 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 With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1309) Various crashes in 1.6 release
[
https://issues.apache.org/jira/browse/DISPATCH-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810830#comment-16810830
]
ASF subversion and git services commented on DISPATCH-1309:
---
Commit 57c3603c427a44d7d1a4490650a622d67a1ef7d6 in qpid-dispatch's branch
refs/heads/master from Ted Ross
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=57c3603 ]
DISPATCH-1309 - Repurposed unused qd_connection_t.closed flag to prevent
writable processing on closed connections.
This closes #481
> Various crashes in 1.6 release
> --
>
> Key: DISPATCH-1309
> URL: https://issues.apache.org/jira/browse/DISPATCH-1309
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.6.0
> Environment: System 'unused':(
> Fedora 5.0.3-200.fc29.x86_64,
> Python 2.7.15,
> Proton master @ eab1f.
> System 'taj':(
> Fedora 4.18.16-200.fc28.x86_64,
> Python 3.6.6,
> Proton master @ 68b38
>Reporter: Chuck Rolke
>Priority: Major
> Attachments: DISPATCH-1309-backtraces.txt,
> DISPATCH-1309-gen_configs_linear.py
>
>
> qpid-dispatch master @ 51244, which is very close to the 1.6 release, has
> various crashes.
> The test network is 12 routers spread over two systems. (Configuration
> generator to be attached.) Four interior routers are in linear arrangement
> with A and C on one system ('unused'), and B and D on the other system
> ('taj'). Each system then attaches four edge routers, one to each interior
> router.
> Running lightweight tests, like proton cpp simple_send and simple_recv to
> ports on INTA and INTB interior routers leads to a crash on INTC. The crashes
> typically look like reuse of structures after they have been freed (addresses
> are 0x). Other crashes hint of general memory corruption
> (crashes in malloc.c).
>
--
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] [Updated] (QPID-8294) [Broker-J][Oracle Message Store] Batch delete fails for more than 1000 messages
[ https://issues.apache.org/jira/browse/QPID-8294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier VERMEULEN updated QPID-8294: Priority: Critical (was: Major) > [Broker-J][Oracle Message Store] Batch delete fails for more than 1000 > messages > --- > > Key: QPID-8294 > URL: https://issues.apache.org/jira/browse/QPID-8294 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Olivier VERMEULEN >Priority: Critical > > When under high load, the Broker-J can end up having to delete more than 1000 > messages in a single batch. But some databases (and Oracle in particular) put > a limit to the number of elements you can have in the IN clause. So we end up > with the following exception: ORA-01795: maximum number of expressions in a > list is 1000 -- 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
