No, the python tooling commands like qpid-config were only for the C++ broker and though some of it will be using intrinsic AMQP 0-x commands, much of it uses a management framework (QMF) that Broker-J does not support.
On Thu, 12 Feb 2026 at 17:19, David Cotton (EXT) <[email protected]> wrote: > > Windows environment. Running Apache Broker-J (Java implementation of the > broker) > > I have access to another Broker (It was built by another department in the > company) and the qpid-config.py utility works well with that broker. > Recently, there's been a switch to having multiple brokers. (Company > politics, don't ask why don't I get the broker software from the other > department). The easiest implementation is the Broker-J version from Apache. > However would still like to use the python tool. > > I'm using the command: qpid-config.py -b localhost:10000 queues -r > > I configured my broker to support these protocols: > AMQP_1_0, AMQP_0_8, AMQP_0_10, AMQP_0_9, AMQP_0_9_1 > Anonymous authentication is enabled. > > I added a qmf.default.topic (topic) exchange via the web configuration tool. > (Got an error from the tool). > > Now getting the error: > Failed: InternalError: Traceback (most recent call last): > File > "C:\BNSF\ITCM\QPID\qpid-python-0.30\qpid-python-0.30\qpid\messaging\driver.py", > line 670, in write op.dispatch(self) > File "C:\BNSF\ITCM\QPID\qpid-python-0.30\qpid-python-0.30\qpid\ops.py", line > 84, in dispatch getattr(target, handler)(self, *args) > AttributeError: Engine instance has no attribute 'do_message_set_flow_mode' > > Since the right protocol is enabled, I'm thinking there's a configuration > issue. > > TIA --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
