Re: JMS Session termination during async sends
On 4/9/24 15:03, alan.masciang...@lmco.com wrote: Greetings, We've encountered an issue when closing JMSContext while doing async sends we tracked down to the exception being thrown here https://github.com/apache/qpid-jms/blob/2.5.0/qpid-jms-client/src/main/java/org/apache/qpid/jms/JmsSession.java#L373C51-L373C118. This appears to be at odds with the how javax.jms.Session and javax.jms.JmsContext are expected to behave. From the close() Javadoc This method must not return until any incomplete asynchronous send operations for this JMSContext have been completed and any CompletionListener callbacks have returned. Incomplete sends should be allowed to complete normally unless an error occurs. It appears to me incomplete sends are not being allowed to be completed normally but rather an exception is being thrown? You are correct this should be handled by session and connection close as is done in the MessageProducer, I've created a JIRA for this and will look into adding handling for this: https://issues.apache.org/jira/browse/QPIDJMS-600 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid proton-dotnet 1.0.0-M10 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache proton-dotnet 1.0.0-M10. This is the latest release of our AMQP .NET client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid proton-dotnet protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Release notes can be found at: http://qpid.apache.org/releases/qpid-proton-dotnet-1.0.0-M10/release-notes.html Thanks to all involved, -- -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid proton-dotnet 1.0.0-M10
There were 3 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release shortly. The website will be updated after the release has had time to sync to the mirrors. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M10 (RC1)
On 4/8/24 19:04, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M10 Qpid proton-dotnet release, please give it a test out and vote accordingly. Tests can be run using the build script in the source archive: "./build.sh podman-test" or "./build.sh docker-test" The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M10-rc1/ The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353498 Regards +1 * Verified signatures and checksums * Verified license and notice files in each archive * Checked source license headers with Apache RAT tool * Built from source and ran the test suite using the './build.sh docket-test' command * Ran all the examples against an ActiveMQ Artemis broker installation -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid proton-dotnet 1.0.0-M10 (RC1)
Hi folks, I have put together a release candidate for a 1.0.0-M10 Qpid proton-dotnet release, please give it a test out and vote accordingly. Tests can be run using the build script in the source archive: "./build.sh podman-test" or "./build.sh docker-test" The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M10-rc1/ The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353498 Regards -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid protonj2 1.0.0-M20 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache protonj2 1.0.0-M20. This is the latest release of our AMQP Java client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M20/release-notes.html Thanks to all involved, - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid protonj2 1.0.0-M20
There were 3 binding +1 votes, and 1 other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M20
On 3/25/24 14:13, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M20 Qpid protonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M20-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1276 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12354130 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1276 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M20 org.apache.qpid protonj2-client 1.0.0-M20 +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked source license headers with 'mvn apache-rat:check' * Built from source and ran the tests * Ran included examples using staged artifacts against an ActiveMQ Artemis broker instance. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid protonj2 1.0.0-M20
Hi folks, I have put together a release candidate for a 1.0.0-M20 Qpid protonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M20-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1276 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12354130 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1276 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M20 org.apache.qpid protonj2-client 1.0.0-M20 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: ProtonJ2 client handling of null message bodies
This should now be fixed as part of:
https://issues.apache.org/jira/browse/PROTON-2809
On 3/15/24 15:42, Ciaran wrote:
On Fri, Mar 15, 2024 at 6:14 PM Timothy Bish wrote:
On 3/15/24 11:50, Ciaran wrote:
Hi,
I'm attempting to build a resilient client using the protonj2 client and
as
part of my testing I was checking that it would handle messages with null
bodies (specifically my client is only willing to work with strings or
byte
arrays so it rejects any other AMQP message body type). However, when I
put
a null body on the message (i.e. body length of 0), when I de-reference
the
delivery's message's body property (e.g. delivery.message().body) I
receive
an error from the proton engine:
Can you capture a frame trace, I need enough information to try and
create an exact reproducer which can be aided with traces of the
incoming frames to reverse engineer a test. I wouldn't expect and
exception here and its likely something that was missed in the current
test suite.
Code snippets of the sender and receiver bits can help as well.
Hi,
Please find below everything I think you've asked for, the real code is
somewhat distributed
across several different classes, but this should be pretty equivalent:
RECEIVER CODE
-
ConnectionOptions options = constructBasicConnectionOptions();
options.reconnectOptions()
.reconnectEnabled(true)
.useReconnectBackOff(true)
.reconnectDelay(5000)
.maxReconnectDelay(10240001)
.maxReconnectAttempts(12)
.warnAfterReconnectAttempts(1);
Client client= Client.create();
Connection connection = client.connect("host", 1234, options);
ReceiverOptions ro = new ReceiverOptions();
ro.autoAccept(false);
Receiver receiver = connection.openReceiver( "queue", ro )) {
Delivery delivery = receiver.tryReceive();
if( delivery != null ) {
Message message= delivery.message();
// Exception occurs here.
Object body= message.body();
}
SENDER CODE
---
final Client client = Client.create();
final ConnectionOptions options = new ConnectionOptions();
options.sslOptions().sslEnabled(true);
options.user("MY_USER");
options.password("MY_PASSWORD");
Connection connection = client.connect(serverHost, serverPort, options);
Sender sender = connection.openSender(address);
sender.send(Message.create((byte[])null));
FRAME TRACE
-> SASL:[269961536:0] AMQP,3,1,0,0
<- SASL:[269961536:0] AMQP,3,1,0,0
<- SASL:[269961536:0] SaslMechanisms{saslServerMechanisms=[MSSBCBS, PLAIN,
ANONYMOUS, EXTERNAL]}
19:36:21,633 WARN SaslMechanismSelector:130 - Caught exception while
trying to create SASL mechanism MSSBCBS: No Matching SASL Mechanism with
name: MSSBCBS
-> SASL:[269961536:0] SaslInit{mechanism=PLAIN,
initialResponse="\x00MY_USER\x00MY_PASSWORD"...(truncated), hostname='
MY_HOST.servicebus.windows.net'}
<- SASL:[269961536:0] SaslOutcome{code=OK, additionalData="Welcome!"}
-> AMQP:[269961536:0] AMQP,0,1,0,0
<- AMQP:[269961536:0] AMQP,0,1,0,0
-> AMQP:[269961536:0] Open{
containerId='ID:081fcabd-ac34-41b5-9bff-fe35d0cfbff1:1:2', hostname='
MY_HOST.servicebus.windows.net', maxFrameSize=65536, channelMax=65535,
idleTimeOut=6, outgoingLocales=null, incomingLocales=null,
offeredCapabilities=null, desiredCapabilities=[ANONYMOUS-RELAY],
properties=null}
-> AMQP:[269961536:0] Begin{remoteChannel=null, nextOutgoingId=0,
incomingWindow=1600, outgoingWindow=2147483647, handleMax=null,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
-> AMQP:[269961536:0]
Attach{name='receiver-ID:081fcabd-ac34-41b5-9bff-fe35d0cfbff1:1:2:1:1',
handle=0, role=RECEIVER, sndSettleMode=UNSETTLED, rcvSettleMode=FIRST,
source=Source{address='testq', durable=NONE, expiryPolicy=LINK_DETACH,
timeout=0, dynamic=false, dynamicNodeProperties=null,
distributionMode=null, filter=null,
defaultOutcome=Modified{deliveryFailed=true, undeliverableHere=false,
messageAnnotations=null}, outcomes=[amqp:accepted:list, amqp:rejected:list,
amqp:released:list, amqp:modified:list], capabilities=null},
target=Target{address='testq', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=null, initialDeliveryCount=null,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
-> AMQP:[269961536:0] Flow{nextIncomingId=null, incomingWindow=1600,
nextOutgoingId=0, outgoingWindow=2147483647, handle=0, deliveryCount=null,
linkCredit=10, available=null, drain=false, echo=null, properties=null}
<- AMQP:[269961536:0] Open{
containerId='af1bcb999146429ea0a245db6affd5e4_G60', hostname='null',
maxFrameSize=65536, channelMax=4999, idleTimeOut=12,
outgoingLocales=null, incomingLocales=null, offeredCapabilities=null,
desiredCapabilities=null, properties=null}
<- AMQP:[269961536:0] Begin{remoteChannel=0, nextOutgoingId=1,
incomingWindow=5000, outgoingWindow=1600, han
Re: ProtonJ2 client handling of null message bodies
On 3/15/24 15:42, Ciaran wrote:
On Fri, Mar 15, 2024 at 6:14 PM Timothy Bish wrote:
On 3/15/24 11:50, Ciaran wrote:
Hi,
I'm attempting to build a resilient client using the protonj2 client and
as
part of my testing I was checking that it would handle messages with null
bodies (specifically my client is only willing to work with strings or
byte
arrays so it rejects any other AMQP message body type). However, when I
put
a null body on the message (i.e. body length of 0), when I de-reference
the
delivery's message's body property (e.g. delivery.message().body) I
receive
an error from the proton engine:
Can you capture a frame trace, I need enough information to try and
create an exact reproducer which can be aided with traces of the
incoming frames to reverse engineer a test. I wouldn't expect and
exception here and its likely something that was missed in the current
test suite.
Code snippets of the sender and receiver bits can help as well.
Hi,
Please find below everything I think you've asked for, the real code is
somewhat distributed
across several different classes, but this should be pretty equivalent:
RECEIVER CODE
-
ConnectionOptions options = constructBasicConnectionOptions();
options.reconnectOptions()
.reconnectEnabled(true)
.useReconnectBackOff(true)
.reconnectDelay(5000)
.maxReconnectDelay(10240001)
.maxReconnectAttempts(12)
.warnAfterReconnectAttempts(1);
Client client= Client.create();
Connection connection = client.connect("host", 1234, options);
ReceiverOptions ro = new ReceiverOptions();
ro.autoAccept(false);
Receiver receiver = connection.openReceiver( "queue", ro )) {
Delivery delivery = receiver.tryReceive();
if( delivery != null ) {
Message message= delivery.message();
// Exception occurs here.
Object body= message.body();
}
SENDER CODE
---
final Client client = Client.create();
final ConnectionOptions options = new ConnectionOptions();
options.sslOptions().sslEnabled(true);
options.user("MY_USER");
options.password("MY_PASSWORD");
Connection connection = client.connect(serverHost, serverPort, options);
Sender sender = connection.openSender(address);
sender.send(Message.create((byte[])null));
FRAME TRACE
-> SASL:[269961536:0] AMQP,3,1,0,0
<- SASL:[269961536:0] AMQP,3,1,0,0
<- SASL:[269961536:0] SaslMechanisms{saslServerMechanisms=[MSSBCBS, PLAIN,
ANONYMOUS, EXTERNAL]}
19:36:21,633 WARN SaslMechanismSelector:130 - Caught exception while
trying to create SASL mechanism MSSBCBS: No Matching SASL Mechanism with
name: MSSBCBS
-> SASL:[269961536:0] SaslInit{mechanism=PLAIN,
initialResponse="\x00MY_USER\x00MY_PASSWORD"...(truncated), hostname='
MY_HOST.servicebus.windows.net'}
<- SASL:[269961536:0] SaslOutcome{code=OK, additionalData="Welcome!"}
-> AMQP:[269961536:0] AMQP,0,1,0,0
<- AMQP:[269961536:0] AMQP,0,1,0,0
-> AMQP:[269961536:0] Open{
containerId='ID:081fcabd-ac34-41b5-9bff-fe35d0cfbff1:1:2', hostname='
MY_HOST.servicebus.windows.net', maxFrameSize=65536, channelMax=65535,
idleTimeOut=6, outgoingLocales=null, incomingLocales=null,
offeredCapabilities=null, desiredCapabilities=[ANONYMOUS-RELAY],
properties=null}
-> AMQP:[269961536:0] Begin{remoteChannel=null, nextOutgoingId=0,
incomingWindow=1600, outgoingWindow=2147483647, handleMax=null,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
-> AMQP:[269961536:0]
Attach{name='receiver-ID:081fcabd-ac34-41b5-9bff-fe35d0cfbff1:1:2:1:1',
handle=0, role=RECEIVER, sndSettleMode=UNSETTLED, rcvSettleMode=FIRST,
source=Source{address='testq', durable=NONE, expiryPolicy=LINK_DETACH,
timeout=0, dynamic=false, dynamicNodeProperties=null,
distributionMode=null, filter=null,
defaultOutcome=Modified{deliveryFailed=true, undeliverableHere=false,
messageAnnotations=null}, outcomes=[amqp:accepted:list, amqp:rejected:list,
amqp:released:list, amqp:modified:list], capabilities=null},
target=Target{address='testq', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=null, initialDeliveryCount=null,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
-> AMQP:[269961536:0] Flow{nextIncomingId=null, incomingWindow=1600,
nextOutgoingId=0, outgoingWindow=2147483647, handle=0, deliveryCount=null,
linkCredit=10, available=null, drain=false, echo=null, properties=null}
<- AMQP:[269961536:0] Open{
containerId='af1bcb999146429ea0a245db6affd5e4_G60', hostname='null',
maxFrameSize=65536, channelMax=4999, idleTimeOut=12,
outgoingLocales=null, incomingLocales=null, offeredCapabilities=null,
desiredCapabilities=null, properties=null}
<- AMQP:[269961536:0] Begin{remoteChannel=0, nextOutgoingId=1,
incomingWindow=5000, outgoingWindow=1600, handleMax=255,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
<
Re: Unexpected idle timeout behaviours
On 3/15/24 15:44, Ciaran wrote: This should be fixed no in: https://issues.apache.org/jira/browse/PROTON-2807 This essentially occurred because the Proton buffers were rewritten to allow zero copy semantics after the ingest code was written and the read offset is no longer reflective of the read outcome as the buffer may have handed off its underlying payload and have a size of zero which means the read offset will still be zero. This code was written in early days and had some safety checks in it that are no longer needed given other mechanics in place in the engine so has been updated to treat an non-empty buffer as cause to update the input sequence value. It's necessary to reproduce and explain the issues before making these changes so I needed to find a test case for this which I now have. I'm glad you got to the bottom of it, thank you for bearing with me. I can run a parallel compile for my purposes, but I was wondering if there is a planned release date for M20 ? Thank you. No planned date as someone keeps reporting issues. Was planning to release something in a few weeks for protonj2 and proton-dotnet -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: ProtonJ2 client handling of null message bodies
On 3/15/24 11:50, Ciaran wrote: Hi, I'm attempting to build a resilient client using the protonj2 client and as part of my testing I was checking that it would handle messages with null bodies (specifically my client is only willing to work with strings or byte arrays so it rejects any other AMQP message body type). However, when I put a null body on the message (i.e. body length of 0), when I de-reference the delivery's message's body property (e.g. delivery.message().body) I receive an error from the proton engine: Can you capture a frame trace, I need enough information to try and create an exact reproducer which can be aided with traces of the incoming frames to reverse engineer a test. I wouldn't expect and exception here and its likely something that was missed in the current test suite. Code snippets of the sender and receiver bits can help as well. 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) ... 7 more My expectation from the comments on the 'body()' method is that I should expect it to return null in this scenario? Should I be trapping this exception and rejecting the messages to avoid poisoning my queue? (I was planning on rejecting them anyway, but it seems weird to have to catch the exception first.) For reference, I'm putting messages onto the queue with the following protonj2 calls: sender.send(Message.create((byte[])null)); sender.send(Message.create((*String*)null)); Thank you (and sorry for the bombardment of things) -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: Unexpected idle timeout behaviours
On 3/14/24 19:28, Ciaran wrote:
I've provided the full set of frames below, but if I'm interpreting
correctly the inputSequence property is not being incremented on receipt
of
data which means that the deadline for hearing from the peer again is not
being suitably increased. (I can see the sequence increments and the
localdeadline is recalculated for the empty frames the peer sends, but
not
for when there's actual data.)
I've gone back through the client and engine code and did some testing
and cannot reproduce any issue where the sequence tracking is not
updated when incoming frames are read regardless of which frame they are.
I fixed a minor issue where the Client is not configuring the idle
timeout to half the set value as it says it will.
Hi Tim,
Thank you for taking a look, but I'm still seeing the issue :( I've
cherry-picked the idle timeout commit
on top of M19 and it /may/ be a little better, but that still feels like
it's covering up an issue.
Forgive me, but I'm not deeply familiar with the protonj2 codebase, but it
seems logical to
me that the inputSequence is incremented whenever some data is received
from the peer.
This should be fixed no in:
https://issues.apache.org/jira/browse/PROTON-2807
This essentially occurred because the Proton buffers were rewritten to
allow zero copy semantics after the ingest code was written and the read
offset is no longer reflective of the read outcome as the buffer may
have handed off its underlying payload and have a size of zero which
means the read offset will still be zero. This code was written in
early days and had some safety checks in it that are no longer needed
given other mechanics in place in the engine so has been updated to
treat an non-empty buffer as cause to update the input sequence value.
It's necessary to reproduce and explain the issues before making these
changes so I needed to find a test case for this which I now have.
I've attached another trace with additional logging to show the state of
ProtonEngine#ingest()
function. As I mentioned earlier, for Transfer frames the readOffset of the
input buffer
after fireRead has completed is 0, which the logic treats as a 'no
sequence' operation.
The interesting part, you may see below is that for each transfer there are
multiple (two)
calls to ingest, both returning 0 as the post fireRead value of the
readOffset. I presume this
is due to buffering and needing to fetch more data for this particular
frame type, so I can get my
head around the first of these reads being ignored as a sequence increment,
but it still feels to me that
the second (or presumably the very last one in the case of larger payloads)
should return a non-zero
value to trigger the sequence increment?
I'm not quite sure what the value of enforcing this logical sequence is as
it only appears to
be used as a 'liveness' indicator for the remote connection, does it matter
if it was a valid frame
returned?
Trace with additional logging of the variable state below:
<- AMQP:[1619358550:0] Open{
containerId='91791f32464449109b4136667ccaa3f7_G52', hostname='null',
maxFrameSize=65536, channelMax=4999, idleTimeOut=12,
outgoingLocales=null, incomingLocales=null, offeredCapabilities=null,
desiredCapabilities=null, properties=null}
startIndex:0, input.getReadOffset():71
inputSequence++
<- AMQP:[1619358550:0] Begin{remoteChannel=0, nextOutgoingId=1,
incomingWindow=5000, outgoingWindow=1600, handleMax=255,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
startIndex:0, input.getReadOffset():34
inputSequence++
<- AMQP:[1619358550:0]
Attach{name='receiver-ID:ecec0184-d4d3-4fe8-b8ec-0b132b249368:1:2:1:1',
handle=0, role=SENDER, sndSettleMode=UNSETTLED, rcvSettleMode=FIRST,
source=Source{address='testq', durable=NONE, expiryPolicy=LINK_DETACH,
timeout=0, dynamic=false, dynamicNodeProperties=null,
distributionMode=null, filter=null,
defaultOutcome=Modified{deliveryFailed=true, undeliverableHere=false,
messageAnnotations=null}, outcomes=[amqp:accepted:list, amqp:rejected:list,
amqp:released:list, amqp:modified:list], capabilities=null},
target=Target{address='testq', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=null, initialDeliveryCount=0,
maxMessageSize=18446744073709551615, offeredCapabilities=[SHARED-SUBS],
desiredCapabilities=null, properties=null}
startIndex:0, input.getReadOffset():258
inputSequence++
startIndex:0, input.getReadOffset():0
<- AMQP:[1619358550:0] Transfer{handle=0, deliveryId=0,
deliveryTag=DeliveryTag: {[56, 109, 70, 77, -127, -59, 8, 72, -120, 61, 85,
-116, 30, -125, -121, -112]}, messageFormat=0, settled=null, more=false,
rcvSettleMode=null, state=null, resume=null, aborted=null, batchable=true}
- "\x00Sp\xc0\x0a\x05@@pH\x19\x08\x00@C
\x00Sq\xc1$\x02\xa3\x10x-opt"...(truncated)
startIndex:0, input.getReadOffset():0
-> AMQP:[1619358550:0] Disposition{role=RECEIVER,
Re: Unexpected idle timeout behaviours
On 3/13/24 17:54, Ciaran wrote:
Hi,
I'm experiencing IdleTimeoutExceptions on my connections when I don't
believe I should. I've looked around and I can see that it is not uncommon
for people to misunderstand the AMQP timeout semantics, so this is quite
possible. However, viewing the frames and attaching a diagnostic logger to
the ProtonEngine.performReadCheck logic provides me with some information
that I don't understand.
I've provided the full set of frames below, but if I'm interpreting
correctly the inputSequence property is not being incremented on receipt of
data which means that the deadline for hearing from the peer again is not
being suitably increased. (I can see the sequence increments and the
localdeadline is recalculated for the empty frames the peer sends, but not
for when there's actual data.)
I've gone back through the client and engine code and did some testing
and cannot reproduce any issue where the sequence tracking is not
updated when incoming frames are read regardless of which frame they are.
I fixed a minor issue where the Client is not configuring the idle
timeout to half the set value as it says it will.
Pattern for logger on line 448 of ProtonEngine.java (
https://github.com/apache/qpid-protonj2/blob/226dedec2ee2b01da47b248d2a51330826ebf4cf/protonj2/src/main/java/org/apache/qpid/protonj2/engine/impl/ProtonEngine.java#L448)
is
localIdleTimeout, localIdleDeadline, currentTime, lastInputSequence,
inputSequence
-> SASL:[392574873:0] AMQP,3,1,0,0
6,0,813312359,0,0
<- SASL:[392574873:0] AMQP,3,1,0,0
<- SASL:[392574873:0] SaslMechanisms{saslServerMechanisms=[MSSBCBS, PLAIN,
ANONYMOUS, EXTERNAL]}
21:39:55,235 WARN SaslMechanismSelector:130 - Caught exception while
trying to create SASL mechanism MSSBCBS: No Matching SASL Mechanism with
name: MSSBCBS
-> SASL:[392574873:0] SaslInit{mechanism=PLAIN,
initialResponse="\x00MY_USERNAME\x00MY_PASSWORD"...(truncated), hostname='
MY_HOST.servicebus.windows.net'}
<- SASL:[392574873:0] SaslOutcome{code=OK, additionalData="Welcome!"}
-> AMQP:[392574873:0] AMQP,0,1,0,0
<- AMQP:[392574873:0] AMQP,0,1,0,0
-> AMQP:[392574873:0] Open{
containerId='ID:36f74f46-a99f-4b7a-93f4-bbe2c0d3c5b7:1:2', hostname='
MY_HOST.servicebus.windows.net', maxFrameSize=65536, channelMax=65535,
idleTimeOut=6, outgoingLocales=null, incomingLocales=null,
offeredCapabilities=null, desiredCapabilities=[ANONYMOUS-RELAY],
properties=null}
-> AMQP:[392574873:0] Begin{remoteChannel=null, nextOutgoingId=0,
incomingWindow=1600, outgoingWindow=2147483647, handleMax=null,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
-> AMQP:[392574873:0]
Attach{name='receiver-ID:36f74f46-a99f-4b7a-93f4-bbe2c0d3c5b7:1:2:1:1',
handle=0, role=RECEIVER, sndSettleMode=UNSETTLED, rcvSettleMode=FIRST,
source=Source{address='testq', durable=NONE, expiryPolicy=LINK_DETACH,
timeout=0, dynamic=false, dynamicNodeProperties=null,
distributionMode=null, filter=null,
defaultOutcome=Modified{deliveryFailed=true, undeliverableHere=false,
messageAnnotations=null}, outcomes=[amqp:accepted:list, amqp:rejected:list,
amqp:released:list, amqp:modified:list], capabilities=null},
target=Target{address='testq', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=null, initialDeliveryCount=null,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
-> AMQP:[392574873:0] Flow{nextIncomingId=null, incomingWindow=1600,
nextOutgoingId=0, outgoingWindow=2147483647, handle=0, deliveryCount=null,
linkCredit=10, available=null, drain=false, echo=null, properties=null}
<- AMQP:[392574873:0] Open{
containerId='543d61c8107e4369acdcf4202219b2d1_G24', hostname='null',
maxFrameSize=65536, channelMax=4999, idleTimeOut=12,
outgoingLocales=null, incomingLocales=null, offeredCapabilities=null,
desiredCapabilities=null, properties=null}
<- AMQP:[392574873:0] Begin{remoteChannel=0, nextOutgoingId=1,
incomingWindow=5000, outgoingWindow=1600, handleMax=255,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
<- AMQP:[392574873:0]
Attach{name='receiver-ID:36f74f46-a99f-4b7a-93f4-bbe2c0d3c5b7:1:2:1:1',
handle=0, role=SENDER, sndSettleMode=UNSETTLED, rcvSettleMode=FIRST,
source=Source{address='testq', durable=NONE, expiryPolicy=LINK_DETACH,
timeout=0, dynamic=false, dynamicNodeProperties=null,
distributionMode=null, filter=null,
defaultOutcome=Modified{deliveryFailed=true, undeliverableHere=false,
messageAnnotations=null}, outcomes=[amqp:accepted:list, amqp:rejected:list,
amqp:released:list, amqp:modified:list], capabilities=null},
target=Target{address='testq', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=null, initialDeliveryCount=0,
maxMessageSize=18446744073709551615, offeredCapabilities=[SHARED-SUBS],
desiredCapabilities=null, properties=null}
Re: ProtonJ2 Initial connection failure, reconnect logic
On 3/12/24 16:25, Ciaran wrote: On Tue, Mar 12, 2024 at 7:13 PM Timothy Bish wrote: On 3/12/24 04:08, Ciaran wrote: On Mon, Mar 11, 2024 at 9:33 PM Timothy Bish wrote: The client re-connection logic treats a SASL authentication error as a terminal state and will not continue reconnect attempts if it receives a SASL outcome that indicates anything other than a temporary failure state so it should be stopping the reconnect if it was actually failing to authenticate. This is true on the first attempt as well as on subsequent attempts to other hosts if you add more than one and it has failed to reach any of the preceding hosts while attempt to recover the connection. From the error logs attached it doesn't appear as though SASL authentication is your issue though, at least in so much as it isn't logging anything indicating SASL authentication as the error. Instead the connection appears to be failing because the remote has sent a response to the Receiver attach that does not include the initial delivery count value as required by the specification. You can capture more information about the AMQP frames being sent and received by enabling frame tracing, see the docs for how to do that. https://github.com/apache/qpid-protonj2/blob/main/protonj2-client-docs/Configuration.md#logging Thanks for getting back to me so quickly Tim, please find below the frames for a successful connection and an unsuccessful connection. My test has actually been to specify an invalid user if that's relevant. I can see in both cases that the SASL challenge completes successfully, which I appreciate is strange, but I would imagine Azure Service Bus is a common enough broker target for the library? So looking at the frame trace it is clear the connection is being established as the SASL outcome is returned as 'OK' and then a normal Open exchange occurs so from the client point of view a connection was successfully made so any initial reconnect attempts option won't apply here as the connection "succeeded". For the connection to fail with bad credentials the SASL outcome would need to indicate a failure. The connection breaks at the point the attach response arrives and is lacking the mandatory initial-delivery-count field as per the AMQP 1.0 specification. http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-attach It could be that the user you logged in as does not have read permission and the server is trying to tell the client that the link will be closed with an error condition in the Detach indicating that as the returned response does not carry a source or target value (both are null) whereas the sent Attach has an appropriate source and target value. If that is what it is doing it gets it wrong as it omits the 'initial-delivery-count' which is required for an Attach with the Role of Sender (as per referenced spec above) regardless of the outcome of the attach. Sorry, I think perhaps I've not explained myself well here, the user is correctly configured on Azure Service Bus. However, the fail case is where I provide an *invalid* (non-existant) user or an *invalid* password. I can see that the SaSL challenges succeeds, and agree from a client perspective that this success is problematic when the credentials provided are invalid! I guess I'm flagging that my configuration is not exotic, and Azure Service Bus is a fairly popular AMQP broker. As I pointed out the remote is telling the client that the connection succeeded so from the client point of view there just isn't anything that it can do here to know that your user doesn't exist. I'd say you need to take this up with MS as there just isn't anything that can be done here. If this is the desired behaviour of the client library when interacting with Azure, I'll stick with my work around, which is to create a connection & receiver with no reconnect semantics configured, check that connection succeeds, close it and then re-open with a retryable connection. P.S. Spotted a minor issue in the ReconnectOptions.java file and have submitted a pull request over on Github, confused the hell out of me for a while! - Cj. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: ProtonJ2 Initial connection failure, reconnect logic
On 3/12/24 04:08, Ciaran wrote:
On Mon, Mar 11, 2024 at 9:33 PM Timothy Bish wrote:
The client re-connection logic treats a SASL authentication error as a
terminal state and will not continue reconnect attempts if it receives a
SASL outcome that indicates anything other than a temporary failure
state so it should be stopping the reconnect if it was actually failing
to authenticate. This is true on the first attempt as well as on
subsequent attempts to other hosts if you add more than one and it has
failed to reach any of the preceding hosts while attempt to recover the
connection.
From the error logs attached it doesn't appear as though SASL
authentication is your issue though, at least in so much as it isn't
logging anything indicating SASL authentication as the error. Instead
the connection appears to be failing because the remote has sent a
response to the Receiver attach that does not include the initial
delivery count value as required by the specification.
You can capture more information about the AMQP frames being sent and
received by enabling frame tracing, see the docs for how to do that.
https://github.com/apache/qpid-protonj2/blob/main/protonj2-client-docs/Configuration.md#logging
Thanks for getting back to me so quickly Tim, please find below the frames
for a successful
connection and an unsuccessful connection. My test has actually been to
specify an invalid user if
that's relevant.
I can see in both cases that the SASL challenge completes successfully,
which I appreciate is
strange, but I would imagine Azure Service Bus is a common enough broker
target for the library?
So looking at the frame trace it is clear the connection is being
established as the SASL outcome is returned as 'OK' and then a normal
Open exchange occurs so from the client point of view a connection was
successfully made so any initial reconnect attempts option won't apply
here as the connection "succeeded". For the connection to fail with bad
credentials the SASL outcome would need to indicate a failure.
The connection breaks at the point the attach response arrives and is
lacking the mandatory initial-delivery-count field as per the AMQP 1.0
specification.
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-attach
It could be that the user you logged in as does not have read permission
and the server is trying to tell the client that the link will be closed
with an error condition in the Detach indicating that as the returned
response does not carry a source or target value (both are null) whereas
the sent Attach has an appropriate source and target value. If that is
what it is doing it gets it wrong as it omits the
'initial-delivery-count' which is required for an Attach with the Role
of Sender (as per referenced spec above) regardless of the outcome of
the attach.
When the username is invalid:
-> SASL:[1793436274:0] AMQP,3,1,0,0
<- SASL:[1793436274:0] AMQP,3,1,0,0
<- SASL:[1793436274:0] SaslMechanisms{saslServerMechanisms=[MSSBCBS, PLAIN,
ANONYMOUS, EXTERNAL]}
-> SASL:[1793436274:0] SaslInit{mechanism=PLAIN,
initialResponse="\x00INVALID_USERNAME\x00VALID_PASSWORD"...(truncated),
hostname='MY_HOST.servicebus.windows.net'}
<- SASL:[1793436274:0] SaslOutcome{code=OK, additionalData="Welcome!"}
-> AMQP:[1793436274:0] AMQP,0,1,0,0
<- AMQP:[1793436274:0] AMQP,0,1,0,0
-> AMQP:[1793436274:0] Open{
containerId='ID:c07c99d2-692b-4c77--b56bfeb2e2e0:1:1', hostname='
cjtestmq.servicebus.windows.net', maxFrameSize=65536, channelMax=65535,
idleTimeOut=6, outgoingLocales=null, incomingLocales=null,
offeredCapabilities=null, desiredCapabilities=[ANONYMOUS-RELAY],
properties=null}
-> AMQP:[1793436274:0] Begin{remoteChannel=null, nextOutgoingId=0,
incomingWindow=1600, outgoingWindow=2147483647, handleMax=null,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
-> AMQP:[1793436274:0]
Attach{name='receiver-ID:c07c99d2-692b-4c77--b56bfeb2e2e0:1:1:1:1',
handle=0, role=RECEIVER, sndSettleMode=UNSETTLED, rcvSettleMode=FIRST,
source=Source{address='testq', durable=NONE, expiryPolicy=LINK_DETACH,
timeout=0, dynamic=false, dynamicNodeProperties=null,
distributionMode=null, filter=null,
defaultOutcome=Modified{deliveryFailed=true, undeliverableHere=false,
messageAnnotations=null}, outcomes=[amqp:accepted:list, amqp:rejected:list,
amqp:released:list, amqp:modified:list], capabilities=null},
target=Target{address='testq', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=null, initialDeliveryCount=null,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
-> AMQP:[1793436274:0] Flow{nextIncomingId=null, incomingWindow=1600,
nextOutgoingId=0, outgoingWindow=2147483647, handle=0, deliveryCount=null,
linkCredit=10, available=null, drain=false, echo=
Re: ProtonJ2 Initial connection failure, reconnect logic
On 3/11/24 16:54, Ciaran wrote:
Hi all,
I'm taking a look at using ProtonJ2 to talk to Azure Service Bus and I've
successfully gotten everything up and running, with and without websockets,
now I'm turning my attention to the 'unhappy path' of network drop-outs and
misconfigurations leading to connection failures.
Is it possible to have a behaviour where:
- If an initial connection fails, the error is immediately propagated
and background reconnect attempts are not attempted.
- If an initial connection was successful then background reconnect
attempts are attempted.
>From looking through the api docs and reading the code, I believed that
configuring the following would exhibit the behaviours described.
options.reconnectOptions().reconnectEnabled(true);
options.reconnectOptions().maxInitialConnectionAttempts(1);
options.reconnectOptions().useReconnectBackOff();
*However, when connecting to Azure Service Bus with a deliberately invalid
password, it appears as though the reconnect logic is continuing in the
background (exceptions spamming my log ), not aborting on first connection
attempt. *Is this the expected behaviour?
I took a brief look at the code and can see that 'connectionEstablished' in
the ClientConnection class is being called even though the connection can't
possibly succeed as the authentication is wrong, is that expected behaviour
of the internals?
I've tried to summarise the code I have below, I've removed error handling,
resource cleanup for clarity:
final String serverHost = "MY_HOST.servicebus.windows.net";
final int serverPort = 443;
final String address = "testq";
final String user = "MY_USER";
final String password= "MY_PASSWORD_BUT_INVALIDATED_FOR_THIS_TEST";
final boolean useSSL = true;
final boolean useWebSockets = true;
final Client client = Client.create();
ConnectionOptions options = new
ConnectionOptions().user(user).password(password);
options.sslOptions().sslEnabled(useSSL);
options.transportOptions().useWebSockets(useWebSockets);
options.transportOptions().webSocketPath("/$servicebus/websocket");
options.reconnectOptions().reconnectEnabled(true);
options.reconnectOptions().maxInitialConnectionAttempts(1);
options.reconnectOptions().useReconnectBackOff();
Connection connection = client.connect(serverHost, serverPort, options);
ReceiverOptions ro = new ReceiverOptions();
ro.autoAccept(false);
Receiver receiver = connection.openReceiver( address, ro);
My exception / warning logs are contained at the end of the email, the
second email repeats until a ClientOperationTimedOutException is thrown
with the message 'Link open timed out waiting for remote to respond'.
Obviously, I could seperate the code into one client that does not have
reconnect logic enabled to determine if a connection is even *possible*
before engaging my proper client, but it seemed like the API offerred the
behaviour I was after?
Thank you for your patience if you made it this far
- Cj.
The client re-connection logic treats a SASL authentication error as a
terminal state and will not continue reconnect attempts if it receives a
SASL outcome that indicates anything other than a temporary failure
state so it should be stopping the reconnect if it was actually failing
to authenticate. This is true on the first attempt as well as on
subsequent attempts to other hosts if you add more than one and it has
failed to reach any of the preceding hosts while attempt to recover the
connection.
From the error logs attached it doesn't appear as though SASL
authentication is your issue though, at least in so much as it isn't
logging anything indicating SASL authentication as the error. Instead
the connection appears to be failing because the remote has sent a
response to the Receiver attach that does not include the initial
delivery count value as required by the specification.
You can capture more information about the AMQP frames being sent and
received by enabling frame tracing, see the docs for how to do that.
https://github.com/apache/qpid-protonj2/blob/main/protonj2-client-docs/Configuration.md#logging
Exception / logs below ---
20:49:52,348 WARN SaslMechanismSelector:130 - Caught exception while
trying to create SASL mechanism MSSBCBS: No Matching SASL Mechanism with
name: MSSBCBS
20:49:52,652 WARN ClientTransportListener:63 - Caught problem during
incoming data processing: Sending peer attach had no initial delivery count
org.apache.qpid.protonj2.engine.exceptions.EngineFailedException: Sending
peer attach had no initial delivery count
at
org.apache.qpid.protonj2.engine.exceptions.ProtonExceptionSupport.createFailedException(ProtonExceptionSupport.java:63)
at
org.apache.qpid.protonj2.engine.exceptions.ProtonExceptionSupport.createFailedException(ProtonExceptionSupport.java:31)
at
org.apache.qpid.protonj2.engine.impl.ProtonEngine.engineFailed(ProtonEngine.java:306)
at
Re: ProtonJ2 client > senderId used for sender source name
On 2/26/24 12:00, Arnaud Cogoluègnes wrote: Thanks for the reply. My understanding is that it does not matter much, right? Would it be OK to change this line [1] and pass in the address variable instead of the senderId? I tried locally: it does not break the test suite and fixes the link pairing issue. This is trivial, I can submit a PR. I have resolved this in the following issue as it makes sense they sender and receiver should at least be consistent https://issues.apache.org/jira/browse/PROTON-2796 Thanks. [1] https://github.com/apache/qpid-protonj2/blob/b5ac05d77ce697d0290643709bb2f5d718a1a673/protonj2-client/src/main/java/org/apache/qpid/protonj2/client/impl/ClientSenderBuilder.java#L120 On Mon, Feb 26, 2024 at 5:52 PM Robbie Gemmell wrote: I would guess just because it was inspired by earlier code that did much the same long before the link-pair extension ever existed, and it just hasnt been used by anyone wanting to do link pairing (which isnt that widely used; referenced by some other extension specs that..). The protocol spec won't cover this as it is essentially an arbitrary choice in its eyes and indeed for most use cases (unless, say, you try to do link-pairs). What it definitely does say is that you dont need to populate the field at all for the typical 'simple client end' terminus of a link (from memory there is also a c error in there when it covers this, in terms of its references to source/target). I expect the existing options don't let you set the 'local' source/target address since the other side is usually the important one and set implicitly most of the time, and also more so just as the options classes are used in common for sender/receiver creation and so allowing that would mean one of them can easily clash with other configuration and perhaps need additional validation added, e.g clashing with whats set implicitly, or e.g with a request for dynamic that forbids setting it. On Mon, 26 Feb 2024 at 14:58, Arnaud Cogoluègnes wrote: Hi. Any reason for using the senderId instead of the address for the source address of a sender (e.g. [1])? This does not align with what's done for receivers where the address is used for both the source and target address and I don't see anything specific in the spec that justifies this choice. The source address then ends up being something like ID:bbd3c071-efd4-4ee4-be3d-870ee90b7d7e:2:1:1:1. This makes it impossible to implement Link Pairing [2], as the 2 following conditions cannot be met: * The source address for L1 is identical to the target address for L2 * The source address for L2 is identical to the target address for L1 Would it be possible to set the target/source addresses from the client API? Thanks. [1] https://github.com/apache/qpid-protonj2/blob/b5ac05d77ce697d0290643709bb2f5d718a1a673/protonj2-client/src/main/java/org/apache/qpid/protonj2/client/impl/ClientSenderBuilder.java#L120 [2] https://docs.oasis-open.org/amqp/linkpair/v1.0/linkpair-v1.0.html - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: ProtonJ2 client asynchronous API?
On 2/12/24 12:03, Arnaud Cogoluègnes wrote: Hi. I'm trying out ProtonJ2 client and I noticed it's only possible to check the status of a sent message and receive messages in a "pull-based manner" (Future and Receiver#receive). I was wondering what the rationale is behind this design (e.g. let the user decide on the threading model to get outbound message status and inbound messages). Are there any plans to provide an asynchronous API in the client library, based on e.g. user-provided callbacks or standard API like CompletableFuture? Thanks! There are no plans to implement an asynchronous API for the protonj2 client no. The client provides a simple imperative API that applications and frameworks can use to implement their own preference of asynchronous handling for send completion and receive calls. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid protonj2 1.0.0-M19
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache protonj2 1.0.0-M19. This is the latest release of our AMQP Java client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M19/release-notes.html Thanks to all involved, - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] enroll Proton and Dispatch in Packit-as-a-Service CI offering from Fedora
On 1/12/24 11:11, Jiri Daněk wrote: I'd like to enable Packit-as-a-Service ( https://github.com/marketplace/packit-as-a-service) for Qpid Proton and Qpid Dispatch GitHub repositories, so that every new PR gets tested on Fedora infrastructure (latest released Fedora and Fedora Rawhide). There are three (gradually more involved) ways to use Packit: 1. use it as a CI system that runs on Fedora (configurable version and system architecture (x86_64, aarch64). The job steps are incidentally written in a RPM spec file, but we don't use the produced RPM 2. write the spec in a way that it builds useful RPM, but don't publish the rpm and don't synchronize the spec file with the spec file that Fedora uses in its Proton build 3. keep the RPM specs in sync with fedora, when new Proton is released, use a single packit command to propose spec changes and version upgrade from the upstream proton spec to Fedora Rawhide My intention is to get Proton all the way to the third scenario. There are three steps to do this: First, if the plan is approved in a vote here, ASF infra will enable the GitHub integration, https://issues.apache.org/jira/browse/INFRA-25349 (authed link) Then, a RPM spec file needs to be written and committed to the repository. I volunteer to do that. The Packit CI job will be building from this spec file. I'd like to place the spec in a packaging/ sub directory, so that files for other packaging systems can be added later and it does not clutter the /. Finally, the spec file should be brought into 1:1 correspondence with the spec file that Fedora itself uses. This way, changes to Fedora's spec can be proposed and tested in the ASF project first and then shipped into Fedora (Rawhide). Benefits: * Compilation of Fedora will be tested directly in the GitHub repo and issues can be fixed right away. * Packit infrastructure offers arm64 machines, so we can opt into compiling on arm as well Supplementary information: * Packit website: https://packit.dev/ * Packit guide (GitHub integration): https://packit.dev/docs/guide * Packit-as-a-Service: https://github.com/marketplace/packit-as-a-service * Fedora wiki page: https://fedoraproject.org/wiki/Packit Thank you, +1 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid protonj2 1.0.0-M19
There were 5 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M19 (RC1)
On 1/8/24 12:08, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M19 Qpid protonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M19-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1271 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353988 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1271 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M19 org.apache.qpid protonj2-client 1.0.0-M19 +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked source license headers with 'mvn apache-rat:check' * Built from source and ran the tests * Ran included examples using staged artifacts against an ActiveMQ Artemis broker instance. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid protonj2 1.0.0-M19 (RC1)
Hi folks, I have put together a release candidate for a 1.0.0-M19 Qpid protonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M19-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1271 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353988 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1271 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M19 org.apache.qpid protonj2-client 1.0.0-M19 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid protonj2 1.0.0-M18 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache protonj2 1.0.0-M18. This is the latest release of our AMQP Java client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M18/release-notes.html Thanks to all involved, - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid protonj2 1.0.0-M18
There were 4 binding +1 votes, and one other vote received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M18
On 11/1/23 10:22, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M18 Qpid protonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M18-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1270 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353499 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1270 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M18 org.apache.qpid protonj2-client 1.0.0-M18 +1 * Validated signatures and checksums * Verified license and notice files in archives * Verified source license headers with 'mvn apache-rat:check' * Built from source and ran the tests * Ran the examples against an ActiveMQ Artemis instance -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid protonj2 1.0.0-M18
Hi folks, I have put together a release candidate for a 1.0.0-M18 Qpid protonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M18-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1270 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353499 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1270 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M18 org.apache.qpid protonj2-client 1.0.0-M18 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 2.5.0
On 10/26/23 12:46, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 2.5.0 Qpid JMS client release, please give it a test out and vote accordingly. The staged source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/jms/2.5.0-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1269 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12353391 Regards, Robbie P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1269 The dependency for the client itself would then be: org.apache.qpid qpid-jms-client 2.5.0 - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org +1 * Validated signatures and checksums * Verified license and notice files in archives * Verified source license headers with 'mvn apache-rat:check' * Built from source and ran the unit tests * Ran the included example using the staged artifacts against ActiveMQ Artemis -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 1.11.0
On 10/26/23 12:08, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 1.11.0 Qpid JMS client release, please give it a test out and vote accordingly. The staged source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/jms/1.11.0-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1268 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12353390 Regards, Robbie P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1268 The dependency for the client itself would then be: org.apache.qpid qpid-jms-client 1.11.0 - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org +1 * Validated signatures and checksums * Verified license and notice files in archives * Verified source license headers with 'mvn apache-rat:check' * Built from source and ran the tests * Built the example from staged artifacts and ran it against ActiveMQ Artemis -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid protonj2 1.0.0-M17 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache protonj2 1.0.0-M17. This is the latest release of our AMQP Java client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M17/release-notes.html Thanks to all involved, - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid protonj2 1.0.0-M17
There were 3 binding +1 votes, and 1 other vote received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M17
Vote remains open awaiting another binding +1 from someone with time to give a quick review. On 7/25/23 11:49, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M17 Qpid protonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M17-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1264 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353394 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1264 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M17 org.apache.qpid protonj2-client 1.0.0-M17 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M17
On 7/25/23 11:49, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M17 Qpid protonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M17-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1264 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353394 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1264 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M17 org.apache.qpid protonj2-client 1.0.0-M17 +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked source with 'mvn apache-rat:check' * Built from source and ran the tests * Ran the examples against an ActiveMQ Artemis broker instance. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid protonj2 1.0.0-M17
Hi folks, I have put together a release candidate for a 1.0.0-M17 Qpid protonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M17-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1264 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353394 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1264 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M17 org.apache.qpid protonj2-client 1.0.0-M17 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid protonj2 1.0.0-M16 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache ProtonJ2 1.0.0-M16. This is the latest release of our AMQP Java client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M16/release-notes.html Thanks to all involved, - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid protonj2 1.0.0-M16
There were 4 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 2.4.0
On 6/27/23 12:09, Robbie Gemmell wrote: On Tue, 27 Jun 2023 at 16:17, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 2.4.0 Qpid JMS client release, please give it a test out and vote accordingly. The staged source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/jms/2.4.0-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1263 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12353304 Regards, Robbie P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1263 The dependency for the client itself would then be: org.apache.qpid qpid-jms-client 2.4.0 +1 I checked things out as follows: - Verified the signature + checksum files. - Checked for LICENCE + NOTICE files in the archives. - Used "mvn apache-rat:check" to check headers in the source archive. - Ran the build and tests from the source archive on JDK11. - Ran HelloWorld example against ActiveMQ Artemis main, on JDK11. - Built Quarkus extension for Qpid JMS using staged client and tested on JDK11 and 17. Robbie - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org +1 * Validated signatures and checksums * Verified license and notice files in archives * Verified source license headers with 'mvn apache-rat:check' * Built from source and ran the tests * Built the example from the binary using staged artifacts and ran them against an Artemis broker instance. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 1.10.0
On 6/27/23 10:32, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 1.10.0 Qpid JMS client release, please give it a test out and vote accordingly. The staged source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/jms/1.10.0-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1262 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12353303 Regards, Robbie P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1262 The dependency for the client itself would then be: org.apache.qpid qpid-jms-client 1.10.0 - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org +1 * Validated signatures and checksums * Verified license and notice files in archives * Verified source license headers with 'mvn apache-rat:check' * Built from source and ran the tests * Built the example from the binary using staged artifacts and ran them against an Artemis broker instance. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M16
On 6/26/23 12:54, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M16 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M16-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1261 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353206 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1261 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M16 org.apache.qpid protonj2-client 1.0.0-M16 +1 * Validated signatures and checksums * Verified license and notice files in archives * Verified source license headers with 'mvn apache-rat:check' * Built from source and ran the test suite * Ran the examples against an ActiveMQ Artemis install -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid protonj2 1.0.0-M16
Hi folks, I have put together a release candidate for a 1.0.0-M16 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M16-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1261 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353206 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1261 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M16 org.apache.qpid protonj2-client 1.0.0-M16 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid proton-dotnet 1.0.0-M9 released
{Subject} [ANNOUNCE] Apache Qpid proton-dotnet 1.0.0-M9 released
{template}
The Apache Qpid (http://qpid.apache.org) community is pleased to
announce the immediate availability of Apache proton-dotnet 1.0.0-M9.
This is the latest release of our AMQP .NET client supporting the
Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464,
http://www.amqp.org), based around the Apache Qpid proton-dotnet
protocol engine also contained in this release.
The release is available now from our website:
http://qpid.apache.org/download.html
Release notes can be found at:
http://qpid.apache.org/releases/qpid-proton-dotnet-1.0.0-M9/release-notes.html
Thanks to all involved,
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid proton-dotnet 1.0.0-M9
There were three binding +1 votes, and one other votes received. The vote has passed. I will add the files to the dist release repo and release shortly. The website will be updated after the release has had time to sync to the mirrors. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M9
Hi folks, gentle reminder that this vote still remains open pending one additional binding +1 On Mon, May 22, 2023 at 6:33 PM Timothy Bish wrote: > > Hi folks, > > I have put together a release candidate for a 1.0.0-M9 Qpid > proton-dotnet release, > please give it a test out and vote accordingly. > > Tests can be run using the build script in the source archive: > > "./build.sh podman-test" or "./build.sh docker-test" > > The source and binary archives can be grabbed from: > https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M9-rc1/ > > The JIRAs assigned are: > https://issues.apache.org/jira/projects/PROTON/versions/12353225 > > Regards > > -- > Tim Bish > -- -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M9
On 5/22/23 18:33, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M9 Qpid proton-dotnet release, please give it a test out and vote accordingly. Tests can be run using the build script in the source archive: "./build.sh podman-test" or "./build.sh docker-test" The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M9-rc1/ The JIRAs assigned are: https://issues.apache.org/jira/projects/PROTON/versions/12353225 Regards +1 * Validated signatures and checksums * Verified license and notice files * Verified source license headers with 'mvn apache-rat:check' * Built from source and ran the test suite on Ubuntu * Built from source and ran the test suite on Windows 10 * Built the examples and ran them against an ActiveMQ Artemis instance. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid proton-dotnet 1.0.0-M9
Hi folks, I have put together a release candidate for a 1.0.0-M9 Qpid proton-dotnet release, please give it a test out and vote accordingly. Tests can be run using the build script in the source archive: "./build.sh podman-test" or "./build.sh docker-test" The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M9-rc1/ The JIRAs assigned are: https://issues.apache.org/jira/projects/PROTON/versions/12353225 Regards -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 2.3.0
On 5/17/23 13:41, Robbie Gemmell wrote: I have put together a spin for a 2.3.0 Qpid JMS client release, please give it a test out and vote accordingly. The staged source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/jms/2.3.0-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1260 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12352748 Regards, Robbie P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1260 The dependency for the client itself would then be: org.apache.qpid qpid-jms-client 2.3.0 - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked source license headers with 'apache-rat:check' * Built from source and ran the tests * Built the example using the staged artifacts and ran it against an Artemis broker instance. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 1.9.0
On 5/17/23 12:44, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 1.9.0 Qpid JMS client release, please give it a test out and vote accordingly. The staged source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/jms/1.9.0-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1259 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12352747 Regards, Robbie P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1259 The dependency for the client itself would then be: org.apache.qpid qpid-jms-client 1.9.0 - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked source license headers with 'apache-rat:check' * Built from source and ran the tests * Built the example using the staged artifacts and ran it against an Artemis broker instance. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid proton-dotnet 1.0.0-M8 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache proton-dotnet 1.0.0-M8. This is the latest release of our AMQP .NET client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid proton-dotnet protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Release notes can be found at: http://qpid.apache.org/releases/qpid-proton-dotnet-1.0.0-M8/release-notes.html Thanks to all involved, - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid proton-dotnet 1.0.0-M8
There were 3 binding +1 votes, and 1 other votes received. The vote has passed. I will add the files to the dist release repo and release shortly. The website will be updated after the release has had time to sync to the mirrors. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M8 (RC1)
On 5/8/23 12:12, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M8 Qpid proton-dotnet release, please give it a test out and vote accordingly. Tests can be run using the build script in the source archive: "./build.sh podman-test" or "./build.sh docker-test" The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M8-rc1/ The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352669 +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked for license headers in archives with 'mvn apache-rat' * Ran the tests using the script './build.sh podman-test' on Ubuntu * Ran the tests using the script 'dotnet test' on Windows 10 * Ran the examples against a ActiveMQ Artemis broker instance. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid proton-dotnet 1.0.0-M8 (RC1)
Hi folks, I have put together a release candidate for a 1.0.0-M8 Qpid proton-dotnet release, please give it a test out and vote accordingly. Tests can be run using the build script in the source archive: "./build.sh podman-test" or "./build.sh docker-test" The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M8-rc1/ The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352669 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid protonj2 1.0.0-M15 released
{Subject} [ANNOUNCE] Apache Qpid ProtonJ2 1.0.0-M15 released
{template}
The Apache Qpid (http://qpid.apache.org) community is pleased to
announce the immediate availability of Apache ProtonJ2 1.0.0-M15.
This is the latest release of our AMQP Java client supporting the
Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464,
http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol
engine also contained in this release.
The release is available now from our website:
http://qpid.apache.org/download.html
Binaries are also available via Maven Central:
http://qpid.apache.org/maven.html
Release notes can be found at:
http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M15/release-notes.html
Thanks to all involved,
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid protonj2 1.0.0-M15
There were 5 binding +1 votes, and 1 other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M15
On 5/2/23 13:27, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M15 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M15-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1258 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353134 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1258 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M15 org.apache.qpid protonj2-client 1.0.0-M15 +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked source for license headers with 'mvn apache-rat:check' * Built from source and ran the unit tests * Ran the included examples against an ActiveMQ Artemis instance using the staged assets. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid protonj2 1.0.0-M15
Hi folks, I have put together a release candidate for a 1.0.0-M15 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M15-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1258 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353134 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1258 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M15 org.apache.qpid protonj2-client 1.0.0-M15 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid ProtonJ2 1.0.0-M14 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache ProtonJ2 1.0.0-M14. This is the latest release of our AMQP Java client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M14/release-notes.html Thanks to all involved, -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid ProtonJ2 1.0.0-M14
There were 3 binding +1 votes, and 1 other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M14
On 4/10/23 11:55, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M14 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M14-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1257 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353064 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1257 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M14 org.apache.qpid protonj2-client 1.0.0-M14 +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked source for license headers with 'mvn apache-rat:check' * Built from source and ran the unit tests * Ran the included examples against an ActiveMQ Artemis instance using the staged assets. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid ProtonJ2 1.0.0-M14
Hi folks, I have put together a release candidate for a 1.0.0-M14 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M14-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1257 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353064 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1257 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M14 org.apache.qpid protonj2-client 1.0.0-M14 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid ProtonJ2 1.0.0-M13 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache ProtonJ2 1.0.0-M13. This is the latest release of our AMQP Java client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M13/release-notes.html Thanks to all involved - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid ProtonJ2 1.0.0-M13
There were 4 binding +1 votes, and one other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M13 (RC1)
On 3/27/23 15:03, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M13 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M13-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1256 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352763 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1256 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M13 org.apache.qpid protonj2-client 1.0.0-M13 +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked license headers with 'mvn apache-rat:check' * Built from source and ran the tests * Built the examples against the staged artifacts and ran them against an AcitveMQ Artemis install -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid ProtonJ2 1.0.0-M13 (RC1)
Hi folks, I have put together a release candidate for a 1.0.0-M13 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M13-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1256 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352763 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1256 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M13 org.apache.qpid protonj2-client 1.0.0-M13 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid Proton-J 0.34.1
On 3/2/23 13:00, Robbie Gemmell wrote: Hi folks, I have put together a spin for a Qpid Proton-J 0.34.1 release, please test it and vote accordingly. The files can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.34.1-rc1/ The maven artifacts are staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1255 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352971 Regards, Robbie P.S. If you want to test things out using maven with your own build you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1255 The dependency for proton-j would then be: org.apache.qpid proton-j 0.34.1 - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org +1 * Validated signatures and checksums * Verified license and notice files in archives * Verified license headers in source with 'mvn apache-rat:check' * Built from source and ran the tests * Built ActiveMQ Artemis main with the staged artifacts and ran the tests. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: ProtonJ2 loading key + trust from a jar
On 1/27/23 09:18, Segesten, Henrik wrote: Hi I am using ProtonJ2 as client for connecting to a broker which uses private key authentication and a custom trust store. I have managed to accomplish this by setting: options.sslOptions().sslEnabled(true); options.sslOptions().keyStoreLocation(keyStoreLocation); options.sslOptions().keyStorePassword(keyStorePassword); The problem I have is that these two locations are instantiated as java.File within ProtonJ2 which means that they need to exist in the file system, and I would like to package them within my single spring boot jar. I have not managed to accomplish this but have to put the two files next to the jar. In my experience this could be solved if ProtonJ2 would load the files from a Path or URL instead which can reside within the jar. Looking at the code I think this happens in https://github.com/apache/qpid-protonj2/blob/main/protonj2-client/src/main/java/org/apache/qpid/protonj2/client/transport/netty5/SslSupport.java, private method loadStore at the end. I would really appreciate any support in how I can resolve this in some other way than changing the code. Best Regards Henrik Segesten The SslOptions provides a mechanism for providing your own SslContext which allows you to configure the key and trust stores using whatever mechanisms you see fit, thereby bypassing the inbuilt configuration loading mechanisms. options.sslOptions().sslContextOverride(); -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid ProtonJ2 1.0.0-M12 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache ProtonJ2 1.0.0-M12. This is the latest release of our AMQP Java client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M12/release-notes.html Thanks to all involved, - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid ProtonJ2 1.0.0-M12
There were 1.0.0-M12 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M12
On 1/10/23 16:24, Timothy Bish wrote:
Hi folks,
I have put together a release candidate for a 1.0.0-M12 Qpid ProtonJ2
release,
please give it a test out and vote accordingly.
The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M12-rc1/
The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1254
The JIRAs assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352532
Regards
P.S. If you want to test it out using maven (e.g with the examples
src, or your own things), you can temporarily add this to your poms to
access the staging repo:
staging
https://repository.apache.org/content/repositories/orgapacheqpid-1254
The dependency for the protocol engine or the client itself would then
be:
org.apache.qpid
protonj2
1.0.0-M12
org.apache.qpid
protonj2-client
1.0.0-M12
{template}
+1
* Validated signatures and checksums
* Verified license and notice files in archives
* Checked source license headers with 'mvn apache-rat:check'
* Built from source and ran the tests
* Ran the examples against an ActiveMQ Artemis broker instance.
--
Tim Bish
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 1.8.0
On 1/10/23 12:02, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 1.8.0 Qpid JMS client release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/jms/1.8.0-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1252 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12352308 Regards, Robbie P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1252 The dependency for the client itself would then be: org.apache.qpid qpid-jms-client 1.8.0 - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked source license headers with 'mvn apache-rat:check' * Built from source and ran the tests * Ran the example against an ActiveMQ Artemis broker instance. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 2.2.0
On 1/10/23 12:55, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 2.2.0 Qpid JMS client release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/jms/2.2.0-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1253 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12352307 Regards, Robbie P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1253 The dependency for the client itself would then be: org.apache.qpid qpid-jms-client 2.2.0 - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked source license headers with 'mvn apache-rat:check' * Built from source and ran the tests * Ran the example against an ActiveMQ Artemis broker instance. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid ProtonJ2 1.0.0-M12
Hi folks,
I have put together a release candidate for a 1.0.0-M12 Qpid ProtonJ2
release,
please give it a test out and vote accordingly.
The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M12-rc1/
The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1254
The JIRAs assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352532
Regards
P.S. If you want to test it out using maven (e.g with the examples
src, or your own things), you can temporarily add this to your poms to
access the staging repo:
staging
https://repository.apache.org/content/repositories/orgapacheqpid-1254
The dependency for the protocol engine or the client itself would then be:
org.apache.qpid
protonj2
1.0.0-M12
org.apache.qpid
protonj2-client
1.0.0-M12
{template}
--
Tim Bish
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid proton-dotnet 1.0.0-M7 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache proton-dotnet 1.0.0-M7. This is the latest release of our AMQP .NET client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid proton-dotnet protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Release notes can be found at: http://qpid.apache.org/releases/qpid-proton-dotnet-1.0.0-M7/release-notes.html Thanks to all involved, - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid proton-dotnet 1.0.0-M7
There were 4 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release shortly. The website will be updated after the release has had time to sync to the mirrors. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M7
On 12/5/22 16:49, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M7 Qpid proton-dotnet release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M7-rc1/ The JIRAs assigned are: https://issues.apache.org/jira/projects/PROTON/versions/12352533 Regards +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked license headers in source with 'mvn apache-rat:check' * Built from source and ran the tests * Ran the examples against an Artemis broker instance -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid proton-dotnet 1.0.0-M7
Hi folks, I have put together a release candidate for a 1.0.0-M7 Qpid proton-dotnet release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M7-rc1/ The JIRAs assigned are: https://issues.apache.org/jira/projects/PROTON/versions/12352533 Regards -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid ProtonJ2 1.0.0-M11 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache ProtonJ2 1.0.0-M11. This is the latest release of our AMQP Java client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M11/release-notes.html Thanks to all involved, - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid proton-dotnet 1.0.0-M6 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache proton-dotnet 1.0.0-M6. This is the latest release of our AMQP .NET client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid proton-dotnet protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Release notes can be found at: http://qpid.apache.org/releases/qpid-proton-dotnet-1.0.0-M6/release-notes.html Thanks to all involved - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid ProtonJ2 1.0.0-M11
There were 3 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid proton-dotnet 1.0.0-M6
There were 3 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release shortly. The website will be updated after the release has had time to sync to the mirrors. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M11
On 11/8/22 13:00, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M11 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M11-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1250 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352473 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1250 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M11 org.apache.qpid protonj2-client 1.0.0-M11 +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked source license headers with 'mvn apache-rat:check' * Built from source and ran the tests * Ran the examples against an ActiveMQ Artemis broker instance. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M6
On 11/8/22 14:46, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M6 Qpid proton-dotnet release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M6-rc1/ The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352477 Regards +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked source license headers with 'mvn apache-rat:check' * Built from source and ran the tests * Ran the examples against an ActiveMQ Artemis broker instance. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid proton-dotnet 1.0.0-M6
Hi folks, I have put together a release candidate for a 1.0.0-M6 Qpid proton-dotnet release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M6-rc1/ The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352477 Regards -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid ProtonJ2 1.0.0-M11
Hi folks, I have put together a release candidate for a 1.0.0-M11 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M11-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1250 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352473 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1250 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M11 org.apache.qpid protonj2-client 1.0.0-M11 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid Proton 0.38.0
On 11/7/22 12:26, Robbie Gemmell wrote: Hi folks, I have put together a first spin for a Qpid Proton 0.38.0 release, please give it a test out and vote accordingly. The files can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.38.0-rc1/ The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12351344 It is tagged as 0.38.0-rc1. Regards, Robbie - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org +1 * Verified signatures and checksums * Verified license and notice files * Built from source and ran the tests -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid ProtonJ2 1.0.0-M10 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache ProtonJ2 . This is the latest release of our AMQP Java client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M10/release-notes.html Thanks to all involved, - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid ProtonJ2 1.0.0-M10
There were 3 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid proton-dotnet 1.0.0-M5 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache proton-dotnet 1.0.0-M5. This is the latest release of our AMQP .NET client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid proton-dotnet protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Release notes can be found at: http://qpid.apache.org/releases/qpid-proton-dotnet-1.0.0-M5/release-notes.html Thanks to all involved, - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid proton-dotnet 1.0.0-M5
There were 3 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release shortly. The website will be updated after the release has had time to sync to the mirrors. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M10
On 10/26/22 12:47, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M10 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M10-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1248 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352341 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1248 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M10 org.apache.qpid protonj2-client 1.0.0-M10 +1 * Validated signatures and checksums * Verified license and notice files in archives * Verified license headers in source tree using 'mvn apache-rat:check' * Built from source and ran the tests * Ran the examples against an Artemis broker install -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid ProtonJ2 1.0.0-M10
Hi folks, I have put together a release candidate for a 1.0.0-M10 Qpid ProtonJ2 release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M10-rc1/ The maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1248 The JIRAs assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352341 Regards P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1248 The dependency for the protocol engine or the client itself would then be: org.apache.qpid protonj2 1.0.0-M10 org.apache.qpid protonj2-client 1.0.0-M10 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M5
On 10/24/22 13:04, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M5 Qpid proton-dotnet release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M5-rc1/ The JIRAs assigned are: https://issues.apache.org/jira/projects/PROTON/versions/12352342 Regards +1 * Validated signatures and checksums * Verified license and notice files in archives * Checked source license headers with 'mvn apache-rat:check' * Built from source and ran the tests * Ran examples against an ActiveMQ Artemis broker installation -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Apache Qpid proton-dotnet 1.0.0-M5
Hi folks, I have put together a release candidate for a 1.0.0-M5 Qpid proton-dotnet release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M5-rc1/ The JIRAs assigned are: https://issues.apache.org/jira/projects/PROTON/versions/12352342 Regards -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [protonj2] How do I force the library to send Detach frame on the wire?
On 10/10/22 11:15, Jiri Daněk wrote:
I want to remove a durable subscriber that I have created on the remote
peer, which is the Artemis messaging broker.
How do I do this correctly? (Also, as a broader question, where do I find
complete instructions for working with durable subscriptions on Artemis
broker using an AMQP client, as opposed to JMS 2.0 client?)
Currently, I am using this code
https://github.com/rh-messaging/cli-java/blob/6c2cfc02984cfd93b44d306973f83422f716aeba/cli-protonj2/src/main/java/com/redhat/mqe/CliProtonJ2Receiver.java#L240-L243
that is, I create a receiver and then call receiver.close(). (If I wanted
to keep the durable subscriber active, I'd do receiver.detach() instead).
This is what happens when I export PN_TRACE_FRM=true
-> SASL:[1658511941:0] AMQP,3,1,0,0
<- SASL:[1658511941:0] AMQP,3,1,0,0
<- SASL:[1658511941:0] SaslMechanisms{saslServerMechanisms=[PLAIN,
ANONYMOUS]}
-> SASL:[1658511941:0] SaslInit{mechanism=PLAIN,
initialResponse="\x00admin\x00admin", hostname='null'}
<- SASL:[1658511941:0] SaslOutcome{code=OK, additionalData=null}
-> AMQP:[1658511941:0] AMQP,0,1,0,0
<- AMQP:[1658511941:0] AMQP,0,1,0,0
-> AMQP:[1658511941:0] Open{ containerId='cliId0', hostname='127.0.0.1',
maxFrameSize=65536, channelMax=65535, idleTimeOut=6,
outgoingLocales=null, incomingLocales=null, offeredCapabilities=null,
desiredCapabilities=[sole-connection-for-container, DELAYED_DELIVERY,
SHARED-SUBS, ANONYMOUS-RELAY], properties=null}
-> AMQP:[1658511941:0] Close{error=null}
<- AMQP:[1658511941:0] Open{ containerId='amq', hostname='null',
maxFrameSize=131072, channelMax=65535, idleTimeOut=3,
outgoingLocales=null, incomingLocales=null,
offeredCapabilities=[sole-connection-for-container, DELAYED_DELIVERY,
SHARED-SUBS, ANONYMOUS-RELAY], desiredCapabilities=null,
properties={product=apache-activemq-artemis, version=2.26.0}}
<- AMQP:[1658511941:0] Close{error=null}
Client does not even bother doing Begin/Attach/Detach! So the durable
subscriber stays active.
You need to use the openFuture of the Receiver to wait until the remote
has fully opened it and then close the receiver to ensure that you get
the behavior you are looking for. In this case it is quite likely that
the connection was still not fully setup when you opened and closed the
receiver resulting in the engine deciding there was no need to send the
performatives since you opened and closed before the connection likely
finished the SASL exchange. For an operation like this it makes sense
to always ensure the receiver fully opened as the open can fail but
closing it wouldn't tell you that.
What I want to happen is something similar to what I can get with Qpid JMS,
which is
[1253727474:0] -> SASL
[1253727474:0] <- SASL
[1253727474:0] <- SaslMechanisms{saslServerMechanisms=[PLAIN, ANONYMOUS]}
[1253727474:0] -> SaslInit{mechanism=PLAIN,
initialResponse=\x00admin\x00admin, hostname='127.0.0.1'}
[1253727474:0] <- SaslOutcome{_code=OK, _additionalData=null}
[1253727474:0] <- AMQP
[1253727474:0] -> AMQP
[1253727474:0] -> Open{ containerId='cliId0', hostname='127.0.0.1',
maxFrameSize=1048576, channelMax=32767, idleTimeOut=3,
outgoingLocales=null, incomingLocales=null, offeredCapabilities=null,
desiredCapabilities=[sole-connection-for-container, DELAYED_DELIVERY,
ANONYMOUS-RELAY, SHARED-SUBS], properties={product=QpidJMS, version=2.1.0,
platform=JVM: 11.0.17-ea, 11.0.17-ea+1, Red Hat, Inc., OS: Linux,
5.19.11-300.fc37.x86_64, amd64}}
[1253727474:0] <- Open{ containerId='amq', hostname='null',
maxFrameSize=131072, channelMax=65535, idleTimeOut=3,
outgoingLocales=null, incomingLocales=null,
offeredCapabilities=[sole-connection-for-container, DELAYED_DELIVERY,
SHARED-SUBS, ANONYMOUS-RELAY], desiredCapabilities=null,
properties={product=apache-activemq-artemis, version=2.26.0}}
[1253727474:0] -> Begin{remoteChannel=null, nextOutgoingId=1,
incomingWindow=2047, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1253727474:0] <- Begin{remoteChannel=0, nextOutgoingId=1,
incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1253727474:1] -> Begin{remoteChannel=null, nextOutgoingId=1,
incomingWindow=2047, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1253727474:1] <- Begin{remoteChannel=1, nextOutgoingId=1,
incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1253727474:0] -> Attach{name='ds0', handle=0, role=RECEIVER,
sndSettleMode=UNSETTLED, rcvSettleMode=FIRST, source=null,
target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=null,
maxMessageSize=null,
Re: [protonj2] How do I ensure that all send()'t messages have been accepted by the other side?
On 10/6/22 10:36, Jiri Daněk wrote: In my code [1], I create a sender using connection.createSender(), that is, I don't use Session at all. The Artemis broker on the other side is configured to BLOCK incoming messages if the queue exceeds a certain configured size. In AMQP terms, the broker sends disposition of Rejected, which looks this way in Wireshark Advanced Message Queueing Protocol Length: 135 Doff: 2 Type: AMQP (0) Channel: 0 Performative: disposition (21) Arguments Role: receiver First: 47 Last: 47 Settled: True Rejected Error Condition: amqp:resource-limit-exceeded Description: Address is full: test_broker_blocks_client_many_messages_in_queue (See zipped capture file at https://github.com/rh-messaging/cli-java/issues/455#issuecomment-1270166736) However, my program does not respond to this as if the messages were delivered correctly, and sends detach and then close. The rejected messages then disappear. Do I need to examine the returned Tracker objects and check what became of my messages? Does the library "take responsibility" for the message the moment I call send, so I can assume any necessary buffering and redelivery will be taken care of? Is this supposed to work even if there is, say, reconnect/failover between brokers while I am sending? Send returns the tracker for you to examine and or wait on the settlement future so that you can ascertain if the remote has accepted or rejected the delivery, the client does not attempt to buffer any messages other than the singular case of a send that blocks because there is not credit in which case that blocked send will either succeed (as in writing it to the wire but still could be rejected) if credit is granted or it would fail if the link was closed (connection dropped etc). The trySend method exists to avoid that blocking behavior if your application doesn't want to deal with blocking on lack of credit scenario. When is the "send()'t but not actually sent" buffer of messages emptied? When I attempt to close the connection? What happens if there are some outstanding messages that (for some reason) cannot be delivered? Should I expect some exception in that case? (I assume that to properly handle this, I have to manage the Tracker objects myself as I am calling send(), and then maybe store the unsent messages to disk, or preserve them some other way.) As above the application needs to manage the tracker and check if the message it sent was actually accepted or rejected, or in the case of connection drop the settlement future would be failed. The client does not maintain in internal buffer of sent messages for resend, that bit is up to you as the user of the client library. Is this reject disposition-related behavior a client bug? (After thinking more about it, having written the above, I became convinced it probably is.) Not a bug as far as I can see as it sounds like it is working as intended, and there are tests checking for same. [1] https://github.com/rh-messaging/cli-java/blob/6cc43514c0ca7eee0385d227faeb574b451075f3/cli-protonj2/src/main/java/com/redhat/mqe/CliProtonJ2Sender.java#L263 -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid ProtonJ2 1.0.0-M9 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache ProtonJ2 1.0.0-M9. This is the latest release of our AMQP Java client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M9/release-notes.html Thanks to all involved, - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid proton-dotnet 1.0.0-M4 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache proton-dotnet 1.0.0-M4. This is the latest release of our AMQP .NET client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid proton-dotnet protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Release notes can be found at: http://qpid.apache.org/releases/qpid-proton-dotnet-1.0.0-M4/release-notes.html Thanks to all involved, -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid proton-dotnet 1.0.0-M4
There were 3 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release shortly. The website will be updated after the release has had time to sync to the mirrors. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid ProtonJ2 1.0.0-M9
There were 3 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
