[jira] [Resolved] (QPIDJMS-600) Session and Connection close should await async send completion

2024-04-19 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved QPIDJMS-600.
-
Resolution: Fixed

> Session and Connection close should await async send completion
> ---
>
> Key: QPIDJMS-600
> URL: https://issues.apache.org/jira/browse/QPIDJMS-600
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 2.5.0
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: 2.6.0
>
>
> According to the JMS specification the close of a session or connection 
> should be allowing for messages sent via the asynchronous API to complete 
> normally before completing the close.  Currently this is not being allow to 
> happen and pending asynchronous sends are failed from a call to session or 
> connection close.  The MessageProducer close is awaiting completion of 
> asynchronous sends as the specification requires.  



--
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] [Closed] (QPIDJMS-599) JmsTransactionInDoubtException: error

2024-04-19 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish closed QPIDJMS-599.
---
Resolution: Information Provided

> JmsTransactionInDoubtException: error
> -
>
> Key: QPIDJMS-599
> URL: https://issues.apache.org/jira/browse/QPIDJMS-599
> Project: Qpid JMS
>  Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Rajesh Kumar
>Priority: Major
> Attachments: JMS_Exception_Details.txt
>
>
> Hi Team,
> we are receiving the following error intermittently
>  
> Exception Details related JmsTransactionInDoubtException:
>  
> Call Stack: org.apache.qpid.jms.JmsTransactionInDoubtException: Transaction 
> is not declared Reference:9a13135d-348c-4a78-b53c-097a11ac103f, 
> TrackingId:8ee88669-b631-4261-93eb-09b9beded92f_G8S3, SystemTracker:gtm, 
> Timestamp:2024-03-05T01:40:45 [condition = amqp:transaction:unknown-id]
> at 
> org.apache.qpid.jms.provider.exceptions.ProviderTransactionInDoubtException.toJMSException(ProviderTransactionInDoubtException.java:39)
> at 
> org.apache.qpid.jms.provider.exceptions.ProviderTransactionInDoubtException.toJMSException(ProviderTransactionInDoubtException.java:25)
>  
> Kindly help in fixing this error in priority



--
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] (QPIDJMS-600) Session and Connection close should await async send completion

2024-04-17 Thread Timothy A. Bish (Jira)
Timothy A. Bish created QPIDJMS-600:
---

 Summary: Session and Connection close should await async send 
completion
 Key: QPIDJMS-600
 URL: https://issues.apache.org/jira/browse/QPIDJMS-600
 Project: Qpid JMS
  Issue Type: Bug
  Components: qpid-jms-client
Affects Versions: 2.5.0
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: 2.6.0


According to the JMS specification the close of a session or connection should 
be allowing for messages sent via the asynchronous API to complete normally 
before completing the close.  Currently this is not being allow to happen and 
pending asynchronous sends are failed from a call to session or connection 
close.  The MessageProducer close is awaiting completion of asynchronous sends 
as the specification requires.  



--
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] (QPIDJMS-599) JmsTransactionInDoubtException: error

2024-04-16 Thread Timothy A. Bish (Jira)


[ 
https://issues.apache.org/jira/browse/QPIDJMS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837833#comment-17837833
 ] 

Timothy A. Bish commented on QPIDJMS-599:
-

>From the details provided the client sent a request to rollback a transaction 
>due to a call to {code:java}session.rollback(){code} by the application.  The 
>server responds with an error indicating that it doesn't have any record of 
>the specified transaction which is acceptable as the JMS API does indicate 
>that the rollback method can throw due to internal errors.  The application 
>should be catching and maybe logging this or otherwise handling it.  There is 
>likely a connection drop and reconnect happening which leads to this but it is 
>a bit hard to say for sure.  There isn't much the client can do but throw as 
>the remote has told it what it attempted failed.  

> JmsTransactionInDoubtException: error
> -
>
> Key: QPIDJMS-599
> URL: https://issues.apache.org/jira/browse/QPIDJMS-599
> Project: Qpid JMS
>  Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Rajesh Kumar
>Priority: Major
> Attachments: JMS_Exception_Details.txt
>
>
> Hi Team,
> we are receiving the following error intermittently
>  
> Exception Details related JmsTransactionInDoubtException:
>  
> Call Stack: org.apache.qpid.jms.JmsTransactionInDoubtException: Transaction 
> is not declared Reference:9a13135d-348c-4a78-b53c-097a11ac103f, 
> TrackingId:8ee88669-b631-4261-93eb-09b9beded92f_G8S3, SystemTracker:gtm, 
> Timestamp:2024-03-05T01:40:45 [condition = amqp:transaction:unknown-id]
> at 
> org.apache.qpid.jms.provider.exceptions.ProviderTransactionInDoubtException.toJMSException(ProviderTransactionInDoubtException.java:39)
> at 
> org.apache.qpid.jms.provider.exceptions.ProviderTransactionInDoubtException.toJMSException(ProviderTransactionInDoubtException.java:25)
>  
> Kindly help in fixing this error in priority



--
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-2766) [proton-dotnet] Add additional documentation to project

2024-04-08 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2766.
-
Resolution: Fixed

> [proton-dotnet] Add additional documentation to project
> ---
>
> Key: PROTON-2766
> URL: https://issues.apache.org/jira/browse/PROTON-2766
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-dotnet
>Affects Versions: proton-dotnet-1.0.0-M9
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: proton-dotnet-1.0.0-M10
>
>
> Add basic documentation for usage and some options documentation for various 
> client resources.



--
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-2811) [proton-dotnet] v1.0.0-M10 release tasks

2024-04-08 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2811.
-
Resolution: Fixed

> [proton-dotnet] v1.0.0-M10 release tasks
> 
>
> Key: PROTON-2811
> URL: https://issues.apache.org/jira/browse/PROTON-2811
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-dotnet
>Affects Versions: proton-dotnet-1.0.0-M9
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Trivial
> Fix For: proton-dotnet-1.0.0-M10
>
>
> Update for release of version 1.0.0-M10



--
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-2811) [proton-dotnet] v1.0.0-M10 release tasks

2024-04-08 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2811:
---

 Summary: [proton-dotnet] v1.0.0-M10 release tasks
 Key: PROTON-2811
 URL: https://issues.apache.org/jira/browse/PROTON-2811
 Project: Qpid Proton
  Issue Type: Task
  Components: proton-dotnet
Affects Versions: proton-dotnet-1.0.0-M9
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: proton-dotnet-1.0.0-M10


Update for release of version 1.0.0-M10



--
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-2798) [protonj2] Update test dependencies to latest releases

2024-03-25 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2798.
-
Resolution: Fixed

> [protonj2] Update test dependencies to latest releases
> --
>
> Key: PROTON-2798
> URL: https://issues.apache.org/jira/browse/PROTON-2798
> Project: Qpid Proton
>  Issue Type: Task
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M20
>
>
> Update test dependencies to latest release



--
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-2802) [protonj2] Add additional validation scripting to the AMQP test peer

2024-03-25 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2802.
-
Resolution: Fixed

> [protonj2] Add additional validation scripting to the AMQP test peer
> 
>
> Key: PROTON-2802
> URL: https://issues.apache.org/jira/browse/PROTON-2802
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M20
>
>
> Expand the test scripting APIs to make test writing easier in some cases



--
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-2797) [protonj2] Update Netty to latest release

2024-03-25 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2797.
-
Resolution: Fixed

> [protonj2] Update Netty to latest release
> -
>
> Key: PROTON-2797
> URL: https://issues.apache.org/jira/browse/PROTON-2797
> Project: Qpid Proton
>  Issue Type: Task
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M20
>
>
> Update netty and its dependencies to latest release



--
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-2727) [protonj2] Support reading keystore from class path

2024-03-19 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2727.
-
Fix Version/s: protonj2-1.0.0-M20
   Resolution: Fixed

Added ability to indicate "classpath:" prefix on the store locations values

> [protonj2] 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
> Fix For: protonj2-1.0.0-M20
>
>
> 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] [Updated] (PROTON-2727) [protonj2] Support reading keystore from class path

2024-03-19 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish updated PROTON-2727:

Summary: [protonj2] Support reading keystore from class path  (was: Support 
reading keystore from class path)

> [protonj2] 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] [Resolved] (PROTON-2809) [protonj2] Exception when composite buffer reads empty Data section payload

2024-03-18 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2809.
-
Resolution: Fixed

> [protonj2] Exception when composite buffer reads empty Data section payload
> ---
>
> Key: PROTON-2809
> URL: https://issues.apache.org/jira/browse/PROTON-2809
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M20
>
>
> When reading a transfer payload and attempting to decode, if the payload was 
> split across frames and is carried in a composite buffer an exception can 
> occur if the Data section in the body carries a null instead of an encoded 
> Binary type.
> {code:java}
> Caused by: org.apache.qpid.protonj2.client.exceptions.ClientException:
> Index 1 out of bounds for length 1
> at
> org.apache.qpid.protonj2.client.impl.ClientExceptionSupport.createNonFatalOrPassthrough(
> ClientExceptionSupport.java:103)
> at org.apache.qpid.protonj2.client.impl.ClientMessageSupport.decodeMessage(
> ClientMessageSupport.java:170)
> at org.apache.qpid.protonj2.client.impl.ClientMessageSupport.decodeMessage(
> ClientMessageSupport.java:152)
> at org.apache.qpid.protonj2.client.impl.ClientDelivery.message(
> ClientDelivery.java:79)
> at
> com.thisisnumero.smartagent.gateway.inbound.sources.background.amqp.AMQPMessageConsumerImpl.internalConsumeMessages(
> AMQPMessageConsumerImpl.java:53)
> ... 4 more
> Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds
> for length 1
> at
> org.apache.qpid.protonj2.buffer.impl.ProtonCompositeBufferImpl.findChunkWithIndex(
> ProtonCompositeBufferImpl.java:1530)
> at org.apache.qpid.protonj2.buffer.impl.ProtonCompositeBufferImpl.copyInto(
> ProtonCompositeBufferImpl.java:387)
> at
> org.apache.qpid.protonj2.codec.decoders.messaging.DataTypeDecoder.readValue(
> DataTypeDecoder.java:85)
> at
> org.apache.qpid.protonj2.codec.decoders.messaging.DataTypeDecoder.readValue(
> DataTypeDecoder.java:40)
> at org.apache.qpid.protonj2.codec.decoders.ProtonDecoder.readObject(
> ProtonDecoder.java:192)
> at org.apache.qpid.protonj2.client.impl.ClientMessageSupport.decodeMessage(
> ClientMessageSupport.java:168) {code}



--
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-2809) [protonj2] Exception when composite buffer reads empty Data section payload

2024-03-18 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2809:
---

 Summary: [protonj2] Exception when composite buffer reads empty 
Data section payload
 Key: PROTON-2809
 URL: https://issues.apache.org/jira/browse/PROTON-2809
 Project: Qpid Proton
  Issue Type: Bug
  Components: protonj2
Affects Versions: protonj2-1.0.0-M19
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M20


When reading a transfer payload and attempting to decode, if the payload was 
split across frames and is carried in a composite buffer an exception can occur 
if the Data section in the body carries a null instead of an encoded Binary 
type.
{code:java}
Caused by: org.apache.qpid.protonj2.client.exceptions.ClientException:
Index 1 out of bounds for length 1

at
org.apache.qpid.protonj2.client.impl.ClientExceptionSupport.createNonFatalOrPassthrough(
ClientExceptionSupport.java:103)

at org.apache.qpid.protonj2.client.impl.ClientMessageSupport.decodeMessage(
ClientMessageSupport.java:170)

at org.apache.qpid.protonj2.client.impl.ClientMessageSupport.decodeMessage(
ClientMessageSupport.java:152)

at org.apache.qpid.protonj2.client.impl.ClientDelivery.message(
ClientDelivery.java:79)

at
com.thisisnumero.smartagent.gateway.inbound.sources.background.amqp.AMQPMessageConsumerImpl.internalConsumeMessages(
AMQPMessageConsumerImpl.java:53)

... 4 more

Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds
for length 1

at
org.apache.qpid.protonj2.buffer.impl.ProtonCompositeBufferImpl.findChunkWithIndex(
ProtonCompositeBufferImpl.java:1530)

at org.apache.qpid.protonj2.buffer.impl.ProtonCompositeBufferImpl.copyInto(
ProtonCompositeBufferImpl.java:387)

at
org.apache.qpid.protonj2.codec.decoders.messaging.DataTypeDecoder.readValue(
DataTypeDecoder.java:85)

at
org.apache.qpid.protonj2.codec.decoders.messaging.DataTypeDecoder.readValue(
DataTypeDecoder.java:40)

at org.apache.qpid.protonj2.codec.decoders.ProtonDecoder.readObject(
ProtonDecoder.java:192)

at org.apache.qpid.protonj2.client.impl.ClientMessageSupport.decodeMessage(
ClientMessageSupport.java:168) {code}



--
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-2808) [proton-dotnet] Prevent read timeout when partial frames are received slowly

2024-03-15 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2808.
-
Resolution: Fixed

> [proton-dotnet] Prevent read timeout when partial frames are received slowly
> 
>
> Key: PROTON-2808
> URL: https://issues.apache.org/jira/browse/PROTON-2808
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-dotnet
>Affects Versions: proton-dotnet-1.0.0-M9
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: proton-dotnet-1.0.0-M10
>
>
> Ensure that slowly accumulating partial frame packets are accounted for in 
> read actively and doesn't result in early idle timeouts from the read check 
> task



--
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-2808) [proton-dotnet] Prevent read timeout when partial frames are received slowly

2024-03-15 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2808:
---

 Summary: [proton-dotnet] Prevent read timeout when partial frames 
are received slowly
 Key: PROTON-2808
 URL: https://issues.apache.org/jira/browse/PROTON-2808
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-dotnet
Affects Versions: proton-dotnet-1.0.0-M9
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: proton-dotnet-1.0.0-M10


Ensure that slowly accumulating partial frame packets are accounted for in read 
actively and doesn't result in early idle timeouts from the read check task



--
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-2807) [protonj2] Prevent read timeout when partial frames are received slowly

2024-03-15 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2807.
-
Resolution: Fixed

> [protonj2] Prevent read timeout when partial frames are received slowly
> ---
>
> Key: PROTON-2807
> URL: https://issues.apache.org/jira/browse/PROTON-2807
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M20
>
>
> Ensure that slowly accumulating partial frame packets are accounted for in 
> read actively and doesn't result in early idle timeouts from the read check 
> task



--
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-2807) [protonj2] Prevent read timeout when partial frames are received slowly

2024-03-15 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2807:
---

 Summary: [protonj2] Prevent read timeout when partial frames are 
received slowly
 Key: PROTON-2807
 URL: https://issues.apache.org/jira/browse/PROTON-2807
 Project: Qpid Proton
  Issue Type: Bug
  Components: protonj2
Affects Versions: protonj2-1.0.0-M19
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M20


Ensure that slowly accumulating partial frame packets are accounted for in read 
actively and doesn't result in early idle timeouts from the read check task



--
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-2806) [protonj2] Fix incorrect error message in protocol violation exception

2024-03-14 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2806.
-
Resolution: Fixed

> [protonj2] Fix incorrect error message in protocol violation exception
> --
>
> Key: PROTON-2806
> URL: https://issues.apache.org/jira/browse/PROTON-2806
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Trivial
> Fix For: protonj2-1.0.0-M20
>
>
> When checking incoming Delivery IDs the session window throws an exception if 
> the value doesn't match the expected value but constructs an incorrect error 
> message for the expected value using the non-incremented value.



--
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-2806) [protonj2] Fix incorrect error message in protocol violation exception

2024-03-14 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2806:
---

 Summary: [protonj2] Fix incorrect error message in protocol 
violation exception
 Key: PROTON-2806
 URL: https://issues.apache.org/jira/browse/PROTON-2806
 Project: Qpid Proton
  Issue Type: Bug
  Components: protonj2
Affects Versions: protonj2-1.0.0-M19
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M20


When checking incoming Delivery IDs the session window throws an exception if 
the value doesn't match the expected value but constructs an incorrect error 
message for the expected value using the non-incremented value.



--
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-2805) [proton-dotnet] Client connection does no send half configured idle timeout

2024-03-14 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2805.
-
Resolution: Fixed

> [proton-dotnet] Client connection does no send half configured idle timeout
> ---
>
> Key: PROTON-2805
> URL: https://issues.apache.org/jira/browse/PROTON-2805
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-dotnet
>Affects Versions: proton-dotnet-1.0.0-M9
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: proton-dotnet-1.0.0-M10
>
>
> Client should send half the configured idle timeout however the configuration 
> code skips that and sends the full value.



--
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-2805) [proton-dotnet] Client connection does no send half configured idle timeout

2024-03-14 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2805:
---

 Summary: [proton-dotnet] Client connection does no send half 
configured idle timeout
 Key: PROTON-2805
 URL: https://issues.apache.org/jira/browse/PROTON-2805
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-dotnet
Affects Versions: proton-dotnet-1.0.0-M9
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: proton-dotnet-1.0.0-M10


Client should send half the configured idle timeout however the configuration 
code skips that and sends the full value.



--
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-2804) [protonj2] Client connection is not halving the idle timeout API says it will

2024-03-14 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2804.
-
Resolution: Fixed

> [protonj2] Client connection is not halving the idle timeout API says it will
> -
>
> Key: PROTON-2804
> URL: https://issues.apache.org/jira/browse/PROTON-2804
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M20
>
>
> The Connection options indicates the idle timeout value is halved when sent 
> to the remote in the Open however that is not being done currently



--
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-2804) [protonj2] Client connection is not halving the idle timeout API says it will

2024-03-14 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2804:
---

 Summary: [protonj2] Client connection is not halving the idle 
timeout API says it will
 Key: PROTON-2804
 URL: https://issues.apache.org/jira/browse/PROTON-2804
 Project: Qpid Proton
  Issue Type: Bug
  Components: protonj2
Affects Versions: protonj2-1.0.0-M19
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M20


The Connection options indicates the idle timeout value is halved when sent to 
the remote in the Open however that is not being done currently



--
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-2803) [protonj2] Reconnect options default max reconnect delay not set correctly

2024-03-12 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2803.
-
Resolution: Fixed

> [protonj2] Reconnect options default max reconnect delay not set correctly
> --
>
> Key: PROTON-2803
> URL: https://issues.apache.org/jira/browse/PROTON-2803
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M20
>
>
> The default value for max reconnect delay should be 30s according to docs but 
> was wrongly assigned the default initial delay of 10ms



--
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-2803) [protonj2] Reconnect options default max reconnect delay not set correctly

2024-03-12 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2803:
---

 Summary: [protonj2] Reconnect options default max reconnect delay 
not set correctly
 Key: PROTON-2803
 URL: https://issues.apache.org/jira/browse/PROTON-2803
 Project: Qpid Proton
  Issue Type: Bug
  Components: protonj2
Affects Versions: protonj2-1.0.0-M19
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M20


The default value for max reconnect delay should be 30s according to docs but 
was wrongly assigned the default initial delay of 10ms



--
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-2802) [protonj2] Add additional validation scripting to the AMQP test peer

2024-03-05 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2802:
---

 Summary: [protonj2] Add additional validation scripting to the 
AMQP test peer
 Key: PROTON-2802
 URL: https://issues.apache.org/jira/browse/PROTON-2802
 Project: Qpid Proton
  Issue Type: Improvement
  Components: protonj2
Affects Versions: protonj2-1.0.0-M19
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M20


Expand the test scripting APIs to make test writing easier in some cases



--
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-2794) [protonj2] Transfer ID does not wrap as expected

2024-03-05 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2794.
-
Resolution: Fixed

> [protonj2] Transfer ID does not wrap as expected
> 
>
> Key: PROTON-2794
> URL: https://issues.apache.org/jira/browse/PROTON-2794
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Arnaud Cogoluègnes
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M20
>
>
> When ProtonJ 2 creates a session and the peer replies with a large 
> {{next-outgoing-id}} in the {{begin}} response (e.g. 4294967292), a receiver 
> on the session throws an exception later on when it detects the 
> {{next-incoming-id}} is greater than the limit of a uint32.
> Corresponding code:
> [https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2/src/main/java/org/apache/qpid/protonj2/types/transport/Flow.java#L153-L155]
> [https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2/src/main/java/org/apache/qpid/protonj2/engine/impl/ProtonSessionIncomingWindow.java#L138]
> The {{transfer-id}} is a {{sequence-no}}, so it must follow 
> [RFC-1982|https://www.ietf.org/rfc/rfc1982.txt] and so wrap around (sections 
> 2.8.9 and 2.8.10 of the AMQP 1.0 spec).
> So from my understanding, the {{nextIncomingId}} field should be set to 0 
> when it "overflows" and no exception should be thrown.
> Other fields like {{delivery-count}} may have the same problem.



--
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] [Updated] (PROTON-2794) [protonj2] Transfer ID does not wrap as expected

2024-03-05 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish updated PROTON-2794:

Fix Version/s: protonj2-1.0.0-M20

> [protonj2] Transfer ID does not wrap as expected
> 
>
> Key: PROTON-2794
> URL: https://issues.apache.org/jira/browse/PROTON-2794
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Arnaud Cogoluègnes
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M20
>
>
> When ProtonJ 2 creates a session and the peer replies with a large 
> {{next-outgoing-id}} in the {{begin}} response (e.g. 4294967292), a receiver 
> on the session throws an exception later on when it detects the 
> {{next-incoming-id}} is greater than the limit of a uint32.
> Corresponding code:
> [https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2/src/main/java/org/apache/qpid/protonj2/types/transport/Flow.java#L153-L155]
> [https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2/src/main/java/org/apache/qpid/protonj2/engine/impl/ProtonSessionIncomingWindow.java#L138]
> The {{transfer-id}} is a {{sequence-no}}, so it must follow 
> [RFC-1982|https://www.ietf.org/rfc/rfc1982.txt] and so wrap around (sections 
> 2.8.9 and 2.8.10 of the AMQP 1.0 spec).
> So from my understanding, the {{nextIncomingId}} field should be set to 0 
> when it "overflows" and no exception should be thrown.
> Other fields like {{delivery-count}} may have the same problem.



--
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] [Updated] (PROTON-2794) [protonj2] Transfer ID does not wrap as expected

2024-03-05 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish updated PROTON-2794:

Summary: [protonj2] Transfer ID does not wrap as expected  (was: Transfer 
ID does not wrap as expected)

> [protonj2] Transfer ID does not wrap as expected
> 
>
> Key: PROTON-2794
> URL: https://issues.apache.org/jira/browse/PROTON-2794
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Arnaud Cogoluègnes
>Assignee: Timothy A. Bish
>Priority: Major
>
> When ProtonJ 2 creates a session and the peer replies with a large 
> {{next-outgoing-id}} in the {{begin}} response (e.g. 4294967292), a receiver 
> on the session throws an exception later on when it detects the 
> {{next-incoming-id}} is greater than the limit of a uint32.
> Corresponding code:
> [https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2/src/main/java/org/apache/qpid/protonj2/types/transport/Flow.java#L153-L155]
> [https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2/src/main/java/org/apache/qpid/protonj2/engine/impl/ProtonSessionIncomingWindow.java#L138]
> The {{transfer-id}} is a {{sequence-no}}, so it must follow 
> [RFC-1982|https://www.ietf.org/rfc/rfc1982.txt] and so wrap around (sections 
> 2.8.9 and 2.8.10 of the AMQP 1.0 spec).
> So from my understanding, the {{nextIncomingId}} field should be set to 0 
> when it "overflows" and no exception should be thrown.
> Other fields like {{delivery-count}} may have the same problem.



--
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-2800) [proton-dotnet] Ensure set message format get sent on first transfer frame

2024-02-28 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2800.
-
Resolution: Fixed

> [proton-dotnet] Ensure set message format get sent on first transfer frame
> --
>
> Key: PROTON-2800
> URL: https://issues.apache.org/jira/browse/PROTON-2800
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-dotnet
>Affects Versions: proton-dotnet-1.0.0-M9
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: proton-dotnet-1.0.0-M10
>
>
> Ensure that the message format value always get set on the first transfer 
> frame when set from the Advanced Message object or running with the defaults.



--
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] [Closed] (PROTON-2801) [proton-dotnet] Message format cannot be set to 0 on outbound messages

2024-02-28 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish closed PROTON-2801.
---
Resolution: Fixed

> [proton-dotnet] Message format cannot be set to 0 on outbound messages
> --
>
> Key: PROTON-2801
> URL: https://issues.apache.org/jira/browse/PROTON-2801
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-dotnet
>Affects Versions: proton-dotnet-1.0.0-M9
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: proton-dotnet-1.0.0-M10
>
>
> Ensure that outgoing transfer frames are always properly tagged with the set 
> message format and improve test coverage.



--
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-2801) [proton-dotnet] Message format cannot be set to 0 on outbound messages

2024-02-28 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2801:
---

 Summary: [proton-dotnet] Message format cannot be set to 0 on 
outbound messages
 Key: PROTON-2801
 URL: https://issues.apache.org/jira/browse/PROTON-2801
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-dotnet
Affects Versions: proton-dotnet-1.0.0-M9
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: proton-dotnet-1.0.0-M10


Ensure that outgoing transfer frames are always properly tagged with the set 
message format and improve test coverage.



--
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-2800) [proton-dotnet] Ensure set message format get sent on first transfer frame

2024-02-27 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2800:
---

 Summary: [proton-dotnet] Ensure set message format get sent on 
first transfer frame
 Key: PROTON-2800
 URL: https://issues.apache.org/jira/browse/PROTON-2800
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-dotnet
Affects Versions: proton-dotnet-1.0.0-M9
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: proton-dotnet-1.0.0-M10


Ensure that the message format value always get set on the first transfer frame 
when set from the Advanced Message object or running with the defaults.



--
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-2799) [proton-dotnet] Update sender create to match source and target address

2024-02-27 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2799.
-
Resolution: Fixed

> [proton-dotnet] Update sender create to match source and target address
> ---
>
> Key: PROTON-2799
> URL: https://issues.apache.org/jira/browse/PROTON-2799
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-dotnet
>Affects Versions: proton-dotnet-1.0.0-M9
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Trivial
> Fix For: proton-dotnet-1.0.0-M10
>
>
> Sender and Receiver create should both do the same action when building the 
> link objects, currently sender doesn't use the address value on source and 
> target while receiver does, we should match them and have them both use the 
> address value.
> Add tests to ensure they are both doing what we expect in this case



--
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-2799) [proton-dotnet] Update sender create to match source and target address

2024-02-27 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2799:
---

 Summary: [proton-dotnet] Update sender create to match source and 
target address
 Key: PROTON-2799
 URL: https://issues.apache.org/jira/browse/PROTON-2799
 Project: Qpid Proton
  Issue Type: Improvement
  Components: proton-dotnet
Affects Versions: proton-dotnet-1.0.0-M9
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: proton-dotnet-1.0.0-M10


Sender and Receiver create should both do the same action when building the 
link objects, currently sender doesn't use the address value on source and 
target while receiver does, we should match them and have them both use the 
address value.

Add tests to ensure they are both doing what we expect in this case



--
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] [Updated] (PROTON-2795) [protonj2] Message format cannot be set to 0 on outbound messages

2024-02-27 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish updated PROTON-2795:

Summary: [protonj2] Message format cannot be set to 0 on outbound messages  
(was: Message format cannot be set to 0 on outbound messages)

> [protonj2] Message format cannot be set to 0 on outbound messages
> -
>
> Key: PROTON-2795
> URL: https://issues.apache.org/jira/browse/PROTON-2795
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Arnaud Cogoluègnes
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M20
>
>
> Setting the message format to 0 or keeping the default value results in a 
> null value in the {{transfer}} frame.
> 0 seems to be considered [a special 
> value|https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2/src/main/java/org/apache/qpid/protonj2/engine/impl/ProtonSessionOutgoingWindow.java#L270-L274]
>  in the code.
> This contradicts [the 
> Javadoc|https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2-client/src/main/java/org/apache/qpid/protonj2/client/AdvancedMessage.java#L170-L200]:
> {quote}This field MUST be specified for the first transfer of a 
> multi-transfer message, if it is not set at the time of send of the first 
> transfer the sender uses the AMQP default value of zero for this field.{quote}
> As well as the AMQP spec (section 2.7.5):
> {quote}This field MUST be specified for the first transfer of a 
> multi-transfer message and can only be omitted for continuation transfers. It 
> is an error if the message-format on a continuation transfer differs from the 
> message-format on the first transfer of a delivery.{quote}



--
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-2798) [protonj2] Update test dependencies to latest releases

2024-02-26 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2798:
---

 Summary: [protonj2] Update test dependencies to latest releases
 Key: PROTON-2798
 URL: https://issues.apache.org/jira/browse/PROTON-2798
 Project: Qpid Proton
  Issue Type: Task
  Components: protonj2
Affects Versions: protonj2-1.0.0-M19
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M20


Update test dependencies to latest release



--
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-2797) [protonj2] Update Netty to latest release

2024-02-26 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2797:
---

 Summary: [protonj2] Update Netty to latest release
 Key: PROTON-2797
 URL: https://issues.apache.org/jira/browse/PROTON-2797
 Project: Qpid Proton
  Issue Type: Task
  Components: protonj2
Affects Versions: protonj2-1.0.0-M19
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M20


Update netty and its dependencies to latest release



--
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-2796) [protonj2] Update sender create to match source and target address

2024-02-26 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2796.
-
Resolution: Fixed

> [protonj2] Update sender create to match source and target address
> --
>
> Key: PROTON-2796
> URL: https://issues.apache.org/jira/browse/PROTON-2796
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Trivial
> Fix For: protonj2-1.0.0-M20
>
>
> Sender and Receiver create should both do the same action when building the 
> link objects, currently sender doesn't use the address value on source and 
> target while receiver does, we should match them and have them both use the 
> address value.
> Add tests to ensure they are both doing what we expect in this case



--
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-2796) [protonj2] Update sender create to match source and target address

2024-02-26 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2796:
---

 Summary: [protonj2] Update sender create to match source and 
target address
 Key: PROTON-2796
 URL: https://issues.apache.org/jira/browse/PROTON-2796
 Project: Qpid Proton
  Issue Type: Improvement
  Components: protonj2
Affects Versions: protonj2-1.0.0-M19
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M20


Sender and Receiver create should both do the same action when building the 
link objects, currently sender doesn't use the address value on source and 
target while receiver does, we should match them and have them both use the 
address value.

Add tests to ensure they are both doing what we expect in this case



--
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-2795) Message format cannot be set to 0 on outbound messages

2024-02-23 Thread Timothy A. Bish (Jira)


[ 
https://issues.apache.org/jira/browse/PROTON-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820222#comment-17820222
 ] 

Timothy A. Bish commented on PROTON-2795:
-

I was mistaken on that one, and have corrected the code to send it as it should 
now. 

> Message format cannot be set to 0 on outbound messages
> --
>
> Key: PROTON-2795
> URL: https://issues.apache.org/jira/browse/PROTON-2795
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Arnaud Cogoluègnes
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M20
>
>
> Setting the message format to 0 or keeping the default value results in a 
> null value in the {{transfer}} frame.
> 0 seems to be considered [a special 
> value|https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2/src/main/java/org/apache/qpid/protonj2/engine/impl/ProtonSessionOutgoingWindow.java#L270-L274]
>  in the code.
> This contradicts [the 
> Javadoc|https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2-client/src/main/java/org/apache/qpid/protonj2/client/AdvancedMessage.java#L170-L200]:
> {quote}This field MUST be specified for the first transfer of a 
> multi-transfer message, if it is not set at the time of send of the first 
> transfer the sender uses the AMQP default value of zero for this field.{quote}
> As well as the AMQP spec (section 2.7.5):
> {quote}This field MUST be specified for the first transfer of a 
> multi-transfer message and can only be omitted for continuation transfers. It 
> is an error if the message-format on a continuation transfer differs from the 
> message-format on the first transfer of a delivery.{quote}



--
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-2795) Message format cannot be set to 0 on outbound messages

2024-02-23 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2795.
-
Fix Version/s: protonj2-1.0.0-M20
   Resolution: Fixed

> Message format cannot be set to 0 on outbound messages
> --
>
> Key: PROTON-2795
> URL: https://issues.apache.org/jira/browse/PROTON-2795
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Arnaud Cogoluègnes
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M20
>
>
> Setting the message format to 0 or keeping the default value results in a 
> null value in the {{transfer}} frame.
> 0 seems to be considered [a special 
> value|https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2/src/main/java/org/apache/qpid/protonj2/engine/impl/ProtonSessionOutgoingWindow.java#L270-L274]
>  in the code.
> This contradicts [the 
> Javadoc|https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2-client/src/main/java/org/apache/qpid/protonj2/client/AdvancedMessage.java#L170-L200]:
> {quote}This field MUST be specified for the first transfer of a 
> multi-transfer message, if it is not set at the time of send of the first 
> transfer the sender uses the AMQP default value of zero for this field.{quote}
> As well as the AMQP spec (section 2.7.5):
> {quote}This field MUST be specified for the first transfer of a 
> multi-transfer message and can only be omitted for continuation transfers. It 
> is an error if the message-format on a continuation transfer differs from the 
> message-format on the first transfer of a delivery.{quote}



--
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] [Reopened] (PROTON-2795) Message format cannot be set to 0 on outbound messages

2024-02-23 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish reopened PROTON-2795:
-

> Message format cannot be set to 0 on outbound messages
> --
>
> Key: PROTON-2795
> URL: https://issues.apache.org/jira/browse/PROTON-2795
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Arnaud Cogoluègnes
>Assignee: Timothy A. Bish
>Priority: Minor
>
> Setting the message format to 0 or keeping the default value results in a 
> null value in the {{transfer}} frame.
> 0 seems to be considered [a special 
> value|https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2/src/main/java/org/apache/qpid/protonj2/engine/impl/ProtonSessionOutgoingWindow.java#L270-L274]
>  in the code.
> This contradicts [the 
> Javadoc|https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2-client/src/main/java/org/apache/qpid/protonj2/client/AdvancedMessage.java#L170-L200]:
> {quote}This field MUST be specified for the first transfer of a 
> multi-transfer message, if it is not set at the time of send of the first 
> transfer the sender uses the AMQP default value of zero for this field.{quote}
> As well as the AMQP spec (section 2.7.5):
> {quote}This field MUST be specified for the first transfer of a 
> multi-transfer message and can only be omitted for continuation transfers. It 
> is an error if the message-format on a continuation transfer differs from the 
> message-format on the first transfer of a delivery.{quote}



--
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] [Closed] (PROTON-2795) Message format cannot be set to 0 on outbound messages

2024-02-23 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish closed PROTON-2795.
---
Resolution: Not A Problem

The default AMQP message format is Zero as per the specification and the value 
is omitted when set to the default by the underlying codec.  If the application 
sets a value other than zero it will be sent in the first Transfer performative 
as the spec requires

> Message format cannot be set to 0 on outbound messages
> --
>
> Key: PROTON-2795
> URL: https://issues.apache.org/jira/browse/PROTON-2795
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M19
>Reporter: Arnaud Cogoluègnes
>Assignee: Timothy A. Bish
>Priority: Minor
>
> Setting the message format to 0 or keeping the default value results in a 
> null value in the {{transfer}} frame.
> 0 seems to be considered [a special 
> value|https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2/src/main/java/org/apache/qpid/protonj2/engine/impl/ProtonSessionOutgoingWindow.java#L270-L274]
>  in the code.
> This contradicts [the 
> Javadoc|https://github.com/apache/qpid-protonj2/blob/d5144af7818b2695747782bacc410580d3ec7943/protonj2-client/src/main/java/org/apache/qpid/protonj2/client/AdvancedMessage.java#L170-L200]:
> {quote}This field MUST be specified for the first transfer of a 
> multi-transfer message, if it is not set at the time of send of the first 
> transfer the sender uses the AMQP default value of zero for this field.{quote}
> As well as the AMQP spec (section 2.7.5):
> {quote}This field MUST be specified for the first transfer of a 
> multi-transfer message and can only be omitted for continuation transfers. It 
> is an error if the message-format on a continuation transfer differs from the 
> message-format on the first transfer of a delivery.{quote}



--
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-2793) [proton-dotnet] Fix test code build warnings under .NET 8

2024-02-20 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2793.
-
Resolution: Fixed

> [proton-dotnet] Fix test code build warnings under .NET 8 
> --
>
> Key: PROTON-2793
> URL: https://issues.apache.org/jira/browse/PROTON-2793
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-dotnet
>Affects Versions: proton-dotnet-1.0.0-M9
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Trivial
> Fix For: proton-dotnet-1.0.0-M10
>
>




--
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-2793) [proton-dotnet] Fix test code build warnings under .NET 8

2024-02-20 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2793:
---

 Summary: [proton-dotnet] Fix test code build warnings under .NET 8 
 Key: PROTON-2793
 URL: https://issues.apache.org/jira/browse/PROTON-2793
 Project: Qpid Proton
  Issue Type: Task
  Components: proton-dotnet
Affects Versions: proton-dotnet-1.0.0-M9
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: proton-dotnet-1.0.0-M10






--
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-2778) [protonj2] Update test dependencies to latest releases

2024-01-08 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2778.
-
Resolution: Fixed

> [protonj2] Update test dependencies to latest releases
> --
>
> Key: PROTON-2778
> URL: https://issues.apache.org/jira/browse/PROTON-2778
> Project: Qpid Proton
>  Issue Type: Task
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M18
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M19
>
>
> Update project test dependencies to latest versions



--
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-2784) [protonj2] Improve test peer completion handling when connection drops

2023-12-15 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2784.
-
Resolution: Fixed

> [protonj2] Improve test peer completion handling when connection drops
> --
>
> Key: PROTON-2784
> URL: https://issues.apache.org/jira/browse/PROTON-2784
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M18
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M19
>
>
> When waiting on test script completion the handling for connection drop 
> should better detect that a failure condition exists such as remaining 
> expectation which can never be reached unless a reconnect is expected (this 
> requires a connection drop to be scripted).  This will allow the test driver 
> to quicker fail a test as opposed to waiting for a full wait timeout.



--
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-2784) [protonj2] Improve test peer completion handling when connection drops

2023-12-15 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2784:
---

 Summary: [protonj2] Improve test peer completion handling when 
connection drops
 Key: PROTON-2784
 URL: https://issues.apache.org/jira/browse/PROTON-2784
 Project: Qpid Proton
  Issue Type: Improvement
  Components: protonj2
Affects Versions: protonj2-1.0.0-M18
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M19


When waiting on test script completion the handling for connection drop should 
better detect that a failure condition exists such as remaining expectation 
which can never be reached unless a reconnect is expected (this requires a 
connection drop to be scripted).  This will allow the test driver to quicker 
fail a test as opposed to waiting for a full wait timeout.



--
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-2783) [protonj2] Test driver expect for connection drop can hang script

2023-12-14 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2783.
-
Resolution: Fixed

> [protonj2] Test driver expect for connection drop can hang script
> -
>
> Key: PROTON-2783
> URL: https://issues.apache.org/jira/browse/PROTON-2783
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M18
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M19
>
>
> When adding an expectation in the test peer for a connection drop event the 
> driver doesn't look to see if all preceding expectations are optional or no 
> and will block on a wait for expected interactions when the connection drops 
> instead of discarding optional interactions.



--
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-2783) [protonj2] Test driver expect for connection drop can hang script

2023-12-14 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2783:
---

 Summary: [protonj2] Test driver expect for connection drop can 
hang script
 Key: PROTON-2783
 URL: https://issues.apache.org/jira/browse/PROTON-2783
 Project: Qpid Proton
  Issue Type: Bug
  Components: protonj2
Affects Versions: protonj2-1.0.0-M18
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M19


When adding an expectation in the test peer for a connection drop event the 
driver doesn't look to see if all preceding expectations are optional or no and 
will block on a wait for expected interactions when the connection drops 
instead of discarding optional interactions.



--
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-2781) [protonj2] Clean up some code and API docs in the SASL layer

2023-12-08 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2781:
---

 Summary: [protonj2] Clean up some code and API docs in the SASL 
layer
 Key: PROTON-2781
 URL: https://issues.apache.org/jira/browse/PROTON-2781
 Project: Qpid Proton
  Issue Type: Improvement
  Components: protonj2
Affects Versions: protonj2-1.0.0-M18
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M19


Some minor additions and cleanups to the javadocs for some SASL layer APIs and 
some cleanup of error messages etc.



--
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-2781) [protonj2] Clean up some code and API docs in the SASL layer

2023-12-08 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2781.
-
Resolution: Fixed

> [protonj2] Clean up some code and API docs in the SASL layer
> 
>
> Key: PROTON-2781
> URL: https://issues.apache.org/jira/browse/PROTON-2781
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M18
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Trivial
> Fix For: protonj2-1.0.0-M19
>
>
> Some minor additions and cleanups to the javadocs for some SASL layer APIs 
> and some cleanup of error messages etc.



--
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-2780) [protonj2] Improve test stability under slow CI conditions

2023-12-06 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2780:
---

 Summary: [protonj2] Improve test stability under slow CI conditions
 Key: PROTON-2780
 URL: https://issues.apache.org/jira/browse/PROTON-2780
 Project: Qpid Proton
  Issue Type: Improvement
  Components: protonj2
Affects Versions: protonj2-1.0.0-M18
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M19


On some heavily loaded CI instances (especially windows VMs) some test 
condition timeouts are a bit short leading to failures.



--
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] [Updated] (PROTON-2779) [protonj2] Update Netty to latest release

2023-12-01 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish updated PROTON-2779:

Fix Version/s: protonj2-1.0.0-M19
   (was: protonj2-1.0.0-M18)

> [protonj2] Update Netty to latest release
> -
>
> Key: PROTON-2779
> URL: https://issues.apache.org/jira/browse/PROTON-2779
> Project: Qpid Proton
>  Issue Type: Task
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M18
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M19
>
>
> Update Netty and tcnatives to latest releases



--
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-2779) [protonj2] Update Netty to latest release

2023-12-01 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2779:
---

 Summary: [protonj2] Update Netty to latest release
 Key: PROTON-2779
 URL: https://issues.apache.org/jira/browse/PROTON-2779
 Project: Qpid Proton
  Issue Type: Task
  Components: protonj2
Affects Versions: protonj2-1.0.0-M18
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M18


Update Netty and tcnatives to latest releases



--
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] [Updated] (PROTON-2778) [protonj2] Update test dependencies to latest releases

2023-12-01 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish updated PROTON-2778:

  Component/s: protonj2
Fix Version/s: protonj2-1.0.0-M19
Affects Version/s: protonj2-1.0.0-M18

> [protonj2] Update test dependencies to latest releases
> --
>
> Key: PROTON-2778
> URL: https://issues.apache.org/jira/browse/PROTON-2778
> Project: Qpid Proton
>  Issue Type: Task
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M18
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M19
>
>
> Update project test dependencies to latest versions



--
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-2778) [protonj2] Update test dependencies to latest releases

2023-12-01 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2778:
---

 Summary: [protonj2] Update test dependencies to latest releases
 Key: PROTON-2778
 URL: https://issues.apache.org/jira/browse/PROTON-2778
 Project: Qpid Proton
  Issue Type: Task
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish


Update project test dependencies to latest versions



--
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-2769) [protonj2] Update test dependencies to latest releases

2023-11-01 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2769.
-
Resolution: Fixed

> [protonj2] Update test dependencies to latest releases
> --
>
> Key: PROTON-2769
> URL: https://issues.apache.org/jira/browse/PROTON-2769
> Project: Qpid Proton
>  Issue Type: Task
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M17
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M18
>
>
> Update test dependencies to latest



--
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-2768) [protonj2] Update Netty to latest release

2023-11-01 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2768.
-
Resolution: Fixed

> [protonj2] Update Netty to latest release
> -
>
> Key: PROTON-2768
> URL: https://issues.apache.org/jira/browse/PROTON-2768
> Project: Qpid Proton
>  Issue Type: Task
>Affects Versions: protonj2-1.0.0-M17
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M18
>
>
> Ensure netty and the tcnative libraries are up to date.



--
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-2767) [protonj2] Add additional client documentation

2023-11-01 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2767.
-
Resolution: Fixed

> [protonj2] Add additional client documentation
> --
>
> Key: PROTON-2767
> URL: https://issues.apache.org/jira/browse/PROTON-2767
> Project: Qpid Proton
>  Issue Type: Task
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M17
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M18
>
>
> Build on existing client documentation to ease the initial entry into using 
> the protonj2 client project



--
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-2769) [protonj2] Update test dependencies to latest releases

2023-09-26 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2769:
---

 Summary: [protonj2] Update test dependencies to latest releases
 Key: PROTON-2769
 URL: https://issues.apache.org/jira/browse/PROTON-2769
 Project: Qpid Proton
  Issue Type: Task
  Components: protonj2
Affects Versions: protonj2-1.0.0-M17
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M18


Update test dependencies to latest



--
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-2768) [protonj2] Update Netty to latest release

2023-09-26 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2768:
---

 Summary: [protonj2] Update Netty to latest release
 Key: PROTON-2768
 URL: https://issues.apache.org/jira/browse/PROTON-2768
 Project: Qpid Proton
  Issue Type: Task
Affects Versions: protonj2-1.0.0-M17
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M18


Ensure netty and the tcnative libraries are up to date.



--
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-2767) [protonj2] Add additional client documentation

2023-09-18 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2767:
---

 Summary: [protonj2] Add additional client documentation
 Key: PROTON-2767
 URL: https://issues.apache.org/jira/browse/PROTON-2767
 Project: Qpid Proton
  Issue Type: Task
  Components: protonj2
Affects Versions: protonj2-1.0.0-M17
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M18


Build on existing client documentation to ease the initial entry into using the 
protonj2 client project



--
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-2766) [proton-dotnet] Add additional documentation to project

2023-09-18 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2766:
---

 Summary: [proton-dotnet] Add additional documentation to project
 Key: PROTON-2766
 URL: https://issues.apache.org/jira/browse/PROTON-2766
 Project: Qpid Proton
  Issue Type: Task
  Components: proton-dotnet
Affects Versions: proton-dotnet-1.0.0-M9
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: proton-dotnet-1.0.0-M10


Add basic documentation for usage and some options documentation for various 
client resources.



--
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-2758) [protonj2] Update JUnit to latest release

2023-07-25 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2758.
-
Resolution: Fixed

> [protonj2] Update JUnit to latest release
> -
>
> Key: PROTON-2758
> URL: https://issues.apache.org/jira/browse/PROTON-2758
> Project: Qpid Proton
>  Issue Type: Task
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M16
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Trivial
> Fix For: protonj2-1.0.0-M17
>
>
> Update the JUnit dependency to v5.10.0



--
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-2750) [protonj2] Add some additional functionality to the AMQP test peer

2023-07-25 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2750.
-
Resolution: Fixed

> [protonj2] Add some additional functionality to the AMQP test peer
> --
>
> Key: PROTON-2750
> URL: https://issues.apache.org/jira/browse/PROTON-2750
> Project: Qpid Proton
>  Issue Type: Task
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M16
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M17
>
>
> Add some additional testing APIs to the test peer.



--
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-2757) [protonj2] Update Netty to latest release

2023-07-25 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2757.
-
Resolution: Fixed

> [protonj2] Update Netty to latest release
> -
>
> Key: PROTON-2757
> URL: https://issues.apache.org/jira/browse/PROTON-2757
> Project: Qpid Proton
>  Issue Type: Task
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M16
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M17
>
>
> Update to latest netty release



--
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-2749) [protonj2] Test peer script of sasl plain connect lacks AMQP header expectation

2023-07-25 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2749.
-
Resolution: Fixed

> [protonj2] Test peer script of sasl plain connect lacks AMQP header 
> expectation
> ---
>
> Key: PROTON-2749
> URL: https://issues.apache.org/jira/browse/PROTON-2749
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M16
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M17
>
>
> The scripted sasl plain queue method in the test peer fails to add an 
> expectation for incoming AMQP header after the SASL exchange completes unlike 
> the scripted sasl anonymous version.



--
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-2758) [protonj2] Update JUnit to latest release

2023-07-24 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2758:
---

 Summary: [protonj2] Update JUnit to latest release
 Key: PROTON-2758
 URL: https://issues.apache.org/jira/browse/PROTON-2758
 Project: Qpid Proton
  Issue Type: Task
  Components: protonj2
Affects Versions: protonj2-1.0.0-M16
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M17


Update the JUnit dependency to v5.10.0



--
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-2757) [protonj2] Update Netty to latest release

2023-07-21 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2757:
---

 Summary: [protonj2] Update Netty to latest release
 Key: PROTON-2757
 URL: https://issues.apache.org/jira/browse/PROTON-2757
 Project: Qpid Proton
  Issue Type: Task
  Components: protonj2
Affects Versions: protonj2-1.0.0-M16
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M17


Update to latest netty release



--
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-2750) [protonj2] Add some additional functionality to the AMQP test peer

2023-07-10 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2750:
---

 Summary: [protonj2] Add some additional functionality to the AMQP 
test peer
 Key: PROTON-2750
 URL: https://issues.apache.org/jira/browse/PROTON-2750
 Project: Qpid Proton
  Issue Type: Task
  Components: protonj2
Affects Versions: protonj2-1.0.0-M16
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M17


Add some additional testing APIs to the test peer.



--
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-2749) [protonj2] Test peer script of sasl plain connect lacks AMQP header expectation

2023-07-10 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2749:
---

 Summary: [protonj2] Test peer script of sasl plain connect lacks 
AMQP header expectation
 Key: PROTON-2749
 URL: https://issues.apache.org/jira/browse/PROTON-2749
 Project: Qpid Proton
  Issue Type: Bug
  Components: protonj2
Affects Versions: protonj2-1.0.0-M16
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M17


The scripted sasl plain queue method in the test peer fails to add an 
expectation for incoming AMQP header after the SASL exchange completes unlike 
the scripted sasl anonymous version.



--
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-2745) [protonj2] Update Apache parent pom to v30

2023-06-26 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2745.
-
Resolution: Fixed

> [protonj2] Update Apache parent pom to v30
> --
>
> Key: PROTON-2745
> URL: https://issues.apache.org/jira/browse/PROTON-2745
> Project: Qpid Proton
>  Issue Type: Task
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M15
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M16
>
>
> Update to latest parent pom



--
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-2745) [protonj2] Update Apache parent pom to v30

2023-06-26 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2745:
---

 Summary: [protonj2] Update Apache parent pom to v30
 Key: PROTON-2745
 URL: https://issues.apache.org/jira/browse/PROTON-2745
 Project: Qpid Proton
  Issue Type: Task
  Components: protonj2
Affects Versions: protonj2-1.0.0-M15
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M16


Update to latest parent pom



--
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-2739) [protonj2] Add some additional functionality to the AMQP test peer

2023-06-26 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2739.
-
Resolution: Fixed

> [protonj2] Add some additional functionality to the AMQP test peer
> --
>
> Key: PROTON-2739
> URL: https://issues.apache.org/jira/browse/PROTON-2739
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M15
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M16
>
>
> Some additional features and APIs need to be added to the AMQP test peer in 
> order to support some more complex cases when testing connections that auto 
> reconnect as well as some other API additions to ease in test writing.



--
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-2744) [protonj2] Fix issue in test peer client that causes netty event loop to leak

2023-06-26 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2744.
-
Resolution: Fixed

> [protonj2] Fix issue in test peer client that causes netty event loop to leak
> -
>
> Key: PROTON-2744
> URL: https://issues.apache.org/jira/browse/PROTON-2744
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M15
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M16
>
>
> The test peer netty client IO layer is not properly shutting down the Event 
> Loop on close of the peer which leaks threads after test runs



--
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] [Reopened] (PROTON-2744) [protonj2] Fix issue in test peer client that causes netty event loop to leak

2023-06-21 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish reopened PROTON-2744:
-

> [protonj2] Fix issue in test peer client that causes netty event loop to leak
> -
>
> Key: PROTON-2744
> URL: https://issues.apache.org/jira/browse/PROTON-2744
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M15
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M16
>
>
> The test peer netty client IO layer is not properly shutting down the Event 
> Loop on close of the peer which leaks threads after test runs



--
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] [Reopened] (PROTON-2739) [protonj2] Add some additional functionality to the AMQP test peer

2023-06-21 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish reopened PROTON-2739:
-

> [protonj2] Add some additional functionality to the AMQP test peer
> --
>
> Key: PROTON-2739
> URL: https://issues.apache.org/jira/browse/PROTON-2739
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M15
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M16
>
>
> Some additional features and APIs need to be added to the AMQP test peer in 
> order to support some more complex cases when testing connections that auto 
> reconnect as well as some other API additions to ease in test writing.



--
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-2744) [protonj2] Fix issue in test peer client that causes netty event loop to leak

2023-06-20 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2744.
-
Resolution: Fixed

> [protonj2] Fix issue in test peer client that causes netty event loop to leak
> -
>
> Key: PROTON-2744
> URL: https://issues.apache.org/jira/browse/PROTON-2744
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M15
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M16
>
>
> The test peer netty client IO layer is not properly shutting down the Event 
> Loop on close of the peer which leaks threads after test runs



--
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-2744) [protonj2] Fix issue in test peer client that causes netty event loop to leak

2023-06-20 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2744:
---

 Summary: [protonj2] Fix issue in test peer client that causes 
netty event loop to leak
 Key: PROTON-2744
 URL: https://issues.apache.org/jira/browse/PROTON-2744
 Project: Qpid Proton
  Issue Type: Bug
  Components: protonj2
Affects Versions: protonj2-1.0.0-M15
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M16


The test peer netty client IO layer is not properly shutting down the Event 
Loop on close of the peer which leaks threads after test runs



--
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-2739) [protonj2] Add some additional functionality to the AMQP test peer

2023-06-20 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2739.
-
Resolution: Fixed

> [protonj2] Add some additional functionality to the AMQP test peer
> --
>
> Key: PROTON-2739
> URL: https://issues.apache.org/jira/browse/PROTON-2739
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M15
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M16
>
>
> Some additional features and APIs need to be added to the AMQP test peer in 
> order to support some more complex cases when testing connections that auto 
> reconnect as well as some other API additions to ease in test writing.



--
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-2740) [protonj2] Update Netty to latest release

2023-06-20 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2740.
-
Resolution: Fixed

> [protonj2] Update Netty to latest release
> -
>
> Key: PROTON-2740
> URL: https://issues.apache.org/jira/browse/PROTON-2740
> Project: Qpid Proton
>  Issue Type: Task
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M15
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: protonj2-1.0.0-M16
>
>
> Update to Netty latest release



--
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-2735) [protonj2] Update Netty tcnatives to latest release

2023-06-20 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2735.
-
Resolution: Fixed

> [protonj2] Update Netty tcnatives to latest release
> ---
>
> Key: PROTON-2735
> URL: https://issues.apache.org/jira/browse/PROTON-2735
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M15
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M16
>
>
> Update the Netty dependencies to the latest versions



--
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-2741) [protonj2] Update project test dependencies to latest

2023-06-20 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2741.
-
Resolution: Fixed

> [protonj2] Update project test dependencies to latest
> -
>
> Key: PROTON-2741
> URL: https://issues.apache.org/jira/browse/PROTON-2741
> Project: Qpid Proton
>  Issue Type: Task
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M15
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M16
>
>
> Update test dependencies to latest versions



--
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-2734) [protonj2] Update project test dependencies to latest

2023-06-20 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2734.
-
Resolution: Fixed

> [protonj2] Update project test dependencies to latest
> -
>
> Key: PROTON-2734
> URL: https://issues.apache.org/jira/browse/PROTON-2734
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M15
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M16
>
>
> Update the project test dependencies to the latest vsions



--
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] [Updated] (PROTON-2735) [protonj2] Update Netty tcnatives to latest release

2023-06-20 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish updated PROTON-2735:

Summary: [protonj2] Update Netty tcnatives to latest release  (was: 
[protonj2] Update Netty to latest release)

> [protonj2] Update Netty tcnatives to latest release
> ---
>
> Key: PROTON-2735
> URL: https://issues.apache.org/jira/browse/PROTON-2735
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M15
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M16
>
>
> Update the Netty dependencies to the latest versions



--
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-2741) [protonj2] Update project test dependencies to latest

2023-05-30 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2741:
---

 Summary: [protonj2] Update project test dependencies to latest
 Key: PROTON-2741
 URL: https://issues.apache.org/jira/browse/PROTON-2741
 Project: Qpid Proton
  Issue Type: Task
  Components: protonj2
Affects Versions: protonj2-1.0.0-M15
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M16


Update test dependencies to latest versions



--
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-2740) [protonj2] Update Netty to latest release

2023-05-30 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2740:
---

 Summary: [protonj2] Update Netty to latest release
 Key: PROTON-2740
 URL: https://issues.apache.org/jira/browse/PROTON-2740
 Project: Qpid Proton
  Issue Type: Task
  Components: protonj2
Affects Versions: protonj2-1.0.0-M15
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M16


Update to Netty latest release



--
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-2739) [protonj2] Add some additional functionality to the AMQP test peer

2023-05-26 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2739:
---

 Summary: [protonj2] Add some additional functionality to the AMQP 
test peer
 Key: PROTON-2739
 URL: https://issues.apache.org/jira/browse/PROTON-2739
 Project: Qpid Proton
  Issue Type: Improvement
  Components: protonj2
Affects Versions: protonj2-1.0.0-M15
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M16


Some additional features and APIs need to be added to the AMQP test peer in 
order to support some more complex cases when testing connections that auto 
reconnect as well as some other API additions to ease in test writing.



--
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-2737) [proton-dotnet] v1.0.0-M9 release tasks

2023-05-22 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2737.
-
Resolution: Fixed

> [proton-dotnet] v1.0.0-M9 release tasks
> ---
>
> Key: PROTON-2737
> URL: https://issues.apache.org/jira/browse/PROTON-2737
> Project: Qpid Proton
>  Issue Type: Task
>  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
>
>
> Source tree updates for the 1.0.0-M9 release



--
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-2737) [proton-dotnet] v1.0.0-M9 release tasks

2023-05-22 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2737:
---

 Summary: [proton-dotnet] v1.0.0-M9 release tasks
 Key: PROTON-2737
 URL: https://issues.apache.org/jira/browse/PROTON-2737
 Project: Qpid Proton
  Issue Type: Task
  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


Source tree updates for the 1.0.0-M9 release



--
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-2728) [proton-dotnet] Fix some spelling and clean up some API docs

2023-05-22 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2728.
-
Resolution: Fixed

> [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-2735) [protonj2] Update Netty to latest release

2023-05-11 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2735:
---

 Summary: [protonj2] Update Netty to latest release
 Key: PROTON-2735
 URL: https://issues.apache.org/jira/browse/PROTON-2735
 Project: Qpid Proton
  Issue Type: Improvement
  Components: protonj2
Affects Versions: protonj2-1.0.0-M15
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M16


Update the Netty dependencies to the latest versions



--
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-2734) [protonj2] Update project test dependencies to latest

2023-05-11 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2734:
---

 Summary: [protonj2] Update project test dependencies to latest
 Key: PROTON-2734
 URL: https://issues.apache.org/jira/browse/PROTON-2734
 Project: Qpid Proton
  Issue Type: Improvement
  Components: protonj2
Affects Versions: protonj2-1.0.0-M15
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: protonj2-1.0.0-M16


Update the project test dependencies to the latest vsions



--
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-2732) [proton-dotnet] Engine configuration TraceFrames option not honored

2023-05-10 Thread Timothy A. Bish (Jira)


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

Timothy A. Bish resolved PROTON-2732.
-
Resolution: Fixed

> [proton-dotnet] Engine configuration TraceFrames option not honored 
> 
>
> Key: PROTON-2732
> URL: https://issues.apache.org/jira/browse/PROTON-2732
> 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 configuration option in the Engine config for setting the TraceFrames 
> value outside the environment variable is not fully wired and won't be 
> honored currently (The env var works as expeceted).  The configuration 
> options needs to check for the presence of the logging handler and then apply 
> or get the option as 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-2732) [proton-dotnet] Engine configuration TraceFrames option not honored

2023-05-10 Thread Timothy A. Bish (Jira)
Timothy A. Bish created PROTON-2732:
---

 Summary: [proton-dotnet] Engine configuration TraceFrames option 
not honored 
 Key: PROTON-2732
 URL: https://issues.apache.org/jira/browse/PROTON-2732
 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 configuration option in the Engine config for setting the TraceFrames value 
outside the environment variable is not fully wired and won't be honored 
currently (The env var works as expeceted).  The configuration options needs to 
check for the presence of the logging handler and then apply or get the option 
as 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-2731) [proton-dotnet] Perform Receive call timeout validation before waiting

2023-05-09 Thread Timothy A. Bish (Jira)


 [ 
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] [Created] (PROTON-2731) [proton-dotnet] Perform Receive call timeout validation before waiting

2023-05-09 Thread Timothy A. Bish (Jira)
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



  1   2   3   4   5   >