Looking at jconsole (connected to the running Qpid broker), it appears that
it exposes a Map under java.lang -> Runtime -> Attributes ->
SystemProperties. Is this something that I can depend on always being
available? This is Qpid version 7.0.6, which no longer supports management
over JMX, but w
Hello Qpid maintainers,
My organization uses Qpid, and we occasionally deploy configuration changes
that we track using a build number that we generate internally. We would
like to find a way to expose this build number so that our application can
access it to see what "build" the Qpid broker is
Hello All,
Please cast your vote on this thread to release RC1 as the
official Qpid Dispatch Router version 1.5.0.
RC1 of Qpid Dispatch Router version 1.5.0 can be found here:
https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.5.0-rc1/
The following features, improvements, and bug
I noticed just now that the GitHub PR integration behaviour had
changed since the migration, with comments not being left on the JIRA
for PR open/close/comments etc, but rather 10minute time-spent entries
made to the Work Log instead to carry activity from the PR. I asked
infra about it and theyve
Hi folks,
I built release artefacts for Qpid Broker-J version 7.1.0 RC1.
Please, give them a test out and vote accordingly.
The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.1.0-rc1/
The maven artifacts are also staged for now at:
https://
Hi Robbie,
We need one suggestion from you for handling JMS exception in better way.
Pre Conditions- We have
a) One javax.jms.Connection
b) Registered exception listner. So we will get connection related exception
on "onException" block
c) 50+ javax.jms.Session
d) 32+ javax.jms.MessageProducer
+1 ... I run the client against different versions of the C++ broker and
all seems to be ok. (I used the staging repository)
On Mon, Dec 17, 2018 at 12:47 PM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a spin for a 0.40.0 Qpid JMS client release,
> please give it a test out and vot
+1
I tested release artefacts as follows:
* verified signatures and checksums
* built and ran unit tests successfully from source bundle
* ran successfully Qpid Broker-J system tests using staged release
artefacts (mvn clean install -DskipTests -DskipITs=false
-Dnetty-version=4.1.32.Final -Dqpid-j
