One of my customers did a PoC using GPFS last fall, and everything went fine.
We chose to use NFS anyway because the environment setup for GPFS was more
complex.
> On May 24, 2016, at 8:08 AM, Naveed Hashmi
> wrote:
>
> Hi,
>
> ( I'm new to activemq) ...
>
> We run Blackboard Learn which us
Hi,
( I'm new to activemq) ...
We run Blackboard Learn which uses ActiveMQ, see link below for info ..
https://en-us.help.blackboard.com/Learn/9.1_2014_04/Administrator/070_Server_Management_and_Integrations/System_Integration/SIS/040_SIS_Integration_Admin/060_Configuring_ActiveMQ_Messaging
We
On 05/24/2016 02:07 AM, Vavricka wrote:
tabish...@gmail.com wrote
The broker won't be able to select on the MessageID as the AMQP message
ID is foreign to the broker and it must create its own internal instance
in order to properly function so the ID the client assigns wouldn't
match what the re
Nothing about your setup seems obviously wrong. Enabling JMX and using a
JMX viewer such as JConsole is typically the best way to troubleshoot
issues like these. First just check that a connection exists between B1
and B3. Then see if the subscription from B3 to B1 (or vice versa) exists
on the
Hi Tim,
it’s an omission. The feature will be completely removed with 5.14.0 and
it’s been disabled by default since 5.12.0, so 5.13.x broker that haven’t
this feature turn on explicitly are not vulnerable.
I’ll fix the announcement now to say 5.13.x so it’s future proof in case of
new 5.13 branc
Does the range of versions specified mean that the issue is already
addressed in 5.13.3, or was its omission from the range an oversight?
Tim
On May 24, 2016 2:41 AM, "Dejan Bosanac" wrote:
> There's a security vulnerability reported against Apache
> ActiveMQ 5.13.2 and older versions.
>
> Pleas
I have used discoveryuri and uri properties to set my network of brokers.
Example :
*
[…]
*
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Network-of-Brokers-with-load-balancing-tp4712
There's a security vulnerability reported against Apache
ActiveMQ 5.13.2 and older versions.
Please check the following document and see if you’re affected by the issue.
http://activemq.apache.org/security-advisories.data/CVE-2016-3088-announcement.txt
Vulnerability is similar to the one reporte
