Are you in fact talking about running Apache (the web server) as your
message seems to state, not Apache (the open source foundation) ActiveMQ
(the JMS broker)? If so, you're on the wrong mailing list. If not, then
yes, you should definitely upgrade from 4.1.2 to something produced this
decade, eve
With master you are talking about the 2.2.0-SNAPSHOT?
How do I have to provide the address? Is the (current) entry in the
broker.xml (IP:PORT) enough?
Shared storage is unfortunately no option (that is why trying to use
Artemis).
On Mon, May 15, 2017, Clebert Suconic wrote:
> that's how it shoul
> First is security settings did not change. If previous convention was to add
> 'jms.queue' and 'jms.topic' then I think migrate command can take care of it.
Agreed.
However, using anycastPrefix and multicastPrefix on your acceptor won't fix
your security settings. Those should be updated so
I'm not sure what the problem is (if anything).
Can you provide a reproducible test-case (e.g. based on one of the examples
shipped with Artemis)?
Justin
- Original Message -
From: "abhijith"
To: users@activemq.apache.org
Sent: Monday, May 15, 2017 8:11:18 PM
Subject: Re: Artemis 2.0
Yes, removing prefix is one option. My queries are
1. Shouldn't migrate cover moving security setting and diverts?
2. Is anycastPrefix and multicastPrefix working correctly? On another post
Justin had confirmed that adding them should resolve other things
3. Why does random address is printed w
Hello everyone,
Apache Artemis 1.5.5 has just been released.
We have fixed many bugs, improving performance and reliability at 1.5.5.
The website has been updated at http://activemq.apache.org/artemis/
The release notes can be found at
https://issues.apache.org/jira/secure/ReleaseNote.jspa?vers
Hello everyone,
Apache Artemis 2.1.0 has just been released.
We have fixed many bugs, improving performance and reliability at 2.1.0.
The website has been updated at http://activemq.apache.org/artemis/
The release notes can be found at
http://activemq.apache.org/artemis/release-notes-2.1.0.html
You could just remove the prefix from the security settings.
I would use Artemis 2.1 already. I'm about to send the release announce
On Mon, May 15, 2017 at 4:51 PM, abhijith wrote:
> Hi,
>
> With 1.x we had configured security settings and topic like below
>
>
>
>
>
>
Hi,
With 1.x we had configured security settings and topic like below
With my instances, I run the instance and specify STOP. So if I had a test
instance at /opt/test then I would execute /opt/test/bin/test STOP.
From: adnan [via ActiveMQ] [mailto:ml+s2283324n4726154...@n4.nabble.com]
Sent: Monday, May 15, 2017 9:46 AM
To: Billy Buzzard
Subject: RE: How do I Set
Any insight to this issue? Someone must have come across such requirement
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Run-multiple-ActiveMQ-services-on-same-server-tp4725885p4726155.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Thank you for your response.
For the most part i am able to run multiple instances of apache on a single
Linux machine. As rightly identified updated the XML files with different
port and able to process XML files through the MQ.
But when trying to stop a specific service its always stopping the
Am I right in thinking that there needs to be another instance of the
AuthorizationBroker, added into the interceptor chain, added in such a
manner so as to make ActiveMQ call it on the call to 'send' upon each of the
destination queues?
Does anyone know if / how such as thing can be done?
I know
The closest I have got so far to answering this myself is looking at
AuthorizationBroker :: addProducer, where allowedACLs is determined via
authorizationMap.getWriteACLs(info.getDestination());
...but, I am still none the wiser, as to why this is only being called for
the ingest queue and not on
I am running ActiveMQ 5.14.0, with all of the following:
* the JAAS plugin - for user authentication on connection
* a custom plugin - similar to authorizationPlugin - for user authorization
on connection per destination
* Selectors, defined in the broker config, as per
http://activemq.apache.org/v
15 matches
Mail list logo