[jira] [Resolved] (PROTON-2731) [proton-dotnet] Perform Receive call timeout validation before waiting
[ https://issues.apache.org/jira/browse/PROTON-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish resolved PROTON-2731. - Resolution: Fixed > [proton-dotnet] Perform Receive call timeout validation before waiting > -- > > Key: PROTON-2731 > URL: https://issues.apache.org/jira/browse/PROTON-2731 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-dotnet >Affects Versions: proton-dotnet-1.0.0-M8 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: proton-dotnet-1.0.0-M9 > > > Calls in IReceiver and IStreamReceiver to wait on a delivery need to check > that the timeout value is not greater than UInt32.MaxValue milliseconds of > the inboult .NET Task API will fail internally in the receiver code and block > the call from ever completing. This should be checked early to prevent a > client call hang. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2731) [proton-dotnet] Perform Receive call timeout validation before waiting
[ https://issues.apache.org/jira/browse/PROTON-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721109#comment-17721109 ] ASF subversion and git services commented on PROTON-2731: - Commit bd1a0da76ba86a2f2ae9c85f13b8d74e8ca9017e in qpid-proton-dotnet's branch refs/heads/main from Timothy Bish [ https://gitbox.apache.org/repos/asf?p=qpid-proton-dotnet.git;h=bd1a0da ] PROTON-2731 Validate timeout value passed to Receive early Prevent the event loop handler from getting blocked by unexpected error from the task API delay feature. > [proton-dotnet] Perform Receive call timeout validation before waiting > -- > > Key: PROTON-2731 > URL: https://issues.apache.org/jira/browse/PROTON-2731 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-dotnet >Affects Versions: proton-dotnet-1.0.0-M8 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: proton-dotnet-1.0.0-M9 > > > Calls in IReceiver and IStreamReceiver to wait on a delivery need to check > that the timeout value is not greater than UInt32.MaxValue milliseconds of > the inboult .NET Task API will fail internally in the receiver code and block > the call from ever completing. This should be checked early to prevent a > client call hang. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Call for Presentations, Community Over Code 2023
(Note: You are receiving this because you are subscribed to the dev@ list for one or more Apache Software Foundation projects.) The Call for Presentations (CFP) for Community Over Code (formerly Apachecon) 2023 is open at https://communityovercode.org/call-for-presentations/, and will close Thu, 13 Jul 2023 23:59:59 GMT. The event will be held in Halifax, Canada, October 7-10, 2023. We welcome submissions on any topic related to the Apache Software Foundation, Apache projects, or the communities around those projects. We are specifically looking for presentations in the following catetegories: Fintech Search Big Data, Storage Big Data, Compute Internet of Things Groovy Incubator Community Data Engineering Performance Engineering Geospatial API/Microservices Frameworks Content Wrangling Tomcat and httpd Cloud and Runtime Streaming Sustainability - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2731) [proton-dotnet] Perform Receive call timeout validation before waiting
Timothy A. Bish created PROTON-2731: --- Summary: [proton-dotnet] Perform Receive call timeout validation before waiting Key: PROTON-2731 URL: https://issues.apache.org/jira/browse/PROTON-2731 Project: Qpid Proton Issue Type: Improvement Components: proton-dotnet Affects Versions: proton-dotnet-1.0.0-M8 Reporter: Timothy A. Bish Assignee: Timothy A. Bish Fix For: proton-dotnet-1.0.0-M9 Calls in IReceiver and IStreamReceiver to wait on a delivery need to check that the timeout value is not greater than UInt32.MaxValue milliseconds of the inboult .NET Task API will fail internally in the receiver code and block the call from ever completing. This should be checked early to prevent a client call hang. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2730) [proton-dotnet] AMQP Messaging types ToString improvements
[ https://issues.apache.org/jira/browse/PROTON-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish resolved PROTON-2730. - Resolution: Fixed > [proton-dotnet] AMQP Messaging types ToString improvements > -- > > Key: PROTON-2730 > URL: https://issues.apache.org/jira/browse/PROTON-2730 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-dotnet >Affects Versions: proton-dotnet-1.0.0-M8 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Minor > Fix For: proton-dotnet-1.0.0-M9 > > > The types in the AMQP Messaging package like DeliveryAnnotations, > MessageAnnotations and ApplicationProperties should enumerate the internal > collections in their ToString implementation into something that shows the > actual contents since the .NET collection types don't implement proper > ToString methods. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2730) [proton-dotnet] AMQP Messaging types ToString improvements
[ https://issues.apache.org/jira/browse/PROTON-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721060#comment-17721060 ] ASF subversion and git services commented on PROTON-2730: - Commit ebd55c331b930274d7a2fbc17bb1e194db0d0bd6 in qpid-proton-dotnet's branch refs/heads/main from Timothy Bish [ https://gitbox.apache.org/repos/asf?p=qpid-proton-dotnet.git;h=ebd55c3 ] PROTON-2730 Improve ToString for AMQP messaging types The collection types need to implement a smarter ToString method in order to display contents in logging or output. > [proton-dotnet] AMQP Messaging types ToString improvements > -- > > Key: PROTON-2730 > URL: https://issues.apache.org/jira/browse/PROTON-2730 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-dotnet >Affects Versions: proton-dotnet-1.0.0-M8 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Minor > Fix For: proton-dotnet-1.0.0-M9 > > > The types in the AMQP Messaging package like DeliveryAnnotations, > MessageAnnotations and ApplicationProperties should enumerate the internal > collections in their ToString implementation into something that shows the > actual contents since the .NET collection types don't implement proper > ToString methods. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2730) [proton-dotnet] AMQP Messaging types ToString improvements
Timothy A. Bish created PROTON-2730: --- Summary: [proton-dotnet] AMQP Messaging types ToString improvements Key: PROTON-2730 URL: https://issues.apache.org/jira/browse/PROTON-2730 Project: Qpid Proton Issue Type: Improvement Components: proton-dotnet Affects Versions: proton-dotnet-1.0.0-M8 Reporter: Timothy A. Bish Assignee: Timothy A. Bish Fix For: proton-dotnet-1.0.0-M9 The types in the AMQP Messaging package like DeliveryAnnotations, MessageAnnotations and ApplicationProperties should enumerate the internal collections in their ToString implementation into something that shows the actual contents since the .NET collection types don't implement proper ToString methods. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2729) [proton-dotnet] Ensure logging on failed connect displays remote location data
[ https://issues.apache.org/jira/browse/PROTON-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish resolved PROTON-2729. - Resolution: Fixed > [proton-dotnet] Ensure logging on failed connect displays remote location data > -- > > Key: PROTON-2729 > URL: https://issues.apache.org/jira/browse/PROTON-2729 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-dotnet >Affects Versions: proton-dotnet-1.0.0-M8 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Minor > Fix For: proton-dotnet-1.0.0-M9 > > > The logging for transport connection failures can end up logging null for the > remote location because a transport channel doesn't get populated for remote > endpoint details unless a successful connection is made. Instead log the > configure host and port values which are always set. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2729) [proton-dotnet] Ensure logging on failed connect displays remote location data
[ https://issues.apache.org/jira/browse/PROTON-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721028#comment-17721028 ] ASF subversion and git services commented on PROTON-2729: - Commit 62c409728edf2200087fe4e5edba672169b2d6ca in qpid-proton-dotnet's branch refs/heads/main from Timothy Bish [ https://gitbox.apache.org/repos/asf?p=qpid-proton-dotnet.git;h=62c4097 ] PROTON-2729 Ensure that a connect failed error message has details Log using the configured remote host and port and not the resulting resolved Endpoint which isn't populated if the channel has been fully connected. > [proton-dotnet] Ensure logging on failed connect displays remote location data > -- > > Key: PROTON-2729 > URL: https://issues.apache.org/jira/browse/PROTON-2729 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-dotnet >Affects Versions: proton-dotnet-1.0.0-M8 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Minor > Fix For: proton-dotnet-1.0.0-M9 > > > The logging for transport connection failures can end up logging null for the > remote location because a transport channel doesn't get populated for remote > endpoint details unless a successful connection is made. Instead log the > configure host and port values which are always set. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2729) [proton-dotnet] Ensure logging on failed connect displays remote location data
Timothy A. Bish created PROTON-2729: --- Summary: [proton-dotnet] Ensure logging on failed connect displays remote location data Key: PROTON-2729 URL: https://issues.apache.org/jira/browse/PROTON-2729 Project: Qpid Proton Issue Type: Improvement Components: proton-dotnet Affects Versions: proton-dotnet-1.0.0-M8 Reporter: Timothy A. Bish Assignee: Timothy A. Bish Fix For: proton-dotnet-1.0.0-M9 The logging for transport connection failures can end up logging null for the remote location because a transport channel doesn't get populated for remote endpoint details unless a successful connection is made. Instead log the configure host and port values which are always set. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2728) [proton-dotnet] Fix some spelling and clean up some API docs
[ https://issues.apache.org/jira/browse/PROTON-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720976#comment-17720976 ] ASF subversion and git services commented on PROTON-2728: - Commit e3a5997ea6555410526d2148c420da56e61c9364 in qpid-proton-dotnet's branch refs/heads/main from Timothy Bish [ https://gitbox.apache.org/repos/asf?p=qpid-proton-dotnet.git;h=e3a5997 ] PROTON-2728 Fix some API doc spelling errors > [proton-dotnet] Fix some spelling and clean up some API docs > > > Key: PROTON-2728 > URL: https://issues.apache.org/jira/browse/PROTON-2728 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-dotnet >Affects Versions: proton-dotnet-1.0.0-M8 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: proton-dotnet-1.0.0-M9 > > > Some client API docs needed -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2728) [proton-dotnet] Fix some spelling and clean up some API docs
Timothy A. Bish created PROTON-2728: --- Summary: [proton-dotnet] Fix some spelling and clean up some API docs Key: PROTON-2728 URL: https://issues.apache.org/jira/browse/PROTON-2728 Project: Qpid Proton Issue Type: Improvement Components: proton-dotnet Affects Versions: proton-dotnet-1.0.0-M8 Reporter: Timothy A. Bish Assignee: Timothy A. Bish Fix For: proton-dotnet-1.0.0-M9 Some client API docs needed -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2726) [proton-dotnet] v1.0.0-M8 release tasks
[ https://issues.apache.org/jira/browse/PROTON-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish resolved PROTON-2726. - Resolution: Fixed > [proton-dotnet] v1.0.0-M8 release tasks > --- > > Key: PROTON-2726 > URL: https://issues.apache.org/jira/browse/PROTON-2726 > Project: Qpid Proton > Issue Type: Task > Components: proton-dotnet >Affects Versions: proton-dotnet-1.0.0-M7 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Minor > Fix For: proton-dotnet-1.0.0-M8 > > > Tasks needed to update the project for v1.0.0-M8 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2727) Support reading keystore from class path
[
https://issues.apache.org/jira/browse/PROTON-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720937#comment-17720937
]
Timothy A. Bish commented on PROTON-2727:
-
You can implement that yourself as the SslOptions allow you to provide an
SSLContext that will override anything the client would do normally. You can
load the resources you want and create a context prior to configuring the
connection and the client will just use what you gave it.
> Support reading keystore from class path
>
>
> Key: PROTON-2727
> URL: https://issues.apache.org/jira/browse/PROTON-2727
> Project: Qpid Proton
> Issue Type: Improvement
> Components: protonj2
>Affects Versions: protonj2-1.0.0-M15
>Reporter: Lester Ward
>Assignee: Timothy A. Bish
>Priority: Minor
>
> It would be useful if {{ConnectionOptions}} allowed you to supply an SSL
> keystore from a resource on the classpath in some way. One possibility would
> be:
> {{options.keyStoreLocation("classpath:com/my/thing/ks.p12")}}
> Another option would be adding a method to take a stream or bytes or Reader
> or something instead of {{String}} for this option.
> Sadly, {{File}} doesn't handle {{classpath:}} URLs on its own.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2727) Support reading keystore from class path
Lester Ward created PROTON-2727:
---
Summary: Support reading keystore from class path
Key: PROTON-2727
URL: https://issues.apache.org/jira/browse/PROTON-2727
Project: Qpid Proton
Issue Type: Improvement
Components: protonj2
Affects Versions: protonj2-1.0.0-M15
Reporter: Lester Ward
Assignee: Timothy A. Bish
It would be useful if {{ConnectionOptions}} allowed you to supply an SSL
keystore from a resource on the classpath in some way. One possibility would be:
{{options.keyStoreLocation("classpath:com/my/thing/ks.p12")}}
Another option would be adding a method to take a stream or bytes or Reader or
something instead of {{String}} for this option.
Sadly, {{File}} doesn't handle {{classpath:}} URLs on its own.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8640) [Broker-J] Remove producer on link destruction
[
https://issues.apache.org/jira/browse/QPID-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka resolved QPID-8640.
--
Resolution: Fixed
> [Broker-J] Remove producer on link destruction
> --
>
> Key: QPID-8640
> URL: https://issues.apache.org/jira/browse/QPID-8640
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.0.1
>
>
> In some test scenarios following error is thrown on the client side:
> {code:java}
> proton._utils.LinkDetached: sender
> c83ab7c1-a1f4-4d3d-b7f9-527fabf9e9dd-broadcast to broadcast closed due to:
> Condition('amqp:internal-error', 'Child of type ProducerImpl already exists
> with name of c83ab7c1-a1f4-4d3d-b7f9-527fabf9e9dd-broadcast'){code}
> It seems, that producer is closed after calling sender.close() on the client
> side, but still remains to be a child of an appropriate AMQP session in
> closed state, preventing producer with the same name to be created.
> StandardReceivingLinkEndpoint#destroy() should be extended with the producer
> removal.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8640) [Broker-J] Remove producer on link destruction
[
https://issues.apache.org/jira/browse/QPID-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720879#comment-17720879
]
ASF GitHub Bot commented on QPID-8640:
--
vavrtom merged PR #179:
URL: https://github.com/apache/qpid-broker-j/pull/179
> [Broker-J] Remove producer on link destruction
> --
>
> Key: QPID-8640
> URL: https://issues.apache.org/jira/browse/QPID-8640
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.0.1
>
>
> In some test scenarios following error is thrown on the client side:
> {code:java}
> proton._utils.LinkDetached: sender
> c83ab7c1-a1f4-4d3d-b7f9-527fabf9e9dd-broadcast to broadcast closed due to:
> Condition('amqp:internal-error', 'Child of type ProducerImpl already exists
> with name of c83ab7c1-a1f4-4d3d-b7f9-527fabf9e9dd-broadcast'){code}
> It seems, that producer is closed after calling sender.close() on the client
> side, but still remains to be a child of an appropriate AMQP session in
> closed state, preventing producer with the same name to be created.
> StandardReceivingLinkEndpoint#destroy() should be extended with the producer
> removal.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8640) [Broker-J] Remove producer on link destruction
[
https://issues.apache.org/jira/browse/QPID-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720880#comment-17720880
]
ASF subversion and git services commented on QPID-8640:
---
Commit 9f3c334b9551fe2edc43b6bb387843f8d6c88e5c in qpid-broker-j's branch
refs/heads/main from Daniil Kirilyuk
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=9f3c334b95 ]
QPID-8640: [Broker-J] Remove producer on link destruction (#179)
> [Broker-J] Remove producer on link destruction
> --
>
> Key: QPID-8640
> URL: https://issues.apache.org/jira/browse/QPID-8640
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.0.1
>
>
> In some test scenarios following error is thrown on the client side:
> {code:java}
> proton._utils.LinkDetached: sender
> c83ab7c1-a1f4-4d3d-b7f9-527fabf9e9dd-broadcast to broadcast closed due to:
> Condition('amqp:internal-error', 'Child of type ProducerImpl already exists
> with name of c83ab7c1-a1f4-4d3d-b7f9-527fabf9e9dd-broadcast'){code}
> It seems, that producer is closed after calling sender.close() on the client
> side, but still remains to be a child of an appropriate AMQP session in
> closed state, preventing producer with the same name to be created.
> StandardReceivingLinkEndpoint#destroy() should be extended with the producer
> removal.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-broker-j] vavrtom merged pull request #179: QPID-8640: [Broker-J] Remove producer on link destruction
vavrtom merged PR #179: URL: https://github.com/apache/qpid-broker-j/pull/179 -- 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. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org 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
