Re: [VOTE] Release Apache Qpid JMS 1.11.0

[Tomas Vavricka]

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by 'mvn apache-rat:check'
* Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
(11.0.20.1) and OpenJDK Java 17 (17.0.8) on Ubuntu 22.04.2

Regards,
Tomas

On 2023/10/26 16:08:56 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&version=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
> 
> 

-
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

[Tomas Vavricka]

+1

On 2023/10/30 08:41:04 Tomas Vavricka wrote:
> * Verified the signature and checksum files
> * Verified LICENCE and NOTICE files in archives
> * Verified source license headers by 'mvn apache-rat:check'
> * Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
> (11.0.20.1) and OpenJDK Java 17 (17.0.8) on Ubuntu 22.04.2
> 
> Regards,
> Tomas
> 
> On 2023/10/26 16:08:56 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&version=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
> > 
> > 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

-
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

[Tomas Vavricka]

+1

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by 'mvn apache-rat:check'
* Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
(11.0.20.1) and OpenJDK Java 17 (17.0.8) on Ubuntu 22.04.2

Regards,
Tomas

On 2023/10/26 16:46:27 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&version=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
> 
> 

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

[RESULT][VOTE] Release Apache Qpid JMS 1.11.0

[Robbie Gemmell]

There were 3 binding +1 votes, 1 non-binding +1 vote, 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, updating the website and announcing after the
release has had time to sync to the CDN and maven central.

Robbie

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

[RESULT][VOTE] Release Apache Qpid JMS 2.5.0

[Robbie Gemmell]

There were 3 binding +1 votes, 1 non-binding +1 vote, 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, updating the website and announcing after the
release has had time to sync to the CDN and maven central.

Robbie

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

[ANNOUNCE] Apache Qpid JMS 2.5.0 released

[Robbie Gemmell]

The Apache Qpid (https://qpid.apache.org) community is pleased to
announce the immediate availability of Apache Qpid JMS 2.5.0.

This is the latest release of our newer JMS client supporting the
Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464,
https://www.amqp.org), based around the Apache Qpid Proton protocol
engine and implementing the AMQP JMS Mapping as it evolves at OASIS.

Note the 2.x client releases use Jakarta Messaging 3.1 and its
"jakarta.jms" package. For existing "javax.jms" use cases
continue to use the 1.x client releases.

The release is available now from our website:
https://qpid.apache.org/download.html

Binaries are also available via Maven Central:
https://qpid.apache.org/maven.html

Release notes can be found at:
https://qpid.apache.org/releases/qpid-jms-2.5.0/release-notes.html

Thanks to all involved,
Robbie

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

[ANNOUNCE] Apache Qpid JMS 1.11.0 released

[Robbie Gemmell]

The Apache Qpid (https://qpid.apache.org) community is pleased to
announce the immediate availability of Apache Qpid JMS 1.11.0.

This is the latest release of our newer JMS client supporting the
Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464,
https://www.amqp.org), based around the Apache Qpid Proton protocol
engine and implementing the AMQP JMS Mapping as it evolves at OASIS.

The release is available now from our website:
https://qpid.apache.org/download.html

Binaries are also available via Maven Central:
https://qpid.apache.org/maven.html

Release notes can be found at:
https://qpid.apache.org/releases/qpid-jms-1.11.0/release-notes.html

Thanks to all involved,
Robbie

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

RE: external event loop

[Tom Crowe]

Hi,
  Any feedback on this point... for connection_driver, must I call tick() if 
I'm not interested in Heartbeats ?

Thanks,
- Tom

From: Tom Crowe
Sent: Wednesday, October 25, 2023 5:44 PM
To: users@qpid.apache.org
Subject: RE: external event loop

Thanks Cliff for your helpful answer to this topic way back on June 30th.

"If you must manage the AMQP connection's IO yourself, then the
connection_driver class is a solid choice. The gotchas are to make
sure to call the tick() function regularly to preserve heartbeats and
to note that both input to and output from the driver can generate new
events to be dispatched."

I am curious about the tick() function.
Is preserving heartbeats the ONLY purpose of tick() ?

I don't need to use the heartbeat feature in AMQP because there is a heartbeat 
at application level.
So perhaps I don't need to call the tick() function at all ?

Or does tick() service other needs e.g. message aging in queues OR timeouts 
related to settlement OR something else ?

Thanks.

From: Tom Crowe
Sent: Friday, June 30, 2023 11:09 AM
To: users@qpid.apache.org
Subject: RE: external event loop

Discovered that search function on mail lists is returning hits, albeit hidden 
from view.
Found enough info to work from.
Thanks,
- Tom

On 2023/06/28 14:12:14 Tom Crowe wrote:
> Hi,
>   I have a working prototype with qpid proton c++ v0.37 consuming an amqps 
> 1.0 data feed.
>
> Next, I would like to incorporate the prototype into existing software. That 
> software has other networking interfaces and has a select() based event loop.

>
> How can I incorporate my qpid proton prototype into this event loop?
>
> I am encouraged when I see the 'connection_driver' class which is 'designed 
> to work with a classic reactor'.
> I am discouraged by the fact that I see 'support for third party event loop' 
> as a nice-to-have feature in the README.
>
> Is it possible to incorporate my qpid proton c++ client into the existing 
> event loop?
> If yes, how?
> Are there any examples of this?
>
> Thanks for your help.
> - Tom.
>

Re: external event loop

[Cliff Jansen]

Yes the tick function is used solely for heartbeat processing. Each peer
sets or declines to set its own heartbeat interval independently.

If you never call the tick function, you fail to send empty heartbeat
frames in time to the peer if required. You also fail to enforce the
presence of inbound frames from the peer within the local heartbeat time
limit you may have specified.

If you have control of both ends of the connection and turn off heartbeats
completely, you do not need to call tick or rely on application heartbeat
activity to satisfy the wire protocol to keep the connection alive.

If you only have control on your side and wish to avoid using the tick
call, then your application heartbeat activity must involve sending AMQP
frames to the peer no less frequently than specified in the peer’s AMQP
connection settings for the remote heartbeat.  Such frames would include
sending message content or updating credit.  Frames sent by the peer to you
would not count towards keeping the connection alive.



On Mon, Oct 30, 2023 at 12:45 PM Tom Crowe  wrote:

> Hi,
>   Any feedback on this point... for connection_driver, must I call tick()
> if I'm not interested in Heartbeats ?
>
> Thanks,
> - Tom
>
> From: Tom Crowe
> Sent: Wednesday, October 25, 2023 5:44 PM
> To: users@qpid.apache.org
> Subject: RE: external event loop
>
> Thanks Cliff for your helpful answer to this topic way back on June 30th.
>
> "If you must manage the AMQP connection's IO yourself, then the
> connection_driver class is a solid choice. The gotchas are to make
> sure to call the tick() function regularly to preserve heartbeats and
> to note that both input to and output from the driver can generate new
> events to be dispatched."
>
> I am curious about the tick() function.
> Is preserving heartbeats the ONLY purpose of tick() ?
>
> I don't need to use the heartbeat feature in AMQP because there is a
> heartbeat at application level.
> So perhaps I don't need to call the tick() function at all ?
>
> Or does tick() service other needs e.g. message aging in queues OR
> timeouts related to settlement OR something else ?
>
> Thanks.
>
> From: Tom Crowe
> Sent: Friday, June 30, 2023 11:09 AM
> To: users@qpid.apache.org
> Subject: RE: external event loop
>
> Discovered that search function on mail lists is returning hits, albeit
> hidden from view.
> Found enough info to work from.
> Thanks,
> - Tom
>
> On 2023/06/28 14:12:14 Tom Crowe wrote:
> > Hi,
> >   I have a working prototype with qpid proton c++ v0.37 consuming an
> amqps 1.0 data feed.
> >
> > Next, I would like to incorporate the prototype into existing software.
> That software has other networking interfaces and has a select() based
> event loop.
>
> >
> > How can I incorporate my qpid proton prototype into this event loop?
> >
> > I am encouraged when I see the 'connection_driver' class which is
> 'designed to work with a classic reactor'.
> > I am discouraged by the fact that I see 'support for third party event
> loop' as a nice-to-have feature in the README.
> >
> > Is it possible to incorporate my qpid proton c++ client into the
> existing event loop?
> > If yes, how?
> > Are there any examples of this?
> >
> > Thanks for your help.
> > - Tom.
> >
>