I have added compatibility tests in 2.5.0. That should cover moving
forward.
Any other issues we can add more compatibility tests.
On Tue, May 1, 2018 at 3:03 AM michael.andre.pearce <
michael.andre.pea...@me.com> wrote:
> This seems genuine bug for the upgrade from 2.1 to 2.2 suprised no one
Thanks Tim,
Jon's example helped I'm not sure what's going on with the "c:\" protocol
but using Jon's example seems to get it reading the file.
Mike
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
AMQP messages arent classed as being 'large' or not at a protocol
level, but rather just messages which can be sent using 1 or more
message-transfer frames as needed or appropriate to the situation.
Messages can be split into multiple frames based on the servers
advertised max frame size, which it
Hi Tim,
The main reason for setting a TTL on messages is to protect the broker’s
database from filling up. If the broker does not honor that, than it is
prone to a denial-of-service. All it takes is a user that does not
acknowledge messages.
This is a very serious flaw in ActiveMQ that anyone ca
Hi Mike
I don't know if it'll help, but here is my working config from a test
server with both Active Directory and ActiveMQ running on the same server:
activemq {
org.apache.activemq.jaas.LDAPLoginModule required
debug=true
initialContextFactory=com.sun.jndi.ldap.LdapCtxFactory
c
I hate trying to troubleshoot memory usage; it's nearly impossible to do
well, especially after the fact. It's very hard to tell exactly what causes
the increase in memory.
When measuring memory, it's important to understand that top measures total
RAM, which 1) includes memory that's not on the h
On Mon, May 7, 2018 at 8:10 AM, pragmaticjdev wrote:
> I think there is some misunderstanding that I created. We don't plan to use
> activemq to populate the cache. We build the cache on cache misses. Here's
> how the overall flow looks like. Note there are multiple jvm's involved, I
> have just
I'm not an expert on NFS, but I'd have expected that the network
connectivity failure to the NFS share to be detected when the broker
attempts to read or write the file, not just when you disable connections
to it. Your description implies that you're doing the latter; what is the
behavior of the b
