Broker-J Queue Message persistent override

We are using Broker-J 7.0.2. For a couple of Queues I've set setting Persist Messages? to 'Never'. However when sending a message via a Qpid JMS 0.30.0 client the messages are being stored as Persistent. I've tried both methods MessageProducer.send(Message message) and

Re: Broker-j - Restoring BDB Backup

Thanks for the reply Alex. I've been working on our production Broker-J backup and recovery solution and my plan was to create a little Java app that utilizes the Broker-J provided BDBBackup class and perform a hot backup every 15 minutes. Ideally we'd never have to use it but things happen (our

Ok to delete default VirtualHostNode with Broker-J 7?

We are using Broker-J 7.0.2. We are utilizing High Availability and I've configured a Virtual Host and Virtual Host Nodes and we do not utilize the 'default' Virtual Host Nodes in any of our Broker-J instances. Just to keep the configuration clean, I would like to delete the 'default'

Broker-J 7.0.2 auto-creation policies

Do you have any documentation regarding the new Broker-J 7.0.2 virtual host node auto-creation policies (https://issues.apache.org/jira/browse/QPID-8102)? I looked in the broker book but couldn't find anything about it. It sounds like something we might want to start utilizing. Thanks Bryan

Broker-j - Restoring BDB Backup

I'm planning on using the broker-j provided org.apache.qpid.server.store.berkeleydb.BDBBackup class to backup our HA BDB database. I want to make sure I understand the restore process. To restore the DB for the Virtual Host Node the backup was taken for do we simply: 1. Stop the VirtualHostNode

Re: qpid-broker-j-7.0.0 failover is slow

Answers to your questions.. Could you please clarify whether you have seen "Gave up waiting" warnings with synchronous or asynchronous recoverer? - definitely when using synchronous but also pretty sure it was after I made the context change to use asynchronous recovery also. I've been making

Re: How to define RulesBased ACLs using Qpid Broker-J 7.0.0

Thanks for the info. I was able to get the acls defined via the REST API Update. There were a few little quirks I ran into where the documentation on the ACL page

Re: qpid-broker-j-7.0.0 failover is slow

I was utilizing DLQs (Alternate Binding) for most of my queues and I think that is why the Virtual Host Node startup time was so slow (1 minute 45 seconds). After I deleted all those DLQs, the startup time was down to 11 seconds - a huge difference especially when dealing with a failover

sole-connection-enforcement-policy with apache-qpid-jms-0.29.0

I'm using apache-qpid-broker-j-7.0.1 and have been doing some development with client apache-qpid-jms-0-x-6.3.0. That has been working fine so far in early development. However, I have an app that I can use the newer client apache-qpid-jms-0.29.0 and its fine when I create one connection.

Not sure how to use failover_exchange

I'm using qpid-broker-j-7.0.1, qpid-jms-amqp-0-x-6.3.0 and JDK 1.8. I have HA setup for broker-j and have been using failover of roundrobin for my client connections and that's been working fine. I was wanting to see the difference when using failover_exchange though. When I try that I get

Re: Stopping JMS Connection with unprocessed prefetched messages results in message moved to DLQ

I think I found why this behavior was occurring but I think I might have uncovered a bug with JMQ queue browsing... I tested with another source queue and there were no messages were being moved to the DLQ for that queue - the stayed on the source queue after the connection was closed and that is

Re: Stopping JMS Connection with unprocessed prefetched messages results in message moved to DLQ

I just ran another test where I set the url to have a maxprefetch of 0: String brokerUrl = "amqp:///spgqpiddev?maxprefetch='0'='tcp://spgappdevmutil:5672'"; And it still ended up moving 2 messages to the DLQ after the connection was stopped. I'm really confused about this behavior. -- Sent

Stopping JMS Connection with unprocessed prefetched messages results in message moved to DLQ

I'm using qpid-broker-j-7.0.1, qpid-jms-amqp-0-x-6.3.0 and JDK 1.8. We have a Java app that using using a JMS MessageListener to consume message from a Queue. Occasionally we want to stop message consumption on the Listener and then restart it. To stop message consumption I simply call the

qpid-broker-j-7.0.1 Simple LDAP and Group Providers

I'm trying to get Simple LDAP setup with qpid-broker-j-7.0.1. I noticed in the documentation that you can configure group info with LDAP. If I do that how does it work in conjunction with Group Providers? I don't see a Group Provider for use with LDAP or am not understanding it. Maybe I don't

qpid-broker-j-7.0.0 failover is slow

I have HA setup for our qpid-broker-j-7.0.0 Development environment. The setup is this: - 2 Windows 2012R2 servers - on one Windows server I have 1 qpid-broker-j-7.0.0 instance - on the other Windows server I have 2 qpid-broker-j-7.0.0 instances (listening on different ports) - all

Re: JMS Client failover error stops message consumption

I have example code for the issue I am running into with session.commit() during message consumption. Here is my test code TestTxnConsumeExample.java and the debug output qpid-session-cmt-consume-error.log

Re: JMS Client failover error stops message consumption

Keith, I think part of the issue I was having is that I wasn't defining enough retry attempts in my connection url. I've noticed the server side failover usually takes up to 45 seconds and what I had set as options in the connection url didn't cover that. However, I am still having issues when

Re: JMS Client failover error stops message consumption

I changed my testing to wait 5 minutes in between stopping a node and when I did that message consumption always resumed successfully when the client failed over to the new master. I realized that the odds of a fail over occurring twice in just a couple minutes was pretty slim and not the normal

Re: JMS Client failover error stops message consumption

I have been doing more testing of different scenarios regarding transacted sessions and different acknowledgement nodes and here is what I've found regarding this topic/behavior: My initial tests (and what I provided logs for) didn't use transactions and used auto acknowledge: Session session =

Re: JMS Client failover error stops message consumption

Keith, I increased the timeout to 3 seconds and then 10 seconds and still received the error and message consumption would not continue - the log file from the test I did with 10 seconds is: qpid-dispatch-timeout.log I

JMS Client failover error stops message consumption

I'm using broker-j-7.0.0 and apache-qpid-jms-0-x-6.3.0. For broker-j I have HA setup with 3 brokers and have been testing failover by simply starting and stopping the virtual host node on a random broker. Usually failover on my simple JMS message consumer is successful and message consumption

Broker-J HA with just 2 brokers

I'm just getting started with QPid and want to setup HA with Broker-J. We are trying to replace our current ActiveMQ environment where we use a Master Slave approach for HA and just have 2 nodes running. I really want to just have 2 nodes with Broker-J also because that setup has been working

How to define RulesBased ACLs using Qpid Broker-J 7.0.0

I'm using qpid-broker-j-7.0.0 and can't find anything in the documentation (https://qpid.apache.org/releases/qpid-broker-j-7.0.0/book/Java-Broker-Security-AccessControlProviders.html) for how to define rule based ACLs. In the documentation it states: ACLFile - an older provider that

Re: qpid-jms-0.11.1 with qpid-broker-j-7.0.0

I was a little confused on the versioning and found that apache-qpid-jms-0-x-6.3.0 was a current release and it is working for us with JDK 1.7. -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html -

How to define RulesBased ACLs

I'm using qpid-broker-j-7.0.0 and can't find anything in the documentation (https://qpid.apache.org/releases/qpid-broker-j-7.0.0/book/Java-Broker-Security-AccessControlProviders.html) for how to define rule based ACLs. -- Sent from:

Can't create exchanges and queues with a dot/period (.) in name

I'm using the Web Management Console for Qpid Broker-J 7.0.0 and it isn't allowing me to create an exchange or queue with a dot/period in the name. -- Sent from:

qpid-jms-0.11.1 with qpid-broker-j-7.0.0

I am just getting started with qpid broker-j and have installed the latest release (7.0.0). I'm hoping that qpid broker-j can replace our ActiveMQ broker. We have some older JMS consumers that are using JMS 1.1 and JDK 1.7 and can't be upgraded near term so I need to use a qpid jms client at