Re: BrokerJ + Oauth2 max frame size

you have now found > something to exceed even that. It doesnt look like it allows > configuring it, but increasing that seems to be the only option that > would help here. > > On Thu, 18 May 2023 at 22:14, Dan Langford wrote: > > > > we are exploring the use of Oauth2

BrokerJ + Oauth2 max frame size

we are exploring the use of Oauth2 with Qpid BrokerJ. We use okta but its all openid and the keycloak provider seems like it might work for us. we are referencing this confluence article about how to configure the qpid jms client to update the token as it expires https://cwiki.apache.org/confluenc

Re: [Broker-J] unable to AutoGenerate self signed on Java17

issue? > > > > As a workaround the mentioned JVM flags can be used, namely: > > > > --add-opens java.base/sun.security.tools.keytool=ALL-UNNAMED > > --add-opens java.base/sun.security.x509=ALL-UNNAMED > > > > Kind regards, > > Daniil Kirilyuk > >

Re: [Broker-J 6.1+] ACL+LDAP requires full DN?

> > > I would say, the current implementation doesn't support the desired > > behavior. You could create a JIRA for this issue. > > > > Kind regards, > > Daniil Kirilyuk > > > > On Wed, 8 Feb 2023 at 23:02, Dan Langford wrote: > > >

[Broker-J] unable to AutoGenerate self signed on Java17

I have run QPID Broker-J 9.0 on openjdk17 for mac as well as temurin17 for linux. in both when i try to AutoGenerate a keystore with self signed cert i get the following error: org.apache.qpid.server.configuration.IllegalConfigurationException: Unable to construct keystore at org.apache.qpid.

[Broker-J 6.1+] ACL+LDAP requires full DN?

We are upgrading some very old qpid servers in the enterprise (6.0.8) and we use LDAP authentication. Where I might have a current ACL entry like this: ACL ALLOW danlangford ALL im finding in QPID 6.1-9.0 i am needing the rule to look like this ACL ALLOW "cn=danlangford,ou=000,ou=People,o=MyEnte

Re: Qpid Jms Client 0.35.0 problem reading message after some message redeliveries

very-count within the message, and that didnt > change as the message was 'released', which is what happened > inbetween. I assume you threw an exception from onMessage to achieve > that, and so that behaviour relates to > https://issues.apache.org/jira/browse/QPIDJMS-388 >

quick qpid-jms-client v0.35.0 (AMQP1.0) questions

1) when i configure a qpid-jms-client (AMQP1.0) PREFETCH to 1 via the uri like this: ?jms.prefetchPolicy.all=1 is that going to prefetch 1 while I process 1 for a total of 2 messages having been acquired or does the prefetch number include messages currently being processed by my application logic?

Qpid Jms Client 0.35.0 problem reading message after some message redeliveries

TLDR messages redelivered from artemis broker get into state where qpid jms client api will not show me the properties or body. trying to determine if its the broker sending down bad data or if its the client not supporting some frame structure I have a message on my broker right now (Artemis 2.6.

[broker-j 7.0.3] TTL expire to alt binding

is there way to configure the broker to treat TTL expired messages as other "undeliverable" messages by delivering those to the configured Alternate Binding?

Re: Dispatch Router load balancing config questions

> On 09/08/17 16:59, Dan Langford wrote: > > back from vacation now. i upgraded to 0.8.0 and local/session > transactions > > look like they are working as expected. > > > > *Question about JMS filters / message selectors*: when i connect to my > > artemis broker wi

Re: Dispatch Router load balancing config questions

via the client? with my aforementioned configuration https://gist.github.com/danlangford/4944dcc6c0d2703ffb8555603ed27340 would you expect jms filters to work? On Wed, Aug 2, 2017 at 9:46 AM Dan Langford wrote: > Thank you all very much. i will upgrade to dispatch router 0.8.0 and > forget

Re: Dispatch Router load balancing config questions

more about XA and realize that for all of my clients they do not need transactions or that the local transactions will be just great. On Wed, Aug 2, 2017 at 4:43 AM Robbie Gemmell wrote: > On 1 August 2017 at 22:20, Dan Langford wrote: > > ( github gist with all the config and data

Re: Dispatch Router load balancing config questions

tiple > deliveries asynchronously, you will see them being distributed to both > brokers in the network. You can make the local-affinity stronger by > increasing the inter-router cost. > > -Ted > > On Tue, Aug 1, 2017 at 3:47 AM, Dan Langford > wrote: > > > Last wee

Dispatch Router load balancing config questions

Last week I had a thread with lots of little questions around Dispatch Routers. Ted Ross has been awesome to answer most of those. As a result I feel like I have my QDR config shaping up a bit better. HOWEVER with some more very focused questions I thought it would be best to start a new thread. Th

Re: Dispatch Router questions

like the old Qpid client for Java but should we expect XA transactions to work through dispatch Router? Thanks so much for your time and thought On Wed, Jul 26, 2017 at 1:10 PM Ted Ross wrote: > On Fri, Jul 21, 2017 at 7:12 PM, Dan Langford > wrote: > > > On Thu, Jul 20, 2017

Re: Dispatch Router questions

On Thu, Jul 20, 2017 at 9:58 AM Ted Ross wrote: > On Wed, Jul 19, 2017 at 7:36 PM, Dan Langford > wrote: > > > > - Can I configure QDR to autoLink in and out ANY/ALL addresses? > > No. There is no way currently for QDR to know what queues are present on > > its co

Dispatch Router questions

So I am struggling to wrap my head around some dispatch Router concepts and was wondering if somebody would be willing to point me in the right direction on one or more of my idea. Background: I am doing some due diligence at my place of employment regarding AMQP1.0 brokers and currently I am tryi

Re: [Java Client JMS] qpid-jms-client 0.22.0 vs qpid-client 6.1.2: prefetch behaving differently

push around millions with very little problems Thanks. I'm anxious for a Qpid JMS client I can encourage my customers to upgrade to to avoid this in the future. Let me know if you would like me to test any bug fixes On Fri, May 5, 2017 at 8:34 AM Dan Langford wrote: > Thanks for the replies

Re: [Java Client JMS] qpid-jms-client 0.22.0 vs qpid-client 6.1.2: prefetch behaving differently

> > -- Rob > > > > Robbie > > > > On 5 May 2017 at 10:07, Keith W wrote: > > > Hi Dan > > > > > > Thanks for the comprehensive report. I can reproduce what you see and > > > confirm there appears to be a bug. I'll hope to be able to take

[Java Client JMS] qpid-jms-client 0.22.0 vs qpid-client 6.1.2: prefetch behaving differently

So over the past few weeks we have had a huge influx of messages on our enterprise message bus (qpid java 6.0.4 serves the AMQP1.0 messaging portion) and when one of our clients struggled scaling their application up it got us looking at prefetch. we thought it was odd that all 500k messages in the

[qpid java broker 6.1.x] enqueue/dequeue over HTTP?

I am going through the HTTP API documentation and I just want to confirm what I am seeing. Is there a portion of the API to enqueue and dequeue messages via HTTP? I was hoping for some REST api like Google's TaskQueues that inc

Re: [Qpid Broker - 6.0.4] Junit testable?

You already mentioned HornetQ I would also toss out there ActiveMQ as one that is fantastic at embedding. In my Java projects I code to JMS and in Unit tests I mock out JMS apis because I am just testing MY code. Sometimes it's just easier or a more thorough test to include a broker especially sinc

Re: [Java Broker 6.1.1, qpid-jms-client 0.20.0] Best match for SASL auth was: null

SCRAM-SHA-256 Auth Provider? Or am I misunderstanding the relationship between a SASL Mechanism and an Auth Provider? As always thanks for your time On Sat, Mar 11, 2017 at 4:07 PM Rob Godfrey wrote: On 11 March 2017 at 22:35, Dan Langford wrote: > thanks for explaining this all to me. i co

Re: [Java Broker 6.1.1, qpid-jms-client 0.20.0] Best match for SASL auth was: null

noticed and fixed recently via > https://issues.apache.org/jira/browse/QPID-7643, so that should work > again in the next release. > > Robbie > > On 10 March 2017 at 22:11, Dan Langford wrote: > > *Software Versions* > > Java Broker 6.1.1 > >

[Java Broker 6.1.1, qpid-jms-client 0.20.0] Best match for SASL auth was: null

*Software Versions* Java Broker 6.1.1 qpid-jms-client 0.20.0 *When my Authentication Provider assigned to my AMQP port is PlainPasswordFile then i am able to connect just fine:* *RemoteURI *amqp://:5672?amqp.vhost=default [AmqpProvider:(1):[amqp://:5672]] INFO org.apache.qpid.jms.sasl.SaslMecha

[Qpid Java Broker] ensure nondestructive via UI

Is there a way via the web management ui to create a queue that ensures clients are nondestructive? I see the rest interface but don't know if there is a way I can use qpid.ensure_nondestructive_consumers argument somehow via context variables. If it's possible via the web UI then my ops team could

Re: deploying Qpid via Cloud Foundry

gt; in a CloudFoundry scenario. > > Kind regards, > Lorenz > > > [1] > > https://qpid.apache.org/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Security.html#Java-Broker-Security-OAuth2-Provider > [2] https://docs.cloudfoundry.org/api/uaa/ > [3] https://docs.clou

deploying Qpid via Cloud Foundry

On the IRC channel last week rgodfrey mentioned that some of you may be deploying Qpid via Cloud Foundry. I am exploring some of those ideas for use at my place of employment and was wondering if I could pick your brain a little bit on what that setup might look like. Please forgive me if my questi