The Apache Qpid (http://qpid.apache.org) community is pleased to
announce the immediate availability of Apache Qpid Dispatch 1.1.0
Qpid Dispatch is a router for the Advanced Message Queuing Protocol 1.0
(AMQP 1.0, ISO/IEC 19464, http://www.amqp.org). It provides a flexible
and scalable interconnec
Hi Franta,
Sleepycat is not required to run Qpid Broker-J 7.0.
You can ran Qpid Broker-J 7.0 using Derby or JDBC message stores instead of BDB.
You just need to provide an initial virtualHostInitialConfiguration
where type of Virtual host is set to DERBY or JDBC. For example,
"virtualHostInitialCo
+1
* built from source distribution and ran all tests
* ran Qpid Broker-J integration tests with staged 0.33.0 maven
artefacts using profiles java-mms.1-0 and java-bdb.1.0
* verified checksums and signatures
On 11 June 2018 at 18:32, Robbie Gemmell wrote:
> Hi folks,
>
> I have put together a
+1
I performed the following tests:
* verified checksums and signature (making sure that md5 checksums are
not included any more)
* built broker from sources with running integration tests using
java-bdb.0-9 profile
* ran JMS tests publishing large messages exceeding maximum size limits
* ran JMS
Hi Robbie,
I tested for issue "https://issues.apache.org/jira/browse/QPIDJMS-386";. It
is working fine.
Regards,
Abhishek Kumar
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
-
To unsubscribe
Hi all,
I created an RC2 built for a Qpid Broker-J 7.0.5 release.
Please give it a test out and vote accordingly.
The source and binary bundles can be found at
https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.0.5-rc2
The maven artifacts are also staged for now at:
https://repository.apache
Hi Robbie,
Good Morning !! Thank you so much for your both reply. With your replies,
our doubts has been cleared and concluded for reliability. We have chosen
"forceSync + send(without listener) + failover(if required)".
This will give us 1/3 performance on comparison with Async but beneficial
Regarding the actual "following through" on the deprecation:
If I understand correctly, the linearstore ORM code relies on classes from
the Berkeley DB library; with legacystore gone, the only purpose of the
dependency on BDB would be for this mapping even though BDB storage would
no longer be in
+1 ... I used the staging repo and run the client against different
versions of Qpid C++ broker. All seems to work fine.
On Mon, Jun 11, 2018 at 7:32 PM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a spin for a 0.33.0 Qpid JMS client release,
> please give it a test out and vote acc
