RE: How do I Set Up Multiple ActiveMQ Services on one Windows Machine

[Tim Bain]

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, even if it doesn't solve your problem.

Tim

On May 15, 2017 8:59 AM, "adnan"  wrote:

> 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 first
> instance that was started and successfully stops the first instance, upon
> looking at the logs i could see its trying to stop the second instance but
> fails.
>
> My issue now is what else need to be modified or any other changes required
> that would ensure when i go about stopping a specific instance it only
> stops
> it instead of the instance that was first started? Any insight? We are
> using
> 4.1.2 but are open to upgrade if that helps. Validated the same in higher
> version, but the issue persists i.e. starting multiple instances and
> consuming from those MQ is fine, but when stopping it always stops the
> service that was first started.
>
> For now living with kill -9 PID. Need some help!
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/How-do-I-Set-Up-Multiple-ActiveMQ-Services-on-
> one-Windows-Machine-tp4714245p4726154.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: Artemis HA cluster with replication

[martk]

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 should work...
> 
> Try master (current version now).. it should work..
> 
> You have to provide an address that's unique for both servers, and you can
> use to validate if the local network is out. that is you need to solve
> your network issues as well.. if you split the network there's
no way araound.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Artemis-HA-cluster-with-replication-tp4725734p4726186.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Artemis 2.0 Security settings

[Justin Bertram]

> 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 that they no longer use the 
prefix since your addresses and queues no long use the prefix. The prefixes are 
mainly for legacy clients that still use the old conventions.


Justin

- Original Message -
From: "abhijith" 
To: users@activemq.apache.org
Sent: Monday, May 15, 2017 3:51:46 PM
Subject: Artemis 2.0 Security settings

Hi,

With 1.x we had configured security settings and topic like below

 






























With move to 2.x, I ran migrate1x command.  That changed my jms declaration
like below





























I see two issues with it.  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.  
To fix this I updated acceptor to add prefix

tcp://localhost:61616?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.

But still it fails giving below error message.  Notice that it is not giving
right address name

Caused by: javax.jms.JMSSecurityException: AMQ119032: User: admin does not
have permission='CREATE_DURABLE_QUEUE' on address ykkUjHVg
at
org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:412)
at
org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:322)
at
org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.createQueue(ActiveMQSessionContext.java:635)
at
org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.internalCreateQueue(ClientSessionImpl.java:1836)
at
org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.createQueue(ClientSessionImpl.java:389)
at
org.apache.activemq.artemis.jms.client.ActiveMQSession.createConsumer(ActiveMQSession.java:670)
at
org.apache.activemq.artemis.jms.client.ActiveMQSession.createConsumer(ActiveMQSession.java:359)
at
org.apache.activemq.artemis.jms.client.ActiveMQSession.createConsumer(ActiveMQSession.java:331)
at
org.apache.activemq.artemis.jms.client.ActiveMQJMSContext.createConsumer(ActiveMQJMSContext.java:371)
... 29 more
Caused by: ActiveMQSecurityException[errorType=SECURITY_EXCEPTION
message=AMQ119032: User: admin does not have
permission='CREATE_DURABLE_QUEUE' on address ykkUjHVg]
... 38 more

Please let me know if I am doing anything wrong?  Do I need to change my
address setting manually?  If I set it to generic '#' then it works fine.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Artemis-2-0-Security-settings-tp4726174.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Artemis 2.0 Security settings

[Justin Bertram]

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 Security settings

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 when permissions are not there?  This
would complicate debugging.

I will switch to 2.1.  Will any of the above issues fixed in 2.1?




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Artemis-2-0-Security-settings-tp4726174p4726183.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Artemis 2.0 Security settings

[abhijith]

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 when permissions are not there?  This
would complicate debugging.

I will switch to 2.1.  Will any of the above issues fixed in 2.1?




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Artemis-2-0-Security-settings-tp4726174p4726183.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

[ANNOUNCE] Apache Artemis 1.5.5

[Clebert Suconic]

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?version=12339947==12315920

[ANNOUNCE] Apache Artemis 2.1.0

[Clebert Suconic]

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



-- 
Clebert Suconic

Re: Artemis 2.0 Security settings

[Clebert Suconic]

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
>
>  
>
> 
> 
> 
> 
>
>
> 
> 
> 
>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> With move to 2.x, I ran migrate1x command.  That changed my jms declaration
> like below
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> I see two issues with it.  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.
> To fix this I updated acceptor to add prefix
>
>  name="netty-acceptor">tcp://localhost:61616?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.
>
> But still it fails giving below error message.  Notice that it is not giving
> right address name
>
> Caused by: javax.jms.JMSSecurityException: AMQ119032: User: admin does not
> have permission='CREATE_DURABLE_QUEUE' on address ykkUjHVg
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:412)
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:322)
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.createQueue(ActiveMQSessionContext.java:635)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.internalCreateQueue(ClientSessionImpl.java:1836)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.createQueue(ClientSessionImpl.java:389)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQSession.createConsumer(ActiveMQSession.java:670)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQSession.createConsumer(ActiveMQSession.java:359)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQSession.createConsumer(ActiveMQSession.java:331)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQJMSContext.createConsumer(ActiveMQJMSContext.java:371)
> ... 29 more
> Caused by: ActiveMQSecurityException[errorType=SECURITY_EXCEPTION
> message=AMQ119032: User: admin does not have
> permission='CREATE_DURABLE_QUEUE' on address ykkUjHVg]
> ... 38 more
>
> Please let me know if I am doing anything wrong?  Do I need to change my
> address setting manually?  If I set it to generic '#' then it works fine.
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/Artemis-2-0-Security-settings-tp4726174.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.



-- 
Clebert Suconic

Artemis 2.0 Security settings

[abhijith]

Hi,

With 1.x we had configured security settings and topic like below

 






























With move to 2.x, I ran migrate1x command.  That changed my jms declaration
like below





























I see two issues with it.  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.  
To fix this I updated acceptor to add prefix

tcp://localhost:61616?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.

But still it fails giving below error message.  Notice that it is not giving
right address name

Caused by: javax.jms.JMSSecurityException: AMQ119032: User: admin does not
have permission='CREATE_DURABLE_QUEUE' on address ykkUjHVg
at
org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:412)
at
org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:322)
at
org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.createQueue(ActiveMQSessionContext.java:635)
at
org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.internalCreateQueue(ClientSessionImpl.java:1836)
at
org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.createQueue(ClientSessionImpl.java:389)
at
org.apache.activemq.artemis.jms.client.ActiveMQSession.createConsumer(ActiveMQSession.java:670)
at
org.apache.activemq.artemis.jms.client.ActiveMQSession.createConsumer(ActiveMQSession.java:359)
at
org.apache.activemq.artemis.jms.client.ActiveMQSession.createConsumer(ActiveMQSession.java:331)
at
org.apache.activemq.artemis.jms.client.ActiveMQJMSContext.createConsumer(ActiveMQJMSContext.java:371)
... 29 more
Caused by: ActiveMQSecurityException[errorType=SECURITY_EXCEPTION
message=AMQ119032: User: admin does not have
permission='CREATE_DURABLE_QUEUE' on address ykkUjHVg]
... 38 more

Please let me know if I am doing anything wrong?  Do I need to change my
address setting manually?  If I set it to generic '#' then it works fine.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Artemis-2-0-Security-settings-tp4726174.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

RE: How do I Set Up Multiple ActiveMQ Services on one Windows Machine

[bbuzzard]

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 Up Multiple ActiveMQ Services on one Windows Machine

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 first 
instance that was started and successfully stops the first instance, upon 
looking at the logs i could see its trying to stop the second instance but 
fails.

My issue now is what else need to be modified or any other changes required 
that would ensure when i go about stopping a specific instance it only stops it 
instead of the instance that was first started? Any insight? We are using 4.1.2 
but are open to upgrade if that helps. Validated the same in higher version, 
but the issue persists i.e. starting multiple instances and consuming from 
those MQ is fine, but when stopping it always stops the service that was first 
started.

For now living with kill -9 PID. Need some help!

If you reply to this email, your message will be added to the discussion below:
http://activemq.2283324.n4.nabble.com/How-do-I-Set-Up-Multiple-ActiveMQ-Services-on-one-Windows-Machine-tp4714245p4726154.html
To unsubscribe from How do I Set Up Multiple ActiveMQ Services on one Windows 
Machine, click 
here.
NAML




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/How-do-I-Set-Up-Multiple-ActiveMQ-Services-on-one-Windows-Machine-tp4714245p4726168.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Run multiple ActiveMQ services on same server

[adnan]

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.

RE: How do I Set Up Multiple ActiveMQ Services on one Windows Machine

[adnan]

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 first
instance that was started and successfully stops the first instance, upon
looking at the logs i could see its trying to stop the second instance but
fails.

My issue now is what else need to be modified or any other changes required
that would ensure when i go about stopping a specific instance it only stops
it instead of the instance that was first started? Any insight? We are using
4.1.2 but are open to upgrade if that helps. Validated the same in higher
version, but the issue persists i.e. starting multiple instances and
consuming from those MQ is fine, but when stopping it always stops the
service that was first started.

For now living with kill -9 PID. Need some help!



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/How-do-I-Set-Up-Multiple-ActiveMQ-Services-on-one-Windows-Machine-tp4714245p4726154.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: where is a producer authorized for writing to a virtual destination?

[Vince Cole]

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 how to write a plugin, but the framework around them which loads them
in and calls them, is still a mystery to me...



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/where-is-a-producer-authorized-for-writing-to-a-virtual-destination-tp4726149p4726151.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: where is a producer authorized for writing to a virtual destination?

[Vince Cole]

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 any of the destination queues. I can't see where
it is (not) being called from...?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/where-is-a-producer-authorized-for-writing-to-a-virtual-destination-tp4726149p4726150.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

where is a producer authorized for writing to a virtual destination?

[Vince Cole]

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/virtual-destinations.html ("Using filtered
destinations").

Having tested it, I see that when a producer sends a message to a virtual
destination (the 'ingest' queue) on the broker which is configured with
Selectors to forward a copy of the message to one or more 'destination'
queues, ActiveMQ first checks that the producer has write permission on the
ingest queue but it does NOT check if the producer has write permission on
any of the destination queues.

I can't figure out where in the ActiveMQ codebase to look at the code, to
work out if / how it would be possible to enable this extra checking.

I have looked at CompositeDestinationFilter::send - I see that ActiveMQ
iterates over the set of destinations for which the Selectors are matched on
an incoming message, and sends a copy of the message to each one - but I
can't see where, outside of this class, ActiveMQ makes a decision to check
for write permissions on the ingest queue, but NOT on any of the destination
queues. 

Can anyone shed any light on this please? 
I am hoping that a VirtualDestinationInterceptors config setting somewhere
can be changed to enable the destination checks, otherwise I am going to
have to write my own CompositeDestinationFilter ?




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/where-is-a-producer-authorized-for-writing-to-a-virtual-destination-tp4726149.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.