[jira] [Resolved] (QPIDJMS-597) Update to Netty 4.1.108

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPIDJMS-597.

Resolution: Fixed

> Update to Netty 4.1.108
> ---
>
> Key: QPIDJMS-597
> URL: https://issues.apache.org/jira/browse/QPIDJMS-597
> Project: Qpid JMS
>  Issue Type: Task
>  Components: qpid-jms-client
>        Reporter: Robbie Gemmell
>    Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.12.0, 2.6.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (QPIDJMS-597) Update to Netty 4.1.108

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated QPIDJMS-597:
---
Summary: Update to Netty 4.1.108  (was: Update to Netty 4.1.107)

> Update to Netty 4.1.108
> ---
>
> Key: QPIDJMS-597
> URL: https://issues.apache.org/jira/browse/QPIDJMS-597
> Project: Qpid JMS
>  Issue Type: Task
>  Components: qpid-jms-client
>        Reporter: Robbie Gemmell
>    Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.12.0, 2.6.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Reopened] (QPIDJMS-597) Update to Netty 4.1.107

[Robbie Gemmell (Jira)]

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

Robbie Gemmell reopened QPIDJMS-597:

  Assignee: Robbie Gemmell

> Update to Netty 4.1.107
> ---
>
> Key: QPIDJMS-597
> URL: https://issues.apache.org/jira/browse/QPIDJMS-597
> Project: Qpid JMS
>  Issue Type: Task
>  Components: qpid-jms-client
>        Reporter: Robbie Gemmell
>    Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.12.0, 2.6.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (QPIDJMS-598) update test dependencies

[Robbie Gemmell (Jira)]

Robbie Gemmell created QPIDJMS-598:
--

 Summary: update test dependencies
 Key: QPIDJMS-598
 URL: https://issues.apache.org/jira/browse/QPIDJMS-598
 Project: Qpid JMS
  Issue Type: Task
Reporter: Robbie Gemmell
 Fix For: 1.12.0, 2.6.0


update test dependencies



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (QPIDJMS-597) Update to Netty 4.1.107

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPIDJMS-597.

Resolution: Fixed

> Update to Netty 4.1.107
> ---
>
> Key: QPIDJMS-597
> URL: https://issues.apache.org/jira/browse/QPIDJMS-597
> Project: Qpid JMS
>  Issue Type: Task
>  Components: qpid-jms-client
>        Reporter: Robbie Gemmell
>Priority: Major
> Fix For: 1.12.0, 2.6.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (QPIDJMS-597) Update to Netty 4.1.107

[Robbie Gemmell (Jira)]

Robbie Gemmell created QPIDJMS-597:
--

 Summary: Update to Netty 4.1.107
 Key: QPIDJMS-597
 URL: https://issues.apache.org/jira/browse/QPIDJMS-597
 Project: Qpid JMS
  Issue Type: Task
  Components: qpid-jms-client
Reporter: Robbie Gemmell
 Fix For: 1.12.0, 2.6.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (QPID-8655) [Broker-J] Dependency updates for version 9.2.x

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated QPID-8655:
-
Summary: [Broker-J] Dependency updates for version 9.2.x  (was: [Broker-J] 
Dependency updates for version 9.1.x)

> [Broker-J] Dependency updates for version 9.2.x
> ---
>
> Key: QPID-8655
> URL: https://issues.apache.org/jira/browse/QPID-8655
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.2.0
>
>
> This Jira should serve for broker-j dependency updates for release 9.1.1
> Following dependencies are updated:
> *runtime dependencies*
> ch.qos.logback:logback-core 1.4.11 => 1.4.14
> ch.qos.logback:logback-classic 1.4.11 => 1.4.14
> com.fasterxml.jackson.core:jackson-core 2.15.3 => 2.16.1
> com.fasterxml.jackson.core:jackson-databind 2.15.3 => 2.16.1
> com.google.guava:guava 32.1.3-jre => 33.0.0-jre
> org.eclipse.jetty:jetty-server 11.0.18 => 11.0.19
> org.eclipse.jetty:jetty-servlet 11.0.18 => 11.0.19
> org.eclipse.jetty:jetty-servlets 11.0.18 => 11.0.19
> org.eclipse.jetty:jetty-rewrite 11.0.18 => 11.0.19
> org.eclipse.jetty.websocket:websocket-jetty-server 11.0.18 => 11.0.19
> de.siegmar:logback-gelf 3.0.0 => 5.0.1
> org.bouncycastle:bcprov-jdk18on 1.76 => 1.77
> org.bouncycastle:bcpkix-jdk18on 1.76 => 1.77
> org.slf4:slf4j-api 2.0.9 => 2.0.10
> *test dependencies*
> io.netty:netty-buffer 4.1.100.Final => 4.1.106.Final
> io.netty:netty-common 4.1.100.Final => 4.1.106.Final
> io.netty:netty-handler 4.1.100.Final => 4.1.106.Final
> io.netty:netty-transport 4.1.100.Final => 4.1.106.Final
> io.netty:netty-codec-http 4.1.100.Final => 4.1.106.Final
> org.mockito:mockito-core 5.7.0 => 5.9.0
> *maven plugins*
> org.codehaus.mojo:exec-maven-plugin 3.1.0 => 3.1.1



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: Java 17 Support for PooledConnectionFactory

[Robbie Gemmell]

Please ask questions on the users mailing list.

There are no 3.6.0 or 4.2.0 versions of the old AMQP 0-x qpid-client,
so I guess you are really referencing Camel versions there. Given that
and the rest of your mail, I think what you are more specifically
asking is really whether there are plans to support Jakarta Messaging
3.x (which is entirely independent from requiring Java 17, though some
projects have updated to both at the same time in their own releases)
for the old qpid-client. That client isnt really actively maintained
anymore, and there have been no discussion about such support, and the
old qpid-client is also only a JMS 1.1 provider anyway so it would
need a lot more than just package import renames, so I believe the
answer is no.

The newer AMQP 1.0 Qpid JMS client has had Jakarta Messaging 3.x
support since its 2.0.0 release in April 2022, current version is
2.5.0.

On Fri, 8 Dec 2023 at 22:18, Nimish Date  wrote:
>
> Hello Team,
>
> My current Camel application uses PooledConnectionFactory from
> org.apache.qpid.client (version 3.6.0). It also creates a JmsConfiguration
> object and sets the PooledConnectionFactory object into it.
> I'm planning to upgrade camel-jms and qpid-client to 4.2.0. I noticed that
> PooledConnectionFactory class in org.apache.qpid.client version 4.2.0 is
> using javax.jms.* and not jakarta.jms.*
> I wanted to know if there are any plans to support Java 17 for qpid-client
> version 4.2.0
>
> Appreciate all your efforts and hardwork.
>
> Thank You,
> ND

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

[jira] [Resolved] (QPID-8352) Official Docker image for Broker-J

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPID-8352.
--
Fix Version/s: qpid-java-broker-9.1.1
 Assignee: Daniil Kirilyuk
   Resolution: Fixed

> Official Docker image for Broker-J
> --
>
> Key: QPID-8352
> URL: https://issues.apache.org/jira/browse/QPID-8352
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Reporter: Chris O'Brien
>Assignee: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.1.1
>
>
> Currently there is no official Docker image for Broker-J.
> It would be great if one was provided, as there are more than a few people 
> interested in running Broker-J in a container, shown by the handful of 
> inflexible and un-maintained Dockerfiles/images for Broker-J floating around 
> GitHub/Docker Hub.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPIDJMS-595) update test dependencies

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPIDJMS-595.

  Assignee: Robbie Gemmell
Resolution: Fixed

> update test dependencies
> 
>
> Key: QPIDJMS-595
> URL: https://issues.apache.org/jira/browse/QPIDJMS-595
> Project: Qpid JMS
>  Issue Type: Task
>    Reporter: Robbie Gemmell
>        Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.11.0, 2.5.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (QPIDJMS-595) update test dependencies

[Robbie Gemmell (Jira)]

Robbie Gemmell created QPIDJMS-595:
--

 Summary: update test dependencies
 Key: QPIDJMS-595
 URL: https://issues.apache.org/jira/browse/QPIDJMS-595
 Project: Qpid JMS
  Issue Type: Task
Reporter: Robbie Gemmell
 Fix For: 1.11.0, 2.5.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (QPIDJMS-594) Update to Netty 4.1.100

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPIDJMS-594.

  Assignee: Robbie Gemmell
Resolution: Fixed

> Update to Netty 4.1.100
> ---
>
> Key: QPIDJMS-594
> URL: https://issues.apache.org/jira/browse/QPIDJMS-594
> Project: Qpid JMS
>  Issue Type: Task
>  Components: qpid-jms-client
>        Reporter: Robbie Gemmell
>    Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.11.0, 2.5.0
>
>
> Update to Netty 4.1.100



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (QPIDJMS-594) Update to Netty 4.1.100

[Robbie Gemmell (Jira)]

Robbie Gemmell created QPIDJMS-594:
--

 Summary: Update to Netty 4.1.100
 Key: QPIDJMS-594
 URL: https://issues.apache.org/jira/browse/QPIDJMS-594
 Project: Qpid JMS
  Issue Type: Task
  Components: qpid-jms-client
Reporter: Robbie Gemmell
 Fix For: 1.11.0, 2.5.0


Update to Netty 4.1.100



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2771) Update to Jacoco 0.8.10

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2771.

Resolution: Fixed

> Update to Jacoco 0.8.10
> ---
>
> Key: PROTON-2771
> URL: https://issues.apache.org/jira/browse/PROTON-2771
> Project: Qpid Proton
>  Issue Type: Task
>    Reporter: Robbie Gemmell
>        Assignee: Robbie Gemmell
>Priority: Major
> Fix For: proton-j-0.35.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (PROTON-2771) Update to Jacoco 0.8.10

[Robbie Gemmell (Jira)]

Robbie Gemmell created PROTON-2771:
--

 Summary: Update to Jacoco 0.8.10
 Key: PROTON-2771
 URL: https://issues.apache.org/jira/browse/PROTON-2771
 Project: Qpid Proton
  Issue Type: Task
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: proton-j-0.35.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (QPIDJMS-593) convert the tests to use JUnit 5

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPIDJMS-593.

Fix Version/s: 1.11.0
   Resolution: Fixed

> convert the tests to use JUnit 5
> 
>
> Key: QPIDJMS-593
> URL: https://issues.apache.org/jira/browse/QPIDJMS-593
> Project: Qpid JMS
>  Issue Type: Task
>    Reporter: Robbie Gemmell
>        Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.11.0, 2.5.0
>
>
> The tests currently use JUnit 4. Update things to convert them to use JUnit 5 
> 'Jupiter'.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (QPIDJMS-593) convert the tests to use JUnit 5

[Robbie Gemmell (Jira)]

Robbie Gemmell created QPIDJMS-593:
--

 Summary: convert the tests to use JUnit 5
 Key: QPIDJMS-593
 URL: https://issues.apache.org/jira/browse/QPIDJMS-593
 Project: Qpid JMS
  Issue Type: Task
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: 2.5.0


The tests currently use JUnit 4. Update things to convert them to use JUnit 5 
'Jupiter'.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: Qpid broker Logback dependency

[Robbie Gemmell]

Please use the users list for your questions going forward.

Since I am replying anyway...a 9.1.0 release is currently under vote
now which includes an upgrade for Logback (thread is on the users
list).

On Mon, 4 Sept 2023 at 17:32, Serhii Zhura  wrote:
>
> Hello.
>
> I'm using Qpid Broker (9.0.0) together with Spring Boot 3.
> From your side it is important to have Logback dependency with version
> 1.2.11 and from Spring Boot side it must be higher than 1.4.x. How can I
> deal with that? Can you upgrade the Logback version or can I do it myself
> to be comparable with your API? If I will you 1.4.x+ right now, I will get
> runtime error from your side which is connected with
> "org.apache.qpid.server.logging.logback.NoopConfigurator".
>
> Regards,
> Serhii Zhura
>
> --
> Disclaimer: This message (including any attachments) contains confidential
> information intended for a specific individual and purpose and is protected
> by law. If you are not the intended recipient, please let us know on
> operati...@panenco.com . You should delete
> this message and are hereby notified that any disclosure, copying, or
> distribution of this message, or the taking of any action based on it, is
> strictly prohibited.

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

[jira] [Resolved] (PROTON-2759) [python docs] auto_accept doc in TransactionalClientHandler is incorrect

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2759.

Fix Version/s: proton-c-0.40.0
   Resolution: Fixed

> [python docs] auto_accept doc in TransactionalClientHandler is incorrect
> 
>
> Key: PROTON-2759
> URL: https://issues.apache.org/jira/browse/PROTON-2759
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Reporter: Rakhi Kumari
>Assignee: Rakhi Kumari
>Priority: Major
> Fix For: proton-c-0.40.0
>
>
> The doc states auto_accept is True by default for Transactional Client, 
> and/but the code bits state otherwise (python/proton/_handlers.py).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: qpid-proton - Exception in send sample, in Win32

[Robbie Gemmell]

This is just a mailing list (with a web view for archival). You move
discussion to the other list by emailing the other list.

On Fri, 14 Jul 2023 at 09:54, Andrew North 
wrote:

> Just to update, we have experimented with other build options in Win32,
>
>
>
> We tried Release, RelWithDebInfo and RelMinSize – the exception does not
> occur here, and seems to work as expected, we see the messages in the
> broker,
>
>
>
> I was curious also if there is documentation to explain the state
> transitions inside the proactor class, or how to use the library without
> relying on it; currently I am referencing on the C API documentation,
>
>
>
> Additionally, I have created the same thread in the user forum, I’m not
> sure how these threads are moderated but can the discussion here be moved
> to there if its not too much hassle?
>
>- Link to that thread: qpid-proton - Exception in send sample, in
>Win32 - BUG?-Apache Mail Archives
><https://lists.apache.org/thread/fz7mpvoqydktwpcvd6ypt3b1kfkh9qvs>
>
>
>
>
> *From:* Jiri Daněk 
> *Sent:* Thursday, July 13, 2023 11:33 AM
> *To:* dev@qpid.apache.org
> *Subject:* Re: qpid-proton - Exception in send sample, in Win32
>
>
>
> Just a quick thought. The Proton CI is running only x64 builds. I must
> admit that I've almost forgotten that win32 exists, by now.
>
> (As it happened, I was privately told something about multiarch Linux
> packages yesterday, so it's not dead on Linux, either, yet.)
>
> Maybe 32bit is still helpful for embedded or low resource applications?
> Also, the address sanitizer prototype for visual studio first worked for
> win32 only.
>
> On Thu, Jul 13, 2023, 12:28 Robbie Gemmell 
> wrote:
>
> > Please use the users@ list for questions. The dev list is only used for
> > dev
> > traffic like JIRA updates etc, so other messages will often be
> overlooked.
> >
> > The lists strip essentially all attachments etc, so your images are not
> > present.
> >
> > On Thu, 13 Jul 2023 at 10:59, Andrew North <
> andrew.no...@campbellsci.co.uk
> > >
> > wrote:
> >
> > > Hello,
> > >
> > > I am seeking help on qpid-proton library, here is the description.
> > >
> > >
> > >
> > > - I cloned this repository: apache/qpid-proton: Mirror of Apache Qpid
> > > Proton (github.com) <https://github.com/apache/qpid-proton
> <https://protect-eu.mimecast.com/s/zkLbCV72pc10qzszJSDp?domain=github.com>
> >
> > > - On this commit hash: 4992b369a1b7aaa81913b4a5413616cf88d347bd
> > > (latest from master)
> > > - I built library including the examples in Win32
> > > - I tested the “send.c” example and get an exception in Win32; when I
> > > build in x64 the sample works fine
> > >
> > >
> > >
> > > Below are results of Win32 exception, let me know if there is any more
> > > information I need to provide with this investigation.
> > >
> > > I can also try to debug myself, but I would need some pointers to see
> > > where to look.
> > >
> > >
> > >
> > > Also let me know if this is the correct place to raise this issue, or
> if
> > > there is another more appropriate place.
> > >
> > >
> > >
> > > Callstack:
> > >
> > > e850fc45() Unknown
> > >
> > > [Frames below may be incorrect and/or missing]
> > >
> > > > qpid-proton-cored.dll!pni_phase(pn_transport_t *
> > transport,
> > > int(*)(pn_transport_t *, pn_endpoint_t *) phase) Line 2514 C
> > >
> > > qpid-proton-cored.dll!pni_process(pn_transport_t *
> > > transport) Line 2532 C
> > >
> > > qpid-proton-cored.dll!pn_output_write_amqp(pn_transport_t
> > *
> > > transport, unsigned int layer, char * bytes, unsigned int available)
> Line
> > > 2687 C
> > >
> > > qpid-proton-cored.dll!transport_produce(pn_transport_t *
> > > transport) Line 2740 C
> > >
> > > qpid-proton-cored.dll!pn_transport_pending(pn_transport_t
> > *
> > > transport) Line 3032 C
> > >
> > >
> > >
> >
> qpid-proton-cored.dll!pn_connection_driver_write_buffer(pn_connection_driver_t
> > > * d) Line 115 C
> > >
> > >
> > qpid-proton-proactord.dll!pconnection_process(pconnection_t
> > > * pc, pn_experimental::iocp_result_t * result, bool topup) Line 2361
> > C++
> > >
> > >
> > > qpid-proton-proactord.dll!pconnection_batch_next(pn_event_batch_t *
> > batch)
> > > Line 2417 C++
> > >
> > >
> > > qpid-proton-proactord.dll!pn_event_batch_next(pn_event_batch_t * batch)
> > > Line 84 C
> > >
> > > send.exe!run(app_data_t * app) Line 178 C
> > >
> > > send.exe!main(int argc, char * * argv) Line 205 C
> > >
> > > [External Code]
> > >
> > >
> > >
> > > Exception (screenshot):
> > >
> > >
> > >
> > >
> > >
> > > Kind Regards,
> > >
> > > Andrew
> > >
> > >
> >
>

Re: qpid-proton - Exception in send sample, in Win32

[Robbie Gemmell]

Please use the users@ list for questions. The dev list is only used for dev
traffic like JIRA updates etc, so other messages will often be overlooked.

The lists strip essentially all attachments etc, so your images are not
present.

On Thu, 13 Jul 2023 at 10:59, Andrew North 
wrote:

> Hello,
>
> I am seeking help on qpid-proton library, here is the description.
>
>
>
>- I cloned this repository: apache/qpid-proton: Mirror of Apache Qpid
>Proton (github.com) 
>   - On this commit hash: 4992b369a1b7aaa81913b4a5413616cf88d347bd
>   (latest from master)
>- I built library including the examples in Win32
>- I tested the “send.c” example and get an exception in Win32; when I
>build in x64 the sample works fine
>
>
>
> Below are results of Win32 exception, let me know if there is any more
> information I need to provide with this investigation.
>
> I can also try to debug myself, but I would need some pointers to see
> where to look.
>
>
>
> Also let me know if this is the correct place to raise this issue, or if
> there is another more appropriate place.
>
>
>
> Callstack:
>
> e850fc45()  Unknown
>
>[Frames below may be incorrect and/or missing]
>
> >  qpid-proton-cored.dll!pni_phase(pn_transport_t * transport,
> int(*)(pn_transport_t *, pn_endpoint_t *) phase) Line 2514C
>
>qpid-proton-cored.dll!pni_process(pn_transport_t *
> transport) Line 2532  C
>
>qpid-proton-cored.dll!pn_output_write_amqp(pn_transport_t *
> transport, unsigned int layer, char * bytes, unsigned int available) Line
> 2687  C
>
>qpid-proton-cored.dll!transport_produce(pn_transport_t *
> transport) Line 2740 C
>
>qpid-proton-cored.dll!pn_transport_pending(pn_transport_t *
> transport) Line 3032 C
>
>
> qpid-proton-cored.dll!pn_connection_driver_write_buffer(pn_connection_driver_t
> * d) Line 115 C
>
>qpid-proton-proactord.dll!pconnection_process(pconnection_t
> * pc, pn_experimental::iocp_result_t * result, bool topup) Line 2361C++
>
>
> qpid-proton-proactord.dll!pconnection_batch_next(pn_event_batch_t * batch)
> Line 2417  C++
>
>
> qpid-proton-proactord.dll!pn_event_batch_next(pn_event_batch_t * batch)
> Line 84 C
>
>send.exe!run(app_data_t * app) Line 178  C
>
>send.exe!main(int argc, char * * argv) Line 205   C
>
>[External Code]
>
>
>
> Exception (screenshot):
>
>
>
>
>
> Kind Regards,
>
> Andrew
>
>

[ANNOUNCE] Apache Qpid JMS 2.4.0 released

[Robbie Gemmell]

The Apache Qpid (https://qpid.apache.org) community is pleased to
announce the immediate availability of Apache Qpid JMS 2.4.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.4.0/release-notes.html

Thanks to all involved,
Robbie

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

[ANNOUNCE] Apache Qpid JMS 1.10.0 released

[Robbie Gemmell]

The Apache Qpid (https://qpid.apache.org) community is pleased to
announce the immediate availability of Apache Qpid JMS 1.10.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.10.0/release-notes.html

Thanks to all involved,
Robbie

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

[jira] [Assigned] (QPIDJMS-589) Update to maven-bundle-plugin 5.1.9

[Robbie Gemmell (Jira)]

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

Robbie Gemmell reassigned QPIDJMS-589:
--

Assignee: Robbie Gemmell

> Update to maven-bundle-plugin 5.1.9
> ---
>
> Key: QPIDJMS-589
> URL: https://issues.apache.org/jira/browse/QPIDJMS-589
> Project: Qpid JMS
>  Issue Type: Task
>    Reporter: Robbie Gemmell
>        Assignee: Robbie Gemmell
>Priority: Minor
> Fix For: 1.10.0, 2.4.0
>
>
> Update to maven-bundle-plugin 5.1.9



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (QPIDJMS-592) Update to apache parent pom 30

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPIDJMS-592.

Resolution: Fixed

> Update to apache parent pom 30
> --
>
> Key: QPIDJMS-592
> URL: https://issues.apache.org/jira/browse/QPIDJMS-592
> Project: Qpid JMS
>  Issue Type: Task
>    Reporter: Robbie Gemmell
>        Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.10.0, 2.4.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (QPIDJMS-592) Update to apache parent pom 30

[Robbie Gemmell (Jira)]

Robbie Gemmell created QPIDJMS-592:
--

 Summary: Update to apache parent pom 30
 Key: QPIDJMS-592
 URL: https://issues.apache.org/jira/browse/QPIDJMS-592
 Project: Qpid JMS
  Issue Type: Task
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: 1.10.0, 2.4.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (QPIDJMS-591) test dependency updates

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPIDJMS-591.

Resolution: Fixed

> test dependency updates
> ---
>
> Key: QPIDJMS-591
> URL: https://issues.apache.org/jira/browse/QPIDJMS-591
> Project: Qpid JMS
>  Issue Type: Task
>    Reporter: Robbie Gemmell
>        Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.10.0, 2.4.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (QPIDJMS-591) test dependency updates

[Robbie Gemmell (Jira)]

Robbie Gemmell created QPIDJMS-591:
--

 Summary: test dependency updates
 Key: QPIDJMS-591
 URL: https://issues.apache.org/jira/browse/QPIDJMS-591
 Project: Qpid JMS
  Issue Type: Task
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: 1.10.0, 2.4.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (QPIDJMS-590) Update to Netty 4.1.94

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated QPIDJMS-590:
---
Summary: Update to Netty 4.1.94  (was: Update to Netty 4.1.93)

> Update to Netty 4.1.94
> --
>
> Key: QPIDJMS-590
> URL: https://issues.apache.org/jira/browse/QPIDJMS-590
> Project: Qpid JMS
>  Issue Type: Task
>  Components: qpid-jms-client
>        Reporter: Robbie Gemmell
>    Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.10.0, 2.4.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Closed] (PROTON-2183) [cpp client] No messaging_handler callback for aborted messages

[Robbie Gemmell (Jira)]

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

Robbie Gemmell closed PROTON-2183.
--

> [cpp client] No messaging_handler callback for aborted messages
> ---
>
> Key: PROTON-2183
> URL: https://issues.apache.org/jira/browse/PROTON-2183
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Affects Versions: proton-c-0.30.0
>Reporter: Charles E. Rolke
>Assignee: Rakhi Kumari
>Priority: Major
> Fix For: proton-c-0.39.0
>
> Attachments: PROTON-2183-send-receive-console.log
>
>
> A cpp receiver throws "receiver read failure" when an aborted message is 
> received.
> A client based on:
> {{    class simple_recv : public proton::messaging_handler}}
> does not get called at (on_transport_error, on_connection_error, 
> on_session_error, on_sender_error, on_receiver_error, on_error). The 
> exception is thrown back to main() and the client application has no way to 
> intercept it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2648) 0.39.0 release tasks

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2648.

Resolution: Fixed

> 0.39.0 release tasks
> 
>
> Key: PROTON-2648
> URL: https://issues.apache.org/jira/browse/PROTON-2648
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-c, release
>        Reporter: Robbie Gemmell
>    Assignee: Robbie Gemmell
>Priority: Major
> Fix For: proton-c-0.39.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[ANNOUNCE] Apache Qpid Proton 0.39.0 released

[Robbie Gemmell]

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

Apache Qpid Proton is a messaging library for the Advanced Message
Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, https://www.amqp.org).
It can be used in a wide range of messaging applications including
brokers, clients, routers, bridges, proxies, and more.

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

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

Thanks to all involved,
Robbie

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

[jira] [Resolved] (PROTON-2742) The python binding installation instructions in python/PACKAGING.txt are wrong

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2742.

Fix Version/s: proton-c-0.40.0
 Assignee: Robbie Gemmell
   Resolution: Fixed

> The python binding installation instructions in python/PACKAGING.txt are wrong
> --
>
> Key: PROTON-2742
> URL: https://issues.apache.org/jira/browse/PROTON-2742
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Reporter: Ken Giusti
>    Assignee: Robbie Gemmell
>Priority: Trivial
> Fix For: proton-c-0.40.0
>
>
> The python/PACKAGING.txt file should probably just be deleted. The top-level 
> INSTALL.md file contains the correct installation instructions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (QPIDJMS-589) Update to maven-bundle-plugin 5.1.9

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPIDJMS-589.

Resolution: Fixed

> Update to maven-bundle-plugin 5.1.9
> ---
>
> Key: QPIDJMS-589
> URL: https://issues.apache.org/jira/browse/QPIDJMS-589
> Project: Qpid JMS
>  Issue Type: Task
>    Reporter: Robbie Gemmell
>Priority: Minor
> Fix For: 1.10.0, 2.4.0
>
>
> Update to maven-bundle-plugin 5.1.9



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (QPIDJMS-590) Update to Netty 4.1.93

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPIDJMS-590.

Resolution: Fixed

> Update to Netty 4.1.93
> --
>
> Key: QPIDJMS-590
> URL: https://issues.apache.org/jira/browse/QPIDJMS-590
> Project: Qpid JMS
>  Issue Type: Task
>  Components: qpid-jms-client
>        Reporter: Robbie Gemmell
>    Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.10.0, 2.4.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (QPIDJMS-589) Update to maven-bundle-plugin 5.1.9

[Robbie Gemmell (Jira)]

Robbie Gemmell created QPIDJMS-589:
--

 Summary: Update to maven-bundle-plugin 5.1.9
 Key: QPIDJMS-589
 URL: https://issues.apache.org/jira/browse/QPIDJMS-589
 Project: Qpid JMS
  Issue Type: Task
Reporter: Robbie Gemmell
 Fix For: 1.10.0, 2.4.0


Update to maven-bundle-plugin 5.1.9



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (QPIDJMS-590) Update to Netty 4.1.93

[Robbie Gemmell (Jira)]

Robbie Gemmell created QPIDJMS-590:
--

 Summary: Update to Netty 4.1.93
 Key: QPIDJMS-590
 URL: https://issues.apache.org/jira/browse/QPIDJMS-590
 Project: Qpid JMS
  Issue Type: Task
  Components: qpid-jms-client
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: 1.10.0, 2.4.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[ANNOUNCE] Apache Qpid JMS 2.3.0 released

[Robbie Gemmell]

The Apache Qpid (https://qpid.apache.org) community is pleased to
announce the immediate availability of Apache Qpid JMS 2.3.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.3.0/release-notes.html

Thanks to all involved,
Robbie

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

[ANNOUNCE] Apache Qpid JMS 1.9.0 released

[Robbie Gemmell]

The Apache Qpid (https://qpid.apache.org) community is pleased to
announce the immediate availability of Apache Qpid JMS 1.9.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.9.0/release-notes.html

Thanks to all involved,
Robbie

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

[jira] [Updated] (QPIDJMS-583) Update to Netty 4.1.92

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated QPIDJMS-583:
---
Summary: Update to Netty 4.1.92  (was: Update to Netty 4.1.87)

> Update to Netty 4.1.92
> --
>
> Key: QPIDJMS-583
> URL: https://issues.apache.org/jira/browse/QPIDJMS-583
> Project: Qpid JMS
>  Issue Type: Task
>  Components: qpid-jms-client
>        Reporter: Robbie Gemmell
>    Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.9.0, 2.3.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (QPIDJMS-588) failover URI with invalid/unused user-info in component URI not rejected, can be logged

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPIDJMS-588.

Resolution: Fixed

> failover URI with invalid/unused user-info in component URI not rejected, can 
> be logged
> ---
>
> Key: QPIDJMS-588
> URL: https://issues.apache.org/jira/browse/QPIDJMS-588
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 1.8.0, 2.2.0
> Environment: We are currently using Apache Qpid 2.2.0
>Reporter: Patrick Gell
>Assignee: Robbie Gemmell
>Priority: Minor
>  Labels: password, security
> Fix For: 1.9.0, 2.3.0
>
>
> The clients documented connection URI config does not utilise user-info 
> details from the URI, with it actively refusing its presence in the base 
> non-failover connection URI, for example using 
> "amqp://erroneous-user:erroneous-pass@localhost:5672" will result in an 
> IllegalArgumentException when creating the connection factory.
> If however a failover URI is supplied with a component server connection URI 
> nested within it erroneously containing user-info detail, e.g 
> "failover:(amqp://erroneous-user:erroneous-pass@localhost:5672)", then they 
> remain invalid/unused as expected but do not currently result in the 
> IllegalArgumentException as in the non-failover case. Later code within the 
> client does not expect this invalid/unused user-info detail to be present, 
> and so can then log it.
> The erroneous presence of the invalid/unused user-info within a component of 
> a failover URI should also cause an IllegalArgumentException when creating 
> the connection factory.
>  
> 
> Original Description:
> If I have a failover URL with `user:password` configured than the password is 
> logged in plain text.
> {+}BrokerURL{+}: 
> failover:(amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672)
> +Log extract:+
> 2023-05-15 13:04:42.484  INFO [localhost:5672]] 
> org.apache.qpid.jms.JmsConnection        : Connection 
> ID:83323730-746c-4430-988f-e9e5f699dc1c:1 connected to server: 
> amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672
>  
> Expected behaviour:
> The password is masked in the log or an IllegalArgumentException is thrown 
> similar to the non failover URL:
> amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672 results in a 
> ...
> Caused by: java.lang.IllegalArgumentException: The supplied URI cannot 
> contain a User-Info section
>     at 
> org.apache.qpid.jms.JmsConnectionFactory.setRemoteURI(JmsConnectionFactory.java:406)
>     at 
> org.amqphub.spring.boot.jms.autoconfigure.AMQP10JMSConnectionFactoryFactory.createConnectionFactory(AMQP10JMSConnectionFactoryFactory.java:66)
>     ... 69 common frames omitted
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Assigned] (QPIDJMS-588) failover URI with invalid/unused user-info in component URI not rejected, can be logged

[Robbie Gemmell (Jira)]

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

Robbie Gemmell reassigned QPIDJMS-588:
--

Fix Version/s: 1.9.0
   2.3.0
Affects Version/s: 1.8.0
 Assignee: Robbie Gemmell

> failover URI with invalid/unused user-info in component URI not rejected, can 
> be logged
> ---
>
> Key: QPIDJMS-588
> URL: https://issues.apache.org/jira/browse/QPIDJMS-588
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 1.8.0, 2.2.0
> Environment: We are currently using Apache Qpid 2.2.0
>Reporter: Patrick Gell
>Assignee: Robbie Gemmell
>Priority: Minor
>  Labels: password, security
> Fix For: 1.9.0, 2.3.0
>
>
> The clients documented connection URI config does not utilise user-info 
> details from the URI, with it actively refusing its presence in the base 
> non-failover connection URI, for example using 
> "amqp://erroneous-user:erroneous-pass@localhost:5672" will result in an 
> IllegalArgumentException when creating the connection factory.
> If however a failover URI is supplied with a component server connection URI 
> nested within it erroneously containing user-info detail, e.g 
> "failover:(amqp://erroneous-user:erroneous-pass@localhost:5672)", then they 
> remain invalid/unused as expected but do not currently result in the 
> IllegalArgumentException as in the non-failover case. Later code within the 
> client does not expect this invalid/unused user-info detail to be present, 
> and so can then log it.
> The erroneous presence of the invalid/unused user-info within a component of 
> a failover URI should also cause an IllegalArgumentException when creating 
> the connection factory.
>  
> 
> Original Description:
> If I have a failover URL with `user:password` configured than the password is 
> logged in plain text.
> {+}BrokerURL{+}: 
> failover:(amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672)
> +Log extract:+
> 2023-05-15 13:04:42.484  INFO [localhost:5672]] 
> org.apache.qpid.jms.JmsConnection        : Connection 
> ID:83323730-746c-4430-988f-e9e5f699dc1c:1 connected to server: 
> amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672
>  
> Expected behaviour:
> The password is masked in the log or an IllegalArgumentException is thrown 
> similar to the non failover URL:
> amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672 results in a 
> ...
> Caused by: java.lang.IllegalArgumentException: The supplied URI cannot 
> contain a User-Info section
>     at 
> org.apache.qpid.jms.JmsConnectionFactory.setRemoteURI(JmsConnectionFactory.java:406)
>     at 
> org.amqphub.spring.boot.jms.autoconfigure.AMQP10JMSConnectionFactoryFactory.createConnectionFactory(AMQP10JMSConnectionFactoryFactory.java:66)
>     ... 69 common frames omitted
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (QPIDJMS-588) failover URI with invalid/unused user-info in component URI not rejected, can be logged

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated QPIDJMS-588:
---
Description: 
The clients documented connection URI config does not utilise user-info details 
from the URI, with it actively refusing its presence in the base non-failover 
connection URI, for example using 
"amqp://erroneous-user:erroneous-pass@localhost:5672" will result in an 
IllegalArgumentException when creating the connection factory.

If however a failover URI is supplied with a component server connection URI 
nested within it erroneously containing user-info detail, e.g 
"failover:(amqp://erroneous-user:erroneous-pass@localhost:5672)", then they 
remain invalid/unused as expected but do not currently result in the 
IllegalArgumentException as in the non-failover case. Later code within the 
client does not expect this invalid/unused user-info detail to be present, and 
so can then log it.

The erroneous presence of the invalid/unused user-info within a component of a 
failover URI should also cause an IllegalArgumentException when creating the 
connection factory.

 



Original Description:

If I have a failover URL with `user:password` configured than the password is 
logged in plain text.

{+}BrokerURL{+}: 
failover:(amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672)

+Log extract:+
2023-05-15 13:04:42.484  INFO [localhost:5672]] 
org.apache.qpid.jms.JmsConnection        : Connection 
ID:83323730-746c-4430-988f-e9e5f699dc1c:1 connected to server: 
amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672

 

Expected behaviour:

The password is masked in the log or an IllegalArgumentException is thrown 
similar to the non failover URL:

amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672 results in a 

...

Caused by: java.lang.IllegalArgumentException: The supplied URI cannot contain 
a User-Info section
    at 
org.apache.qpid.jms.JmsConnectionFactory.setRemoteURI(JmsConnectionFactory.java:406)
    at 
org.amqphub.spring.boot.jms.autoconfigure.AMQP10JMSConnectionFactoryFactory.createConnectionFactory(AMQP10JMSConnectionFactoryFactory.java:66)
    ... 69 common frames omitted

 

  was:
If I have a failover URL with `user:password` configured than the password is 
logged in plain text.


{+}BrokerURL{+}: 
failover:(amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672)


+Log extract:+
2023-05-15 13:04:42.484  INFO [localhost:5672]] 
org.apache.qpid.jms.JmsConnection        : Connection 
ID:83323730-746c-4430-988f-e9e5f699dc1c:1 connected to server: 
amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672

 

Expected behaviour:

The password is masked in the log or an IllegalArgumentException is thrown 
similar to the non failover URL:

amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672 results in a 

...

Caused by: java.lang.IllegalArgumentException: The supplied URI cannot contain 
a User-Info section
    at 
org.apache.qpid.jms.JmsConnectionFactory.setRemoteURI(JmsConnectionFactory.java:406)
    at 
org.amqphub.spring.boot.jms.autoconfigure.AMQP10JMSConnectionFactoryFactory.createConnectionFactory(AMQP10JMSConnectionFactoryFactory.java:66)
    ... 69 common frames omitted

 

Summary: failover URI with invalid/unused user-info in component URI 
not rejected, can be logged  (was: when invalid failover URI supplied, password 
can be present in log file)

> failover URI with invalid/unused user-info in component URI not rejected, can 
> be logged
> ---
>
> Key: QPIDJMS-588
> URL: https://issues.apache.org/jira/browse/QPIDJMS-588
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 2.2.0
> Environment: We are currently using Apache Qpid 2.2.0
>Reporter: Patrick Gell
>Priority: Minor
>  Labels: password, security
>
> The clients documented connection URI config does not utilise user-info 
> details from the URI, with it actively refusing its presence in the base 
> non-failover connection URI, for example using 
> "amqp://erroneous-user:erroneous-pass@localhost:5672" will result in an 
> IllegalArgumentException when creating the connection factory.
> If however a failover URI is supplied with a component server connection URI 
> nested within it erroneously containing user-info detail, e.g 
> "failover:(amqp://erroneous-user:erroneous-pass@localhost:5672)", then they 
> remain invalid/unused as expected but do not currently result in the 
> IllegalArgumentException as in the non-failover case. Later code within the 
> client does not expect this invalid/unused user

[jira] [Closed] (QPIDJMS-587) io.netty:netty-transport-native-unix-common not managed but used

[Robbie Gemmell (Jira)]

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

Robbie Gemmell closed QPIDJMS-587.
--
Fix Version/s: (was: 2.3.0)
   Resolution: Not A Bug

> io.netty:netty-transport-native-unix-common not managed but used
> 
>
> Key: QPIDJMS-587
> URL: https://issues.apache.org/jira/browse/QPIDJMS-587
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client, qpid-jms-discovery
>Affects Versions: 2.2.0
> Environment: linux OS running a Spring Boot app 2.7.11 and qpid-jms 
> 2.2.0 together.
>Reporter: Harald Aamot
>Priority: Major
> Attachments: image-2023-04-28-12-03-00-922.png, 
> image-2023-04-28-12-03-40-683.png
>
>
> When using qpid-jms 2.2.0 running on a linux OS then netty transitively pulls 
> in io.netty:netty-transport-native-unix-common .
> The version for this depndency is not managed in qpid-jms.
> When running a SpringBoot 2.7.11 application, Spring Boot manages io.netty on 
> version 4.1.91.Final . This version then gets used for 
> io.netty:netty-transport-native-unix-common, while the other netty components 
> run on 4.1.86.Final (managed by qpid-jms).
> This leads to a runtime exception when trying to connect.
> Reason is this:
> With netty 4.1.91.Final an incompatible change for qpid-jms has been made.
> Changelog [https://netty.io/news/2023/04/03/4-1-91-Final.html]
> incompatible change [https://github.com/netty/netty/issues/13317]
> code changed there [https://github.com/netty/netty/pull/13318]
> {noformat}
> ["jakarta.jms.JMSException: Could not initialize class 
> io.netty.channel.unix.Errors","
>   at 
> org.apache.qpid.jms.provider.ProviderException.toJMSException(ProviderException.java:34)","
>   at 
> org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:80)","
>   at 
> org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:112)","
>   at 
> org.apache.qpid.jms.JmsConnection.onAsyncException(JmsConnection.java:1564)","
>   at 
> org.apache.qpid.jms.JmsConnection.onProviderException(JmsConnection.java:1548)","
>   at 
> org.apache.qpid.jms.JmsConnection.onConnectionFailure(JmsConnection.java:1392)","
>   at 
> org.apache.qpid.jms.provider.failover.FailoverProvider.lambda$reportReconnectFailure$3(FailoverProvider.java:808)","
>   at 
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown 
> Source)","
>   at java.base/java.util.concurrent.FutureTask.run(Unknown Source)","
>   at 
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
>  Source)","
>   at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown 
> Source)","
>   at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown 
> Source)","
>   at java.base/java.lang.Thread.run(Unknown Source)","Caused by: 
> org.apache.qpid.jms.provider.exceptions.ProviderIOException: Could not 
> initialize class io.netty.channel.unix.Errors","
>   at 
> org.apache.qpid.jms.provider.exceptions.ProviderExceptionSupport.createOrPassthroughFatal(ProviderExceptionSupport.java:46)","
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider.connect(AmqpProvider.java:309)","
>   at 
> org.apache.qpid.jms.provider.failover.FailoverProvider$14.run(FailoverProvider.java:747)","
>   ... 6 more","Caused by: java.io.IOException: Could not initialize class 
> io.netty.channel.unix.Errors","
>   at 
> org.apache.qpid.jms.util.IOExceptionSupport.create(IOExceptionSupport.java:45)","
>   at 
> org.apache.qpid.jms.transports.netty.NettyTcpTransport$2.operationComplete(NettyTcpTransport.java:176)","
>   at 
> org.apache.qpid.jms.transports.netty.NettyTcpTransport$2.operationComplete(NettyTcpTransport.java:171)","
>   at 
> io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:590)","
>   at 
> io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:557)","
>   at 
> io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:492)","
>   at 
> io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:636)","
>   

[jira] [Reopened] (QPIDJMS-587) io.netty:netty-transport-native-unix-common not managed but used

[Robbie Gemmell (Jira)]

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

Robbie Gemmell reopened QPIDJMS-587:


> io.netty:netty-transport-native-unix-common not managed but used
> 
>
> Key: QPIDJMS-587
> URL: https://issues.apache.org/jira/browse/QPIDJMS-587
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client, qpid-jms-discovery
>Affects Versions: 2.2.0
> Environment: linux OS running a Spring Boot app 2.7.11 and qpid-jms 
> 2.2.0 together.
>Reporter: Harald Aamot
>Priority: Major
> Fix For: 2.3.0
>
> Attachments: image-2023-04-28-12-03-00-922.png, 
> image-2023-04-28-12-03-40-683.png
>
>
> When using qpid-jms 2.2.0 running on a linux OS then netty transitively pulls 
> in io.netty:netty-transport-native-unix-common .
> The version for this depndency is not managed in qpid-jms.
> When running a SpringBoot 2.7.11 application, Spring Boot manages io.netty on 
> version 4.1.91.Final . This version then gets used for 
> io.netty:netty-transport-native-unix-common, while the other netty components 
> run on 4.1.86.Final (managed by qpid-jms).
> This leads to a runtime exception when trying to connect.
> Reason is this:
> With netty 4.1.91.Final an incompatible change for qpid-jms has been made.
> Changelog [https://netty.io/news/2023/04/03/4-1-91-Final.html]
> incompatible change [https://github.com/netty/netty/issues/13317]
> code changed there [https://github.com/netty/netty/pull/13318]
> {noformat}
> ["jakarta.jms.JMSException: Could not initialize class 
> io.netty.channel.unix.Errors","
>   at 
> org.apache.qpid.jms.provider.ProviderException.toJMSException(ProviderException.java:34)","
>   at 
> org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:80)","
>   at 
> org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:112)","
>   at 
> org.apache.qpid.jms.JmsConnection.onAsyncException(JmsConnection.java:1564)","
>   at 
> org.apache.qpid.jms.JmsConnection.onProviderException(JmsConnection.java:1548)","
>   at 
> org.apache.qpid.jms.JmsConnection.onConnectionFailure(JmsConnection.java:1392)","
>   at 
> org.apache.qpid.jms.provider.failover.FailoverProvider.lambda$reportReconnectFailure$3(FailoverProvider.java:808)","
>   at 
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown 
> Source)","
>   at java.base/java.util.concurrent.FutureTask.run(Unknown Source)","
>   at 
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
>  Source)","
>   at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown 
> Source)","
>   at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown 
> Source)","
>   at java.base/java.lang.Thread.run(Unknown Source)","Caused by: 
> org.apache.qpid.jms.provider.exceptions.ProviderIOException: Could not 
> initialize class io.netty.channel.unix.Errors","
>   at 
> org.apache.qpid.jms.provider.exceptions.ProviderExceptionSupport.createOrPassthroughFatal(ProviderExceptionSupport.java:46)","
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider.connect(AmqpProvider.java:309)","
>   at 
> org.apache.qpid.jms.provider.failover.FailoverProvider$14.run(FailoverProvider.java:747)","
>   ... 6 more","Caused by: java.io.IOException: Could not initialize class 
> io.netty.channel.unix.Errors","
>   at 
> org.apache.qpid.jms.util.IOExceptionSupport.create(IOExceptionSupport.java:45)","
>   at 
> org.apache.qpid.jms.transports.netty.NettyTcpTransport$2.operationComplete(NettyTcpTransport.java:176)","
>   at 
> org.apache.qpid.jms.transports.netty.NettyTcpTransport$2.operationComplete(NettyTcpTransport.java:171)","
>   at 
> io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:590)","
>   at 
> io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:557)","
>   at 
> io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:492)","
>   at 
> io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:636)","
>   at 
> io.netty.util.concurrent.DefaultPromise.setFailure0(De

[jira] [Commented] (QPIDJMS-588) when invalid failover URI supplied, password can be present in log file

[Robbie Gemmell (Jira)]

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

Robbie Gemmell commented on QPIDJMS-588:


It should throw an IllegalArgumentException as it already does in the 
regular/non-failover URI case, since the userinfo presence is not considered 
valid and will not be used.

I already have a change mostly done for this, just still to give it a check 
over and tidyup before pushing.

> when invalid failover URI supplied, password can be present in log file
> ---
>
> Key: QPIDJMS-588
> URL: https://issues.apache.org/jira/browse/QPIDJMS-588
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 2.2.0
> Environment: We are currently using Apache Qpid 2.2.0
>Reporter: Patrick Gell
>Priority: Minor
>  Labels: password, security
>
> If I have a failover URL with `user:password` configured than the password is 
> logged in plain text.
> {+}BrokerURL{+}: 
> failover:(amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672)
> +Log extract:+
> 2023-05-15 13:04:42.484  INFO [localhost:5672]] 
> org.apache.qpid.jms.JmsConnection        : Connection 
> ID:83323730-746c-4430-988f-e9e5f699dc1c:1 connected to server: 
> amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672
>  
> Expected behaviour:
> The password is masked in the log or an IllegalArgumentException is thrown 
> similar to the non failover URL:
> amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672 results in a 
> ...
> Caused by: java.lang.IllegalArgumentException: The supplied URI cannot 
> contain a User-Info section
>     at 
> org.apache.qpid.jms.JmsConnectionFactory.setRemoteURI(JmsConnectionFactory.java:406)
>     at 
> org.amqphub.spring.boot.jms.autoconfigure.AMQP10JMSConnectionFactoryFactory.createConnectionFactory(AMQP10JMSConnectionFactoryFactory.java:66)
>     ... 69 common frames omitted
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Commented] (QPIDJMS-588) when invalid failover URI supplied, password can be present in log file

[Robbie Gemmell (Jira)]

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

Robbie Gemmell commented on QPIDJMS-588:


This presumably happens because the code in the ConnectionFactory which 
normally rejects the invalid presence of userinfo detail in the base URI, 
doesnt apply to failover URIs which are instead handled later by the failover 
provider to extract individual server details, which presumably isnt enforcing 
the same check for invalid presence of userinfo detail in the base URI. The 
later created Connection then doesnt anticipate userinfo being present in its 
base URI since it is not considered valid to be there in the client URI, and it 
then logs the base URI (first stripping the query, that might have had user 
detail props contained). For now: remove the invalid userinfo detail from your 
URI, it isnt being used from there anyway.

> when invalid failover URI supplied, password can be present in log file
> ---
>
> Key: QPIDJMS-588
> URL: https://issues.apache.org/jira/browse/QPIDJMS-588
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 2.2.0
> Environment: We are currently using Apache Qpid 2.2.0
>Reporter: Patrick Gell
>Priority: Minor
>  Labels: password, security
>
> If I have a failover URL with `user:password` configured than the password is 
> logged in plain text.
> {+}BrokerURL{+}: 
> failover:(amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672)
> +Log extract:+
> 2023-05-15 13:04:42.484  INFO [localhost:5672]] 
> org.apache.qpid.jms.JmsConnection        : Connection 
> ID:83323730-746c-4430-988f-e9e5f699dc1c:1 connected to server: 
> amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672
>  
> Expected behaviour:
> The password is masked in the log or an IllegalArgumentException is thrown 
> similar to the non failover URL:
> amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672 results in a 
> ...
> Caused by: java.lang.IllegalArgumentException: The supplied URI cannot 
> contain a User-Info section
>     at 
> org.apache.qpid.jms.JmsConnectionFactory.setRemoteURI(JmsConnectionFactory.java:406)
>     at 
> org.amqphub.spring.boot.jms.autoconfigure.AMQP10JMSConnectionFactoryFactory.createConnectionFactory(AMQP10JMSConnectionFactoryFactory.java:66)
>     ... 69 common frames omitted
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (QPIDJMS-588) when invalid failover URI supplied, password can be present in log file

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated QPIDJMS-588:
---
Priority: Minor  (was: Major)
 Summary: when invalid failover URI supplied, password can be present in 
log file  (was: Disclosure of broker password in log file)

> when invalid failover URI supplied, password can be present in log file
> ---
>
> Key: QPIDJMS-588
> URL: https://issues.apache.org/jira/browse/QPIDJMS-588
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 2.2.0
> Environment: We are currently using Apache Qpid 2.2.0
>Reporter: Patrick Gell
>Priority: Minor
>  Labels: password, security
>
> If I have a failover URL with `user:password` configured than the password is 
> logged in plain text.
> {+}BrokerURL{+}: 
> failover:(amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672)
> +Log extract:+
> 2023-05-15 13:04:42.484  INFO [localhost:5672]] 
> org.apache.qpid.jms.JmsConnection        : Connection 
> ID:83323730-746c-4430-988f-e9e5f699dc1c:1 connected to server: 
> amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672
>  
> Expected behaviour:
> The password is masked in the log or an IllegalArgumentException is thrown 
> similar to the non failover URL:
> amqp://{*}myactivemquser:my-secure-password{*}@localhost:5672 results in a 
> ...
> Caused by: java.lang.IllegalArgumentException: The supplied URI cannot 
> contain a User-Info section
>     at 
> org.apache.qpid.jms.JmsConnectionFactory.setRemoteURI(JmsConnectionFactory.java:406)
>     at 
> org.amqphub.spring.boot.jms.autoconfigure.AMQP10JMSConnectionFactoryFactory.createConnectionFactory(AMQP10JMSConnectionFactoryFactory.java:66)
>     ... 69 common frames omitted
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Commented] (PROTON-2720) [proton-dotnet] virtual host connection option not applied correctly

[Robbie Gemmell (Jira)]

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

Robbie Gemmell commented on PROTON-2720:


The fixing commit was tagged with PROTON-2719 by mistake:

 {quote}
Commit 79fe183edc3f27e919868bb71094c4607b9276e7 in qpid-proton-dotnet's branch 
refs/heads/main from Timothy Bish
[ https://gitbox.apache.org/repos/asf?p=qpid-proton-dotnet.git;h=79fe183 ]

PROTON-2719 Ensure configured virtual host value is sent to the remote

The connection options virtual host should be used to override the
value set for the connection host or to omit a value if empty string
is provided. The host option should be applied both to the Open
performative and to the SASLInit performative consistently.
 {quote}
 

> [proton-dotnet] virtual host connection option not applied correctly
> 
>
> Key: PROTON-2720
> URL: https://issues.apache.org/jira/browse/PROTON-2720
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-dotnet
>Affects Versions: proton-dotnet-1.0.0-M7
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: proton-dotnet-1.0.0-M8
>
>
> Setting the connection option for virtual host not applied correctly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Commented] (PROTON-2719) [protonj2] virtual host connection option not applied correctly

[Robbie Gemmell (Jira)]

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

Robbie Gemmell commented on PROTON-2719:


2nd commit was meant for PROTON-2720.

> [protonj2] virtual host connection option not applied correctly
> ---
>
> Key: PROTON-2719
> URL: https://issues.apache.org/jira/browse/PROTON-2719
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: protonj2
>Affects Versions: protonj2-1.0.0-M14
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Minor
> Fix For: protonj2-1.0.0-M15
>
>
> The client does not correctly apply the virtual host option from the 
> ConnectionOptions



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Comment Edited] (QPIDJMS-587) io.netty:netty-transport-native-unix-common not managed but used

[Robbie Gemmell (Jira)]

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

Robbie Gemmell edited comment on QPIDJMS-587 at 5/2/23 10:05 AM:
-

I was not asking you to give any of the tree. Just noting that giving an 
isolated snippet as you did is not particularly interpretable without full 
context. Even the added detail you gave, isnt sufficient to fully analyse the 
snippet...though it does actually point to your application not doing only what 
you described.

We wont be removing dependency management within the client itself. It shouldnt 
even matter if we did, particularly so in the example you just described.

Your applications netty dependency version selection is not behaving at all the 
way I would expect, or have just locally tested out to verify, when inheriting 
dependencyManagement via netty-bom from the spring-boot-dependencies pom/bom 
via one of their parents, such as e.g their 
[suggested|https://docs.spring.io/spring-boot/docs/2.7.11/reference/html/getting-started.html#getting-started.first-application.pom]
 spring-boot-starter-parent, and then declaring a simple dependency on the 
client within the same application pom.

That inherited netty-bom dependencyManagement should still be overriding any 
client-defined netty versions, regardless of whether any client used module is 
dependency managed in the client or not, unless something else is overriding 
that inherited management with some other selection criteria in the application 
pom. Given you indicated changing qpid-jms management had any effect here, 
which it shouldn'tare you importing the qpid-jms-parent pom in the 
application dependencyManagement or something strange like that?


was (Author: gemmellr):
I was not asking you to give any of the tree. Just noting that giving an 
isolated snippet as you did is not particularly interpretable without full 
context. Even the added detail you gave, isnt sufficient to fully analyse the 
snippet...though it does actually point to your application not doing only what 
you described.

We wont be removing dependency management within the client itself. It shouldnt 
even matter if we did, particularly so in the example you just described.

Your applications netty dependency version selection is not behaving at all the 
way I would expect, or have just locally tested out to verify, when inheriting 
dependencyManagement via netty-bom from the spring-boot-dependencies pom/bom 
via one of their parents, such as e.g their 
[https://docs.spring.io/spring-boot/docs/2.7.11/reference/html/getting-started.html#getting-started.first-application.pom|suggested]
  spring-boot-starter-parent, and then declaring a simple dependency on the 
client within the same application pom.

That inherited netty-bom dependencyManagement should still be overriding any 
client-defined netty versions, regardless of whether any client used module is 
dependency managed in the client or not, unless something else is overriding 
that inherited management with some other selection criteria in the application 
pom. Given you indicated changing qpid-jms management had any effect here, 
which it shouldn'tare you importing the qpid-jms-parent pom in the 
application dependencyManagement or something strange like that?

> io.netty:netty-transport-native-unix-common not managed but used
> 
>
> Key: QPIDJMS-587
> URL: https://issues.apache.org/jira/browse/QPIDJMS-587
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client, qpid-jms-discovery
>Affects Versions: 2.2.0
> Environment: linux OS running a Spring Boot app 2.7.11 and qpid-jms 
> 2.2.0 together.
>Reporter: Harald Aamot
>Priority: Major
> Fix For: 2.3.0
>
> Attachments: image-2023-04-28-12-03-00-922.png, 
> image-2023-04-28-12-03-40-683.png
>
>
> When using qpid-jms 2.2.0 running on a linux OS then netty transitively pulls 
> in io.netty:netty-transport-native-unix-common .
> The version for this depndency is not managed in qpid-jms.
> When running a SpringBoot 2.7.11 application, Spring Boot manages io.netty on 
> version 4.1.91.Final . This version then gets used for 
> io.netty:netty-transport-native-unix-common, while the other netty components 
> run on 4.1.86.Final (managed by qpid-jms).
> This leads to a runtime exception when trying to connect.
> Reason is this:
> With netty 4.1.91.Final an incompatible change for qpid-jms has been made.
> Changelog [https://netty.io/news/2023/04/03/4-1-91-Final.html]
> incompatible change [https://github.com/netty/netty/issues/13317]
> code changed there [https://github.c

[jira] [Commented] (QPIDJMS-587) io.netty:netty-transport-native-unix-common not managed but used

[Robbie Gemmell (Jira)]

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

Robbie Gemmell commented on QPIDJMS-587:


I was not asking you to give any of the tree. Just noting that giving an 
isolated snippet as you did is not particularly interpretable without full 
context. Even the added detail you gave, isnt sufficient to fully analyse the 
snippet...though it does actually point to your application not doing only what 
you described.

We wont be removing dependency management within the client itself. It shouldnt 
even matter if we did, particularly so in the example you just described.

Your applications netty dependency version selection is not behaving at all the 
way I would expect, or have just locally tested out to verify, when inheriting 
dependencyManagement via netty-bom from the spring-boot-dependencies pom/bom 
via one of their parents, such as e.g their 
[https://docs.spring.io/spring-boot/docs/2.7.11/reference/html/getting-started.html#getting-started.first-application.pom|suggested]
  spring-boot-starter-parent, and then declaring a simple dependency on the 
client within the same application pom.

That inherited netty-bom dependencyManagement should still be overriding any 
client-defined netty versions, regardless of whether any client used module is 
dependency managed in the client or not, unless something else is overriding 
that inherited management with some other selection criteria in the application 
pom. Given you indicated changing qpid-jms management had any effect here, 
which it shouldn'tare you importing the qpid-jms-parent pom in the 
application dependencyManagement or something strange like that?

> io.netty:netty-transport-native-unix-common not managed but used
> 
>
> Key: QPIDJMS-587
> URL: https://issues.apache.org/jira/browse/QPIDJMS-587
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client, qpid-jms-discovery
>Affects Versions: 2.2.0
> Environment: linux OS running a Spring Boot app 2.7.11 and qpid-jms 
> 2.2.0 together.
>Reporter: Harald Aamot
>Priority: Major
> Fix For: 2.3.0
>
> Attachments: image-2023-04-28-12-03-00-922.png, 
> image-2023-04-28-12-03-40-683.png
>
>
> When using qpid-jms 2.2.0 running on a linux OS then netty transitively pulls 
> in io.netty:netty-transport-native-unix-common .
> The version for this depndency is not managed in qpid-jms.
> When running a SpringBoot 2.7.11 application, Spring Boot manages io.netty on 
> version 4.1.91.Final . This version then gets used for 
> io.netty:netty-transport-native-unix-common, while the other netty components 
> run on 4.1.86.Final (managed by qpid-jms).
> This leads to a runtime exception when trying to connect.
> Reason is this:
> With netty 4.1.91.Final an incompatible change for qpid-jms has been made.
> Changelog [https://netty.io/news/2023/04/03/4-1-91-Final.html]
> incompatible change [https://github.com/netty/netty/issues/13317]
> code changed there [https://github.com/netty/netty/pull/13318]
> {noformat}
> ["jakarta.jms.JMSException: Could not initialize class 
> io.netty.channel.unix.Errors","
>   at 
> org.apache.qpid.jms.provider.ProviderException.toJMSException(ProviderException.java:34)","
>   at 
> org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:80)","
>   at 
> org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:112)","
>   at 
> org.apache.qpid.jms.JmsConnection.onAsyncException(JmsConnection.java:1564)","
>   at 
> org.apache.qpid.jms.JmsConnection.onProviderException(JmsConnection.java:1548)","
>   at 
> org.apache.qpid.jms.JmsConnection.onConnectionFailure(JmsConnection.java:1392)","
>   at 
> org.apache.qpid.jms.provider.failover.FailoverProvider.lambda$reportReconnectFailure$3(FailoverProvider.java:808)","
>   at 
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown 
> Source)","
>   at java.base/java.util.concurrent.FutureTask.run(Unknown Source)","
>   at 
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
>  Source)","
>   at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown 
> Source)","
>   at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown 
> Source)","
>   at java

[jira] [Commented] (QPIDJMS-587) io.netty:netty-transport-native-unix-common not managed but used

[Robbie Gemmell (Jira)]

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

Robbie Gemmell commented on QPIDJMS-587:


Without knowing what deps are declared, in what order, and what things are 
managed, and in which order, etc, a partial tree like that isn't all that 
interpretable. But it is showing why it makes sense to manage e.g netty 
versions in the application when you know you are mixing things using different 
versions of it.

> io.netty:netty-transport-native-unix-common not managed but used
> 
>
> Key: QPIDJMS-587
> URL: https://issues.apache.org/jira/browse/QPIDJMS-587
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client, qpid-jms-discovery
>Affects Versions: 2.2.0
> Environment: linux OS running a Spring Boot app 2.7.11 and qpid-jms 
> 2.2.0 together.
>Reporter: Harald Aamot
>Priority: Major
> Fix For: 2.3.0
>
> Attachments: image-2023-04-28-12-03-00-922.png, 
> image-2023-04-28-12-03-40-683.png
>
>
> When using qpid-jms 2.2.0 running on a linux OS then netty transitively pulls 
> in io.netty:netty-transport-native-unix-common .
> The version for this depndency is not managed in qpid-jms.
> When running a SpringBoot 2.7.11 application, Spring Boot manages io.netty on 
> version 4.1.91.Final . This version then gets used for 
> io.netty:netty-transport-native-unix-common, while the other netty components 
> run on 4.1.86.Final (managed by qpid-jms).
> This leads to a runtime exception when trying to connect.
> Reason is this:
> With netty 4.1.91.Final an incompatible change for qpid-jms has been made.
> Changelog [https://netty.io/news/2023/04/03/4-1-91-Final.html]
> incompatible change [https://github.com/netty/netty/issues/13317]
> code changed there [https://github.com/netty/netty/pull/13318]
> {noformat}
> ["jakarta.jms.JMSException: Could not initialize class 
> io.netty.channel.unix.Errors","
>   at 
> org.apache.qpid.jms.provider.ProviderException.toJMSException(ProviderException.java:34)","
>   at 
> org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:80)","
>   at 
> org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:112)","
>   at 
> org.apache.qpid.jms.JmsConnection.onAsyncException(JmsConnection.java:1564)","
>   at 
> org.apache.qpid.jms.JmsConnection.onProviderException(JmsConnection.java:1548)","
>   at 
> org.apache.qpid.jms.JmsConnection.onConnectionFailure(JmsConnection.java:1392)","
>   at 
> org.apache.qpid.jms.provider.failover.FailoverProvider.lambda$reportReconnectFailure$3(FailoverProvider.java:808)","
>   at 
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown 
> Source)","
>   at java.base/java.util.concurrent.FutureTask.run(Unknown Source)","
>   at 
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
>  Source)","
>   at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown 
> Source)","
>   at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown 
> Source)","
>   at java.base/java.lang.Thread.run(Unknown Source)","Caused by: 
> org.apache.qpid.jms.provider.exceptions.ProviderIOException: Could not 
> initialize class io.netty.channel.unix.Errors","
>   at 
> org.apache.qpid.jms.provider.exceptions.ProviderExceptionSupport.createOrPassthroughFatal(ProviderExceptionSupport.java:46)","
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider.connect(AmqpProvider.java:309)","
>   at 
> org.apache.qpid.jms.provider.failover.FailoverProvider$14.run(FailoverProvider.java:747)","
>   ... 6 more","Caused by: java.io.IOException: Could not initialize class 
> io.netty.channel.unix.Errors","
>   at 
> org.apache.qpid.jms.util.IOExceptionSupport.create(IOExceptionSupport.java:45)","
>   at 
> org.apache.qpid.jms.transports.netty.NettyTcpTransport$2.operationComplete(NettyTcpTransport.java:176)","
>   at 
> org.apache.qpid.jms.transports.netty.NettyTcpTransport$2.operationComplete(NettyTcpTransport.java:171)","
>   at 
> io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:590)","
>   at 
> io.netty.util.concurrent.DefaultP

[jira] [Commented] (QPIDJMS-587) io.netty:netty-transport-native-unix-common not managed but used

[Robbie Gemmell (Jira)]

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

Robbie Gemmell commented on QPIDJMS-587:


We have actually avoided the netty bom thus far as they have broken things with 
it multiple times. I would instead just add an entry for 
netty-transport-native-unix-common if needed.

This also suggests you are not managing the versions in your application 
though. If you are mixing components with dependencies on clearly different 
versions of netty, as you note you are, then ideally you would manage the 
versions yourself to predictably pick one, otherwise there it is still going to 
be possible you will see issues even if each individual component managed every 
module they use. Unless they use exactly the same modules a mismatch is always 
possible, as one of the versions of any module has to be picked by the build 
tools, and thus so is a combination that doesnt work...perhaps in less obvious 
ways than seen here.

> io.netty:netty-transport-native-unix-common not managed but used
> 
>
> Key: QPIDJMS-587
> URL: https://issues.apache.org/jira/browse/QPIDJMS-587
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client, qpid-jms-discovery
>Affects Versions: 2.2.0
> Environment: linux OS running a Spring Boot app 2.7.11 and qpid-jms 
> 2.2.0 together.
>Reporter: Harald Aamot
>Priority: Major
> Fix For: 2.3.0
>
>
> When using qpid-jms 2.2.0 running on a linux OS then netty transitively pulls 
> in io.netty:netty-transport-native-unix-common .
> The version for this depndency is not managed in qpid-jms.
> When running a SpringBoot 2.7.11 application, Spring Boot manages io.netty on 
> version 4.1.91.Final . This version then gets used for 
> io.netty:netty-transport-native-unix-common, while the other netty components 
> run on 4.1.86.Final (managed by qpid-jms).
> This leads to a runtime exception when trying to connect.
> Reason is this:
> With netty 4.1.91.Final an incompatible change for qpid-jms has been made.
> Changelog [https://netty.io/news/2023/04/03/4-1-91-Final.html]
> incompatible change [https://github.com/netty/netty/issues/13317]
> code changed there [https://github.com/netty/netty/pull/13318]
> {noformat}
> ["jakarta.jms.JMSException: Could not initialize class 
> io.netty.channel.unix.Errors","
>   at 
> org.apache.qpid.jms.provider.ProviderException.toJMSException(ProviderException.java:34)","
>   at 
> org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:80)","
>   at 
> org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:112)","
>   at 
> org.apache.qpid.jms.JmsConnection.onAsyncException(JmsConnection.java:1564)","
>   at 
> org.apache.qpid.jms.JmsConnection.onProviderException(JmsConnection.java:1548)","
>   at 
> org.apache.qpid.jms.JmsConnection.onConnectionFailure(JmsConnection.java:1392)","
>   at 
> org.apache.qpid.jms.provider.failover.FailoverProvider.lambda$reportReconnectFailure$3(FailoverProvider.java:808)","
>   at 
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown 
> Source)","
>   at java.base/java.util.concurrent.FutureTask.run(Unknown Source)","
>   at 
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
>  Source)","
>   at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown 
> Source)","
>   at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown 
> Source)","
>   at java.base/java.lang.Thread.run(Unknown Source)","Caused by: 
> org.apache.qpid.jms.provider.exceptions.ProviderIOException: Could not 
> initialize class io.netty.channel.unix.Errors","
>   at 
> org.apache.qpid.jms.provider.exceptions.ProviderExceptionSupport.createOrPassthroughFatal(ProviderExceptionSupport.java:46)","
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider.connect(AmqpProvider.java:309)","
>   at 
> org.apache.qpid.jms.provider.failover.FailoverProvider$14.run(FailoverProvider.java:747)","
>   ... 6 more","Caused by: java.io.IOException: Could not initialize class 
> io.netty.channel.unix.Errors","
>   at 
> org.apache.qpid.jms.util.IOExceptionSupport.create(IOExceptionSupport.java:45)","
> 

[jira] [Updated] (PROTON-2706) [Python] Allow setting the container id for containers/connections

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2706:
---
Description: 
This is an improvement suggested by [~jmennius]

(Originally suggested on [https://github.com/apache/qpid-proton/pull/388], 
though a different change was made for the commit below).

  was:This is an improvement suggested by [~jmennius]


> [Python] Allow setting the container id for containers/connections
> --
>
> Key: PROTON-2706
> URL: https://issues.apache.org/jira/browse/PROTON-2706
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> This is an improvement suggested by [~jmennius]
> (Originally suggested on [https://github.com/apache/qpid-proton/pull/388], 
> though a different change was made for the commit below).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2710) 0.40.0 release tasks

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2710:
---
Fix Version/s: proton-c-0.40.0
   (was: proton-c-0.39.0)

> 0.40.0 release tasks
> 
>
> Key: PROTON-2710
> URL: https://issues.apache.org/jira/browse/PROTON-2710
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-c, release
>        Reporter: Robbie Gemmell
>    Assignee: Robbie Gemmell
>Priority: Major
> Fix For: proton-c-0.40.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (PROTON-2710) 0.40.0 release tasks

[Robbie Gemmell (Jira)]

Robbie Gemmell created PROTON-2710:
--

 Summary: 0.40.0 release tasks
 Key: PROTON-2710
 URL: https://issues.apache.org/jira/browse/PROTON-2710
 Project: Qpid Proton
  Issue Type: Task
  Components: proton-c, release
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: proton-c-0.39.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2296) running ctest creates test sasl config artifacts in the source tree

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2296:
---
Affects Version/s: proton-c-0.32.0
   proton-c-0.39.0
   (was: proton-c-0.33.0)
   (was: proton-c-0.34.0)
   (was: proton-c-0.35.0)

> running ctest creates test sasl config artifacts in the source tree
> ---
>
> Key: PROTON-2296
> URL: https://issues.apache.org/jira/browse/PROTON-2296
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: build, proton-c
>Affects Versions: proton-c-0.32.0, proton-c-0.39.0
>    Reporter: Robbie Gemmell
>Priority: Major
>
> Running ctest creates test sasl config artifacts in the source tree, that are 
> then available to accidentally add to the git index:
>  # Create build dir as a subdir of repo checkout
>  # Run cmake from the build dir
>  # Source resulting config.sh
>  # Run make and ctest
>  # Observe git status
> {noformat}
> $ git status
> On branch main
> Your branch is up to date with 'origin/main'.
> Untracked files:
>  (use "git add ..." to include in what will be committed)
>  ../cpp/examples/sasl-conf/
>  ../sasl_conf/
>  ../tests/examples/sasl-conf/
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2095) Move away from SWIG to CFFI

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2095:
---
Issue Type: Improvement  (was: Wish)

> Move away from SWIG to CFFI
> ---
>
> Key: PROTON-2095
> URL: https://issues.apache.org/jira/browse/PROTON-2095
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: python-binding
>Affects Versions: proton-c-0.29.0, proton-c-future
>Reporter: Omer Katz
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> SWIG is fine but we're not using it for anything other than exporting all of 
> proton-c's API as is.
> Unfortunately SWIG only generates CPython extension bindings. This may be a 
> problem on PyPy where CPython extensions are either slow or simply won't 
> compile.
> Unlike SWIG, CFFI is portable both on CPython and PyPy.
> It also satisfies the same requirements as SWIG currently does.
> In addition, calls to CFFI simply release the GIL which will help 
> parallelizing Python applications using threads.
> By using CFFI we can also get rid of all of our setup.py code and simply use 
> it to build the extension. We will also no longer have problems building 
> wheels.
> The newest version of CFFI supports pkg-config so we can use that to find 
> proton-c easily.
> I'm willing to help with the refactor but I'll need a mentor since I'm not 
> familiar with the code base.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2708) New proactor APIs to query event batch for subject

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2708.

Resolution: Fixed

> New proactor APIs to query event batch for subject
> --
>
> Key: PROTON-2708
> URL: https://issues.apache.org/jira/browse/PROTON-2708
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> The object that a proactor event batch refers can't change during the 
> processing of the batch so you shouldn't need to extract the object from 
> every individual event of the batch,
> This change introduces an API for each of the possible subjects of an event 
> batch:
> {{pn_event_batch_proactor()}}, {{pn_event_batch_listener()}}, 
> {{pn_event_batch_connection()}}, {{pn_event_batch_raw_connection(),}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2708) New proactor APIs to query event batch for subject

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2708:
---
Fix Version/s: proton-c-0.39.0

> New proactor APIs to query event batch for subject
> --
>
> Key: PROTON-2708
> URL: https://issues.apache.org/jira/browse/PROTON-2708
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> The object that a proactor event batch refers can't change during the 
> processing of the batch so you shouldn't need to extract the object from 
> every individual event of the batch,
> This change introduces an API for each of the possible subjects of an event 
> batch:
> {{pn_event_batch_proactor()}}, {{pn_event_batch_listener()}}, 
> {{pn_event_batch_connection()}}, {{pn_event_batch_raw_connection(),}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2706) [Python] Allow setting the container id for containers/connections

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2706.

Resolution: Fixed

> [Python] Allow setting the container id for containers/connections
> --
>
> Key: PROTON-2706
> URL: https://issues.apache.org/jira/browse/PROTON-2706
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> This is an improvement suggested by [~jmennius]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2706) [Python] Allow setting the container id for containers/connections

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2706:
---
Fix Version/s: proton-c-0.39.0

> [Python] Allow setting the container id for containers/connections
> --
>
> Key: PROTON-2706
> URL: https://issues.apache.org/jira/browse/PROTON-2706
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> This is an improvement suggested by [~jmennius]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2677) cpp-example-container test failure

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2677.

Resolution: Fixed

> cpp-example-container test failure
> --
>
> Key: PROTON-2677
> URL: https://issues.apache.org/jira/browse/PROTON-2677
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> Since the commit for PROTON-2657 there have been test failures due to the C++ 
> broker example crashing and failing the TSAN test runs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2677) cpp-example-container test failure

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2677:
---
Fix Version/s: proton-c-0.39.0

> cpp-example-container test failure
> --
>
> Key: PROTON-2677
> URL: https://issues.apache.org/jira/browse/PROTON-2677
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> Since the commit for PROTON-2657 there have been test failures due to the C++ 
> broker example crashing and failing the TSAN test runs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2669) Change version of cmake supported to 3.16 and up

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2669.

Resolution: Fixed

> Change version of cmake supported to 3.16 and up
> 
>
> Key: PROTON-2669
> URL: https://issues.apache.org/jira/browse/PROTON-2669
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> We've supported CMake 2.8.12 for a very long time, but it has made our life 
> much harder for building.
> At this point the orld has moved on and every system we care about has a 
> newer version of cmake available - 3.16 seems like a fairly conservative 
> choice (Currently cmake is version 3.25)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2669) Change version of cmake supported to 3.16 and up

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2669:
---
Fix Version/s: proton-c-0.39.0

> Change version of cmake supported to 3.16 and up
> 
>
> Key: PROTON-2669
> URL: https://issues.apache.org/jira/browse/PROTON-2669
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> We've supported CMake 2.8.12 for a very long time, but it has made our life 
> much harder for building.
> At this point the orld has moved on and every system we care about has a 
> newer version of cmake available - 3.16 seems like a fairly conservative 
> choice (Currently cmake is version 3.25)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2690) [Python] The desired and offered capabilities field in open performative should be symbol array or symbol

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2690.

Resolution: Fixed

> [Python] The desired and offered capabilities field in open performative 
> should be symbol array or symbol
> -
>
> Key: PROTON-2690
> URL: https://issues.apache.org/jira/browse/PROTON-2690
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> Currently if you pass a list (or a  symbol list) to connection.open the 
> performative that goes on the wire contains a list. The AMQP standard 
> requires that the wire contains a symbol array or a single symbol.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2690) [Python] The desired and offered capabilities field in open performative should be symbol array or symbol

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2690:
---
Fix Version/s: proton-c-0.39.0

> [Python] The desired and offered capabilities field in open performative 
> should be symbol array or symbol
> -
>
> Key: PROTON-2690
> URL: https://issues.apache.org/jira/browse/PROTON-2690
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> Currently if you pass a list (or a  symbol list) to connection.open the 
> performative that goes on the wire contains a list. The AMQP standard 
> requires that the wire contains a symbol array or a single symbol.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2667) Various CI python test failures

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2667.

Resolution: Fixed

> Various CI python test failures
> ---
>
> Key: PROTON-2667
> URL: https://issues.apache.org/jira/browse/PROTON-2667
> Project: Qpid Proton
>  Issue Type: Bug
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> Various of the python tests have been failing on some or all of the CI builds 
> for a while. These have a few causes and symptoms. but are all related to 
> using newer versions of python or the various python modules used in testing.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2667) Various CI python test failures

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2667:
---
Fix Version/s: proton-c-0.39.0

> Various CI python test failures
> ---
>
> Key: PROTON-2667
> URL: https://issues.apache.org/jira/browse/PROTON-2667
> Project: Qpid Proton
>  Issue Type: Bug
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> Various of the python tests have been failing on some or all of the CI builds 
> for a while. These have a few causes and symptoms. but are all related to 
> using newer versions of python or the various python modules used in testing.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2666) [C++] Allow more python examples to run using the C++ broker example

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2666.

Resolution: Fixed

> [C++] Allow more python examples to run using the C++ broker example
> 
>
> Key: PROTON-2666
> URL: https://issues.apache.org/jira/browse/PROTON-2666
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Affects Versions: proton-c-0.38.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> It would be nice to be able to run all the in tree examples with an broker 
> that is in the proton source tree itself. Currently there seem to be 3 
> capabilities needed for this:
> * Anonymous relay
> * Transactions
> * Selector filters
> Anonymous relay is a fairly simple thing to implement; transactions would be 
> the next simplest; selectors are somewhat complex and would need to parse an 
> entire language.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2666) [C++] Allow more python examples to run using the C++ broker example

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2666:
---
Fix Version/s: proton-c-0.39.0

> [C++] Allow more python examples to run using the C++ broker example
> 
>
> Key: PROTON-2666
> URL: https://issues.apache.org/jira/browse/PROTON-2666
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Affects Versions: proton-c-0.38.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> It would be nice to be able to run all the in tree examples with an broker 
> that is in the proton source tree itself. Currently there seem to be 3 
> capabilities needed for this:
> * Anonymous relay
> * Transactions
> * Selector filters
> Anonymous relay is a fairly simple thing to implement; transactions would be 
> the next simplest; selectors are somewhat complex and would need to parse an 
> entire language.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Closed] (PROTON-2696) raw_connection_test.cpp:846:12: error: private field 'accept_' is not used [-Werror,-Wunused-private-field]

[Robbie Gemmell (Jira)]

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

Robbie Gemmell closed PROTON-2696.
--

> raw_connection_test.cpp:846:12: error: private field 'accept_' is not used 
> [-Werror,-Wunused-private-field]
> ---
>
> Key: PROTON-2696
> URL: https://issues.apache.org/jira/browse/PROTON-2696
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: build, proton-c
>Affects Versions: proton-c-0.39.0
> Environment: Arm64 Ubuntu Focal on TravisCI
>Reporter: Jiri Daněk
>Priority: Major
>
> https://app.travis-ci.com/github/jiridanek/skupper-router/jobs/598829054#L950
> {noformat}
> /home/travis/build/jiridanek/skupper-router/qpid-proton/c/tests/raw_connection_test.cpp:846:12:
>  error: private field 'accept_' is not used [-Werror,-Wunused-private-field]
>   handler *accept_; // Handler for accepted connections
>^
> 1 error generated.
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2696) raw_connection_test.cpp:846:12: error: private field 'accept_' is not used [-Werror,-Wunused-private-field]

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2696:
---
Fix Version/s: (was: proton-c-0.39.0)

Removing fix-version as its test-only and the causing change/JIRA is already a 
bug in the same release. Linked this issue as being part of it.

> raw_connection_test.cpp:846:12: error: private field 'accept_' is not used 
> [-Werror,-Wunused-private-field]
> ---
>
> Key: PROTON-2696
> URL: https://issues.apache.org/jira/browse/PROTON-2696
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: build, proton-c
>Affects Versions: proton-c-0.39.0
> Environment: Arm64 Ubuntu Focal on TravisCI
>Reporter: Jiri Daněk
>Priority: Major
>
> https://app.travis-ci.com/github/jiridanek/skupper-router/jobs/598829054#L950
> {noformat}
> /home/travis/build/jiridanek/skupper-router/qpid-proton/c/tests/raw_connection_test.cpp:846:12:
>  error: private field 'accept_' is not used [-Werror,-Wunused-private-field]
>   handler *accept_; // Handler for accepted connections
>^
> 1 error generated.
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2695) Epoll proactor raw connections hang on incomplete batches

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2695.

Resolution: Fixed

> Epoll proactor raw connections hang on incomplete batches
> -
>
> Key: PROTON-2695
> URL: https://issues.apache.org/jira/browse/PROTON-2695
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: proton-c-0.38.0
>Reporter: Clifford Jansen
>Assignee: Clifford Jansen
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> If an application returns a batch before draining all available events from 
> it, the internal state machine may not have completed the steps needed to 
> determine the correct polling events of interest, leaving the associated task 
> in a hung state.
> This is particularly relevant for the Catch2 test harness using the proactor.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2695) Epoll proactor raw connections hang on incomplete batches

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2695:
---
Fix Version/s: proton-c-0.39.0

> Epoll proactor raw connections hang on incomplete batches
> -
>
> Key: PROTON-2695
> URL: https://issues.apache.org/jira/browse/PROTON-2695
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: proton-c-0.38.0
>Reporter: Clifford Jansen
>Assignee: Clifford Jansen
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> If an application returns a batch before draining all available events from 
> it, the internal state machine may not have completed the steps needed to 
> determine the correct polling events of interest, leaving the associated task 
> in a hung state.
> This is particularly relevant for the Catch2 test harness using the proactor.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2663) class ssl_client_options does not have a constructor for a custom client certificate, and default certificate trust database

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2663:
---
Affects Version/s: proton-c-0.38.0

> class ssl_client_options does not have a constructor for a custom client 
> certificate, and default certificate trust database 
> -
>
> Key: PROTON-2663
> URL: https://issues.apache.org/jira/browse/PROTON-2663
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Affects Versions: proton-c-0.37.0, proton-c-0.38.0
> Environment: Linux 64bit
> Ubuntu 22.04: libqpid-proton-cpp12 0.22.0-5 (used for testing, not intended 
> for production)
> Redhat, Oracle: qpid-proton-cpp-0.37.0-1.el8.x86_64
>Reporter: Marko Hrastovec
>Assignee: Andrew Stitcher
>Priority: Major
>  Labels: ssl
> Fix For: proton-c-0.39.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Class ssl_client_options does not have a constructor for a custom client 
> certificate, and default certificate trust database.
> Out application has to present a custom certificate to the server, but the 
> server uses a certificate signed by a certificate authority (CA) that is 
> present in the systems default certificate trust database.
> Curently, our only option to connect is to supply a dummy certificate trust 
> database, and use proton::ssl::ANONYMOUS_PEER which disables server check. In 
> that way, we skip an important check for a secure connection. That is 
> unacceptable for a production version of our application. Until we come to a 
> production version we must resolve that issue. That is why I marked it as a 
> blocker.
> I have a patch, but I am not sure how to contribute it. I guess reporting is 
> a first step?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2663) class ssl_client_options does not have a constructor for a custom client certificate, and default certificate trust database

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2663:
---
Priority: Major  (was: Blocker)

> class ssl_client_options does not have a constructor for a custom client 
> certificate, and default certificate trust database 
> -
>
> Key: PROTON-2663
> URL: https://issues.apache.org/jira/browse/PROTON-2663
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Affects Versions: proton-c-0.37.0
> Environment: Linux 64bit
> Ubuntu 22.04: libqpid-proton-cpp12 0.22.0-5 (used for testing, not intended 
> for production)
> Redhat, Oracle: qpid-proton-cpp-0.37.0-1.el8.x86_64
>Reporter: Marko Hrastovec
>Assignee: Andrew Stitcher
>Priority: Major
>  Labels: ssl
> Fix For: proton-c-0.39.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Class ssl_client_options does not have a constructor for a custom client 
> certificate, and default certificate trust database.
> Out application has to present a custom certificate to the server, but the 
> server uses a certificate signed by a certificate authority (CA) that is 
> present in the systems default certificate trust database.
> Curently, our only option to connect is to supply a dummy certificate trust 
> database, and use proton::ssl::ANONYMOUS_PEER which disables server check. In 
> that way, we skip an important check for a secure connection. That is 
> unacceptable for a production version of our application. Until we come to a 
> production version we must resolve that issue. That is why I marked it as a 
> blocker.
> I have a patch, but I am not sure how to contribute it. I guess reporting is 
> a first step?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Assigned] (PROTON-2663) class ssl_client_options does not have a constructor for a custom client certificate, and default certificate trust database

[Robbie Gemmell (Jira)]

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

Robbie Gemmell reassigned PROTON-2663:
--

Assignee: Andrew Stitcher

> class ssl_client_options does not have a constructor for a custom client 
> certificate, and default certificate trust database 
> -
>
> Key: PROTON-2663
> URL: https://issues.apache.org/jira/browse/PROTON-2663
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Affects Versions: proton-c-0.37.0
> Environment: Linux 64bit
> Ubuntu 22.04: libqpid-proton-cpp12 0.22.0-5 (used for testing, not intended 
> for production)
> Redhat, Oracle: qpid-proton-cpp-0.37.0-1.el8.x86_64
>Reporter: Marko Hrastovec
>Assignee: Andrew Stitcher
>Priority: Blocker
>  Labels: ssl
> Fix For: proton-c-0.39.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Class ssl_client_options does not have a constructor for a custom client 
> certificate, and default certificate trust database.
> Out application has to present a custom certificate to the server, but the 
> server uses a certificate signed by a certificate authority (CA) that is 
> present in the systems default certificate trust database.
> Curently, our only option to connect is to supply a dummy certificate trust 
> database, and use proton::ssl::ANONYMOUS_PEER which disables server check. In 
> that way, we skip an important check for a secure connection. That is 
> unacceptable for a production version of our application. Until we come to a 
> production version we must resolve that issue. That is why I marked it as a 
> blocker.
> I have a patch, but I am not sure how to contribute it. I guess reporting is 
> a first step?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2704) [Python] The examples test hangs

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2704.

Resolution: Fixed

> [Python] The examples test hangs
> 
>
> Key: PROTON-2704
> URL: https://issues.apache.org/jira/browse/PROTON-2704
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Affects Versions: proton-c-0.39.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> Running the python examples via the unittest in the examples directory hangs 
> at the various sync client tests.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2668) Change versions of Python used/supported

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2668.

Resolution: Fixed

> Change versions of Python used/supported
> 
>
> Key: PROTON-2668
> URL: https://issues.apache.org/jira/browse/PROTON-2668
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> We currently support Python 3.6 upwards; this is an old and unsupported 
> version of python pretty much everywhere.
> In particular some of the CI systems no longer even have this version which 
> is causing some build failures.
> Let's change the supported versions to be 3.8 and up which covers pretty much 
> all supported LTS versions of Ubuntu (20.04, 22.04)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2699) Turn off proactor fdlimit test by default

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2699.

Resolution: Fixed

> Turn off proactor fdlimit test by default
> -
>
> Key: PROTON-2699
> URL: https://issues.apache.org/jira/browse/PROTON-2699
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: proton-c-0.38.0
>Reporter: Clifford Jansen
>Assignee: Clifford Jansen
>Priority: Minor
> Fix For: proton-c-0.39.0
>
>
> It has had many tweaks over the years yet remains sensitive to changes in OS 
> versions, Python versions, parallelism of the test, system resources... i.e. 
> it is flaky.  Keep it around but off by default.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[ANNOUNCE] Apache Qpid Proton-J 0.34.1 released

[Robbie Gemmell]

The Apache Qpid (https://qpid.apache.org) community is pleased to announce
the immediate availability of Apache Qpid Proton-J 0.34.1.

Apache Qpid Proton-J is a messaging library for the Advanced Message Queuing
Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, https://www.amqp.org). It can be used
in a wide range of messaging applications including brokers, clients,
routers, bridges, proxies, and more.

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-proton-j-0.34.1/release-notes.html

Thanks to all involved,
Robbie

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

[jira] [Resolved] (QPIDJMS-585) update to proton-j 0.34.1

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPIDJMS-585.

Resolution: Fixed

> update to proton-j 0.34.1
> -
>
> Key: QPIDJMS-585
> URL: https://issues.apache.org/jira/browse/QPIDJMS-585
> Project: Qpid JMS
>  Issue Type: Task
>  Components: qpid-jms-client
>        Reporter: Robbie Gemmell
>    Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.9.0, 2.3.0
>
>
> update to proton-j 0.34.1



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (QPIDJMS-585) update to proton-j 0.34.1

[Robbie Gemmell (Jira)]

Robbie Gemmell created QPIDJMS-585:
--

 Summary: update to proton-j 0.34.1
 Key: QPIDJMS-585
 URL: https://issues.apache.org/jira/browse/QPIDJMS-585
 Project: Qpid JMS
  Issue Type: Task
  Components: qpid-jms-client
Reporter: Robbie Gemmell
 Fix For: 1.9.0, 2.3.0


update to proton-j 0.34.1



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Assigned] (QPIDJMS-585) update to proton-j 0.34.1

[Robbie Gemmell (Jira)]

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

Robbie Gemmell reassigned QPIDJMS-585:
--

Assignee: Robbie Gemmell

> update to proton-j 0.34.1
> -
>
> Key: QPIDJMS-585
> URL: https://issues.apache.org/jira/browse/QPIDJMS-585
> Project: Qpid JMS
>  Issue Type: Task
>  Components: qpid-jms-client
>        Reporter: Robbie Gemmell
>    Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.9.0, 2.3.0
>
>
> update to proton-j 0.34.1



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2688) [proton-j] stale entries can stick in transport work list upon freeing sender with buffered delivery

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2688.

Resolution: Fixed

> [proton-j] stale entries can stick in transport work list upon freeing sender 
> with buffered delivery
> 
>
> Key: PROTON-2688
> URL: https://issues.apache.org/jira/browse/PROTON-2688
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: proton-j-0.34.0
>    Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>Priority: Major
> Fix For: proton-j-0.34.1
>
>
> When a sender link is freed with a buffered delivery it can become stuck in 
> the transport work list, leading to retention when repeating this with lots 
> of senders on a long lived session/connection. The transport should clear 
> such entries from the work list when encountered and it is clear they cant be 
> actioned.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (PROTON-2687) [proton-j] stale entries can stick in transport work list upon freeing session with outstanding deliveries

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved PROTON-2687.

Resolution: Fixed

> [proton-j] stale entries can stick in transport work list upon freeing 
> session with outstanding deliveries
> --
>
> Key: PROTON-2687
> URL: https://issues.apache.org/jira/browse/PROTON-2687
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: proton-j-0.34.0
>    Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>Priority: Major
> Fix For: proton-j-0.34.1
>
>
> In certain circumstances it is possible for delivery entries to make it into 
> the transport work list which then cant be actioned, but are not cleared as 
> they weren't actioned, meaning the list retains the delivery, link, and 
> session. This was noticed after freeing a closed session without previously 
> closing a link that still had outstanding delivery entries. Repeating this 
> situation with lots of sessions on a long lived connections can lead to 
> significant retention. The transport should clear such cases from the work 
> list if encountered, and we should prevent their creation where possible.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (PROTON-2688) [proton-j] stale entries can stick in transport work list upon freeing sender with buffered delivery

[Robbie Gemmell (Jira)]

Robbie Gemmell created PROTON-2688:
--

 Summary: [proton-j] stale entries can stick in transport work list 
upon freeing sender with buffered delivery
 Key: PROTON-2688
 URL: https://issues.apache.org/jira/browse/PROTON-2688
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-j
Affects Versions: proton-j-0.34.0
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: proton-j-0.35.0


When a sender link is freed with a buffered delivery it can become stuck in the 
transport work list, leading to retention when repeating this with lots of 
senders on a long lived session/connection. The transport should clear such 
entries from the work list when encountered and it is clear they cant be 
actioned.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (PROTON-2687) [proton-j] stale entries can stick in transport work list upon freeing session with outstanding deliveries

[Robbie Gemmell (Jira)]

Robbie Gemmell created PROTON-2687:
--

 Summary: [proton-j] stale entries can stick in transport work list 
upon freeing session with outstanding deliveries
 Key: PROTON-2687
 URL: https://issues.apache.org/jira/browse/PROTON-2687
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-j
Affects Versions: proton-j-0.34.0
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: proton-j-0.35.0


In certain circumstances it is possible for delivery entries to make it into 
the transport work list which then cant be actioned, but are not cleared as 
they weren't actioned, meaning the list retains the delivery, link, and 
session. This was noticed after freeing a closed session without previously 
closing a link that still had outstanding delivery entries. Repeating this 
situation with lots of sessions on a long lived connections can lead to 
significant retention. The transport should clear such cases from the work list 
if encountered, and we should prevent their creation where possible.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (QPIDJMS-584) JMSProducer#send(...body) will NPE when given null Map or byte[] body values

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPIDJMS-584.

Resolution: Fixed

> JMSProducer#send(...body) will NPE when given null Map or byte[] body values
> 
>
> Key: QPIDJMS-584
> URL: https://issues.apache.org/jira/browse/QPIDJMS-584
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 1.8.0, 2.2.0
>    Reporter: Robbie Gemmell
>    Assignee: Robbie Gemmell
>Priority: Trivial
> Fix For: 1.9.0, 2.3.0
>
>
> The JMSProducer interface has methods for sending body values without a 
> containing Message object. The methods define they should succeed and send a 
> message with no body when given a null value, but the Map and byte[] related 
> method implementations would currently throw a NullPointerException instead.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (QPIDJMS-584) JMSProducer#send(...body) will NPE when given null Map or byte[] body values

[Robbie Gemmell (Jira)]

Robbie Gemmell created QPIDJMS-584:
--

 Summary: JMSProducer#send(...body) will NPE when given null Map or 
byte[] body values
 Key: QPIDJMS-584
 URL: https://issues.apache.org/jira/browse/QPIDJMS-584
 Project: Qpid JMS
  Issue Type: Bug
  Components: qpid-jms-client
Affects Versions: 2.2.0, 1.8.0
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: 1.9.0, 2.3.0


The JMSProducer interface has methods for sending body values without a 
containing Message object. The methods define they should succeed and send a 
message with no body when given a null value, but the Map and byte[] related 
method implementations would currently throw a NullPointerException instead.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (QPID-8523) [Broker-J] refusing-attach while rejecting consumer does not set required initial-delivery-count field

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated QPID-8523:
-
Fix Version/s: (was: qpid-java-broker-8.0.7)

> [Broker-J] refusing-attach while rejecting consumer does not set required 
> initial-delivery-count field
> --
>
> Key: QPID-8523
> URL: https://issues.apache.org/jira/browse/QPID-8523
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-8.0.4
>    Reporter: Robbie Gemmell
>Priority: Major
>
> Attempting to create a consumer link from e.g. a non-existing address results 
> in refusal of the link, which in case of a consumer is done by sending a 
> 'response' attach with null source to indicate the terminus wasnt created, 
> followed by a detach with the error.
> The broker does send an attach without a source, but it omits the 
> initialDeliveryCount value from the attach, which the spec says is required 
> when role=SENDER ("This MUST NOT be null if role is sender, and it is ignored 
> if the role is receiver."). Protocol libraries validating such required 
> values will run afoul of this, leading to decode error that can bring the 
> connection down unnecessarily.
> From looking at the wire encoding, it appears only the first 3 fields (name, 
> handle, role) of the attach are being set, with the rest unpopulated and thus 
> being equivalent to null or any default they may have.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (PROTON-2668) Change versions of Python used/supported

[Robbie Gemmell (Jira)]

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

Robbie Gemmell updated PROTON-2668:
---
Fix Version/s: proton-c-0.39.0

> Change versions of Python used/supported
> 
>
> Key: PROTON-2668
> URL: https://issues.apache.org/jira/browse/PROTON-2668
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> We currently support Python 3.6 upwards; this is an old and unsupported 
> version of python pretty much everywhere.
> In particular some of the CI systems no longer even have this version which 
> is causing some build failures.
> Let's change the supported versions to be 3.8 and up which covers pretty much 
> all supported LTS versions of Ubuntu (20.04, 22.04)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Commented] (PROTON-2668) Change versions of Python used/supported

[Robbie Gemmell (Jira)]

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

Robbie Gemmell commented on PROTON-2668:


RHEL 8 was also considered I believe, with 3.8 and 3.9 available to install: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/assembly_introduction-to-python_configuring-basic-system-settings

> Change versions of Python used/supported
> 
>
> Key: PROTON-2668
> URL: https://issues.apache.org/jira/browse/PROTON-2668
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
>
> We currently support Python 3.6 upwards; this is an old and unsupported 
> version of python pretty much everywhere.
> In particular some of the CI systems no longer even have this version which 
> is causing some build failures.
> Let's change the supported versions to be 3.8 and up which covers pretty much 
> all supported LTS versions of Ubuntu (20.04, 22.04)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (QPIDJMS-583) Update to Netty 4.1.87

[Robbie Gemmell (Jira)]

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

Robbie Gemmell resolved QPIDJMS-583.

Resolution: Fixed

> Update to Netty 4.1.87
> --
>
> Key: QPIDJMS-583
> URL: https://issues.apache.org/jira/browse/QPIDJMS-583
> Project: Qpid JMS
>  Issue Type: Task
>  Components: qpid-jms-client
>        Reporter: Robbie Gemmell
>    Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 1.9.0, 2.3.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (QPIDJMS-583) Update to Netty 4.1.87

[Robbie Gemmell (Jira)]

Robbie Gemmell created QPIDJMS-583:
--

 Summary: Update to Netty 4.1.87
 Key: QPIDJMS-583
 URL: https://issues.apache.org/jira/browse/QPIDJMS-583
 Project: Qpid JMS
  Issue Type: Task
  Components: qpid-jms-client
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: 1.9.0, 2.3.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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