Github user michaelandrepearce commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/2427#discussion_r235842374
--- Diff:
artemis-core-client/src/main/java/org/apache/activemq/artemis/core/message/impl/CoreMessage.java
---
@@ -578,34 +567,41 @@
Hi,
Yes, correctly tuned, KahaDB works fine with high volume. I'm using it
in several productions (with master/slave and network of brokers).
Regards
JB
On 22/11/2018 17:38, rododendro wrote:
> Hi JB, thank you for your reply.
>
> Cassandra does not support traditional RDBMS transactions (nor
Hi JB, thank you for your reply.
Cassandra does not support traditional RDBMS transactions (nor XA) so a
Cassandra Persistence Adapter for ActiveMQ would be someway limited.
Nevertheless a such connector looks very interesting to me for uses cases
which don't need XA, it would allow an extremely
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/319
---
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/320
---
Hi Ivan,
I think it's just a question of interest. I worked on the CassandraIO in
Apache Beam and I think we have to be careful the way we are using the
collection for have max performance.
Regards
JB
On 22/11/2018 15:40, rododendro wrote:
> Hi all,
> apart from the old and discontinued
Hi all,
apart from the old and discontinued QSandra project it seems that no one is
interested in a Cassandra persistence adapter, is there any specific reason
to that?
Ivan
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/321
---
GitHub user coheigea opened a pull request:
https://github.com/apache/activemq/pull/321
Enable secure processing on all DocumentBuilderFactory.newInstance()
Good security practices say that all DocumentBuilderFactory instances
should enable the secure processing feature and disable
Hi Christopher,
I don't ask for a release now, but relatively soon.
So, roughly a month before 5.15.9 is fine for me.
I think Karaf users can live with ActiveMQ 5.15.6 for now.
By the way, I tested the fix on Karaf 4.1.x and 4.2.x, both with
ActiveMQ 5.16.0-SNAPSHOT (master) and
I would say in this case a user could just downgrade to 5.15.6 so I don't
know that this is a truly critical fix we need to rush out super fast.
Other fixes we have rushed out were because of possible data store
corruption, etc.
That being said we can still do another release relatively soon but
GitHub user jbonofre opened a pull request:
https://github.com/apache/activemq/pull/320
[AMQ-7076] Does not define spring-legacy repository by default in Actâ¦
â¦iveMQ Karaf features repo, and let the user add it
You can merge this pull request into a Git repository by running:
GitHub user jbonofre opened a pull request:
https://github.com/apache/activemq/pull/319
[AMQ-7076] Does not define spring-legacy repository by default in Actâ¦
â¦iveMQ Karaf features repo, and let the user add it
You can merge this pull request into a Git repository by running:
Hi guys,
For ActiveMQ 5.15.7, I did a change the ActiveMQ Karaf features XML to
simplify the installation of ActiveMQ in Karaf (especially for Karaf 4.2.x).
Unfortunately, this change is causing issue for Karaf 4.0.x & 4.1.x users.
I'm working on a fix right now
14 matches
Mail list logo
