Re: Artemis - audit logging and anonymous user

[andytaylor]

https://issues.apache.org/jira/browse/ARTEMIS-2648

feel free to add extra requirements



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Artemis - audit logging and anonymous user

[andytaylor]

just fyi, Im currently doing some workaround this to improve audit logging.
basically being able to log the user and ip address in certain events and
also refining the granularity, should have something in a week or so.




--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Artemis activemq with jconsole doesn't show topics management

[andytaylor]

Internally Artemis has no notion of topics, only addresses and queues, JMS
topics are an abstraction built on top of these in the client. I would read
the addressing chapter of the user manual to understand how a topic maps
internally on to an address and a queue

On 3 August 2017 at 10:45, aragoubi [via ActiveMQ] <
ml+s2283324n4729214...@n4.nabble.com> wrote:

> I have a standalone artemis activemq broker.
> I start the broker, and I open jconsole in order to see and manage
> activemq, but I am not seeing topic, I can see only queues.
> Before, I was using activemq, and I was able to see topics through
> jconsole.
> jconsole.png
> 
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/Artemis-activemq-
> with-jconsole-doesn-t-show-topics-management-tp4729214.html
> To start a new topic under ActiveMQ - User, email
> ml+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Re-Artemis-activemq-with-jconsole-doesn-t-show-topics-management-tp4729216.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: setting activemq artemis load balanced and HA

[andytaylor]

take a look at one of the many HA and cluster examples
https://github.com/apache/activemq-artemis/tree/master/examples/features

On 2 July 2017 at 01:42, hassan khraim [via ActiveMQ] <
ml+s2283324n4728181...@n4.nabble.com> wrote:

> Hi,
>
>
> I am trying to set  activemq artemis as load balanced and HA, can someone
> help me to achieve that.
>
>
>
> Thanks
>
>
>
>
> Sent from Outlook
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/setting-activemq-
> artemis-load-balanced-and-HA-tp4728181.html
> To start a new topic under ActiveMQ - User, email
> ml+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/setting-activemq-artemis-load-balanced-and-HA-tp4728181p4728182.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: why AvtiveMq is slowly than Kafka?

[andytaylor]

well said

On 5 June 2017 at 12:31, christopher.l.shannon [via ActiveMQ] <
ml+s2283324n4727011...@n4.nabble.com> wrote:

> You can't compare Kafka to a JMS type message broker.  Kafka is completely
> different.
>
> Kafka is a system that scales horizontally and is essentially a big
> write-ahead log and breaks up the topics into partitions across many
> servers so they can be scanned concurrently.   This allows insane message
> rates but the trade off is that the feature set is much less...there are
> no
> features like message acknowledgement (messages are not deleted, they are
> aged off and a client can seek to any point in the log), message
> expiration, scheduled messages, transactions (although transaction support
> is currently being worked on) etc which offloads a lot of work that a
> typical message broker has to do.   Kafka clusters can scale to thousands
> of nodes and handle millions of messages per second.
>
> Any standalone broker like ActiveMQ, Artemis, etc is going to be measured
> at a rate of thousands per second.
>
> On Sat, Jun 3, 2017 at 3:13 PM, Clebert Suconic <[hidden email]
> >
> wrote:
>
> > For the use case you're after. (No hard syncs). Mmap is a good
> candidate.
> > Probably better.
> >
> >
> > Libaio was engineered the case where you hard sync with callbacks from
> the
> > Linux os
> > On Sat, Jun 3, 2017 at 12:46 PM wangqinghuan <[hidden email]
> > wrote:
> >
> > > hi clebertsuconic:
> > > i read the blog
> > > https://activemq.apache.org/artemis/docs/2.1.0/persistence.html
> > > By default Apache ActiveMQ Artemis will try and use an AIO journal.But
> it
> > > seems like that Mmap is also a good implemention.which one gives more
> > > performance?
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > > http://activemq.2283324.n4.nabble.com/why-AvtiveMq-is-
> slowly-than-Kafka-
> > tp4726911p4726992.html
> > > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> > >
> > --
> > Clebert Suconic
> >
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/why-AvtiveMq-is-slowly-than-Kafka-
> tp4726911p4727011.html
> To start a new topic under ActiveMQ - User, email
> ml+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/why-AvtiveMq-is-slowly-than-Kafka-tp4726911p4727048.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Artemis 2.0: JMS seems to create an address/queue on jmsSession.createProducer() calls

[andytaylor]

nothing directly maps to JMS objects at the broker side, the addressing
schema is generic to be multi protocol, all of the JMS bits are just a
facade at the client. But in essence a message is sent to an address, if
its anycast it will pick 1 queue and if it is multicast it sends to all the
queues. In short a jms queue is:



   

 

and a JMS topic is:



 

>From a consumer pov the protol decides how how it will consume, for JMS
Durable Subscriptions for example it will create a queue using its client
id as the queue name, for AMQP its similar.



On 1 April 2017 at 14:14, titou10 [via ActiveMQ] <
ml-node+s2283324n4724471...@n4.nabble.com> wrote:

> andytaylor wrote
> Im not sure I mentioned a topic, however for clarification jms queue =
> anycast and jms topic = multicast in general
>
> OK. q1 = "anycast" in this case, so it should be a JMS queue, right? The
> doc with this example says it is a queue, not a topic nor an alias...
>
> andytaylor wrote
> > > For the second exception, this is because you send to an address not a
> queue, so it tries to create a new queue under the address q1 which fails
> because it already exists under address address.foo
>
> With this in broker.xml:   
>   
> 
>   
>
>   
>
>
>   
> 
>   
>
>
> From a client, using the "activemq.management" queue,
> Calling ResourceNames.BROKER::queueNames returns this list of queues:-
> orders
>   -> JMS createQueue + createProducer + createBrowser = OK
> - q1
>   -> JMS createProducer fails with "ActiveMQQueueExistsException:
> AMQ119019: Queue already exists q1"
> - 1358977c-57dd-4e29-9a3d-65200f437c44
>   -> Temporary queue
>   -> JMS createQueue + createProducer + createBrowser = seems OK
>   -> Sometime calling ResourceNames.QUEUE::messageCount fails with the
> following exception (Another problem I guess):
>   java.lang.IndexOutOfBoundsException: readerIndex(19) + length(1)
> exceeds writerIndex(19): UnpooledDuplicatedByteBuf(ridx: 19, widx: 19,
> cap: 260, unwrapped: UnpooledUnsafeHeapByteBuf(ridx: 0, widx: 260, cap:
> 260))
>
> Q: how do I distinguish here between
> - queues that directly map to "JMS queues" like "orders"
> - queues which are "adresses but not queues" (quoting you) like "q1"
> - others queues like "1358..." that seems to act like a regular "JMS
> queues" but do not respond well to some admin commands
>
> Calling ResourceNames.BROKER::addressNames returns this list of addresses:-
> pubsub.foo deliveryMode ["MULTICAST"] queues:[]
>   -> JMS createTopic + createProducer + MessageConsumer.setMessageListener
> = OK
> - orders deliveryMode ["ANYCAST"] queues:[orders]
>   -> JMS createQueue + createProducer + createBrowser = OK
> - address.foo deliveryMode: ["ANYCAST"] queues: [q1]
>   -> JMS createQueue + createProducer = OK
>   -> JMS createBrowser fails with "ActiveMQNonExistentQueueException:
> AMQ119017: Queue address.foo does not exist"
>   -> JMS createTopic + createProducer + MessageConsumer.setMessageListener
> = OK
>   -> so it acts like a Topic even if deliveryMode=ANYCAST!
> - 1358977c-57dd-4e29-9a3d-65200f437c44 deliveryMode: ["ANYCAST"] queues:
> [1358977c-57dd-4e29-9a3d-65200f437c44] temporary
>   -> see above
>
> To summarize.- what Artemis "objects" map to JMS queues?
>   -> the "queues" returned by ResourceNames.BROKER::queueNames
>   -> ...except the ones like "q1". how to distinguish those ones ??
> - what Artemis "objects" map to JMS topics?
>   -> the "addresses" returned by ResourceNames.BROKER::addressNames with
> deliveryMode=MULTICAST
>   -> some "addresses" returned by ResourceNames.BROKER::addressNames with
> deliveryMode=ANYCAST like "address.foo" above.
>  -> how to distinguish the one in that category ??
>
> Is that correct?
>
> Thanks
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/Artemis-2-0-JMS-
> seems-to-create-an-address-queue-on-jmsSession-createProducer-calls-
> tp4724415p4724471.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2341805&code=YW5keS50YXlsczY3QGdtYWlsLmNvbXwyMzQxODA1fC05MDE1

Re: Artemis 2.0: JMS seems to create an address/queue on jmsSession.createProducer() calls

[andytaylor]

Im not sure I mentioned a topic, however for clarification jms queue =
anycast and jms topic = multicast in general

On 31 March 2017 at 13:30, titou10 [via ActiveMQ] <
ml-node+s2283324n4724423...@n4.nabble.com> wrote:

> I must admit I'm lost here..
>
> The example is from https://activemq.apache.org/
> artemis/docs/2.0.0/address-model.html, section "Point-to-Point Address
> multiple
> Queues" and there is no question about Topics here
>
> Do you say that q1 is a Topic from a JMS perspective, even if it is
> attached to an "ANYCAST" Address?
>
> Quoting the section "Mapping JMS Concepts to the Core API"
>
> "A JMS topic is implemented in core as an address with name=(the topic
> name) and with a MULTICAST routing type with zero or more
> queues bound to it. Each queue bound to that address represents a topic
> subscription.Likewise, a JMS queue is implemented as an
> address with name=(the JMS queue name) with an ANYCAST routing type
> assocatied with it."
>
> Please help me understand the rules to determine if an "Artemis Address"
> is a JMS Topic or a JMS Queue and also how to determine if
> an "Artemis Queue" is a JMS Topic or a JMS Queue because the definition
> above is either incomplete or the assumption on q1 are wrong
>
> Thanks !
>
>
>
>
> Le 31/03/2017 à 08:12, andytaylor a écrit :
>
> > It does adhere to the JMS spec, the destinations are just created
> > dynamically not explicitly because of the call.NB mos vendors do this
> >
> > For the second exception, this is because you send to an address not a
> > queue, so it tries to create a new queue under the address q1 which
> fails
> > because it already exists under address address.foo
> >
> > On 31 March 2017 at 13:05, titou10 [via ActiveMQ] <
> > [hidden email] <http:///user/SendEmail.jtp?type=node&node=4724423&i=0>>
> wrote:
> >
> >> OK...
> >>
> >> I'm not sure that setting the server in this mode respects the JMS
> >> specs...maybe it may be considered as a JMS extension?
> >>
> >> And what about the ActiveMQQueueExistsException[errorType=QUEUE_EXISTS
> >> message=AMQ119019: Queue already exists q1]exception for the
> >> second case ?
> >>
> >>
> >> Le 31/03/2017 à 07:51, andytaylor a écrit :
> >>
> >>> This happens if you have auto create for queues/topics configured on
> the
> >>> address settings, you can turn this off if you desire
> >>>
> >>> On 31 March 2017 at 12:17, titou10 [via ActiveMQ] <
> >>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=4724421&i=0>>
>
> >> wrote:
> >>>> FYI, same code to an IBM MQ server fails as expected with an
> >>>> "UNKNOWN_OBJECT_NAME" on the createProducer() method
> >>>>
> >>>> com.ibm.mq.MQException: JMSCMQ0001: IBM MQ call failed with compcode
> >> '2'
> >>>> ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME').
> >>>>   at com.ibm.msg.client.wmq.common.internal.Reason.
> >>>> createException(Reason.java:203) ~[na:na]
> >>>>   at com.ibm.msg.client.wmq.internal.WMQMessageProducer.
> >>>> checkJmqiCallSuccess(WMQMessageProducer.java:1248) ~[na:na]
> >>>>   at com.ibm.msg.client.wmq.internal.WMQMessageProducer.
> >>>> checkJmqiCallSuccess(WMQMessageProducer.java:1205) ~[na:na]
> >>>>   at com.ibm.msg.client.wmq.internal.WMQMessageProducer.
> >>>> access$800(WMQMessageProducer.java:75) ~[na:na]
> >>>>   at com.ibm.msg.client.wmq.internal.WMQMessageProducer$
> >>>> SpiIdentifiedProducerShadow.initialise(WMQMessageProducer.java:801)
> >>>> ~[na:na]
> >>>>   at com.ibm.msg.client.wmq.internal.WMQMessageProducer.<
> >>>> init>(WMQMessageProducer.java:1181) ~[na:na]
> >>>>   at com.ibm.msg.client.wmq.internal.WMQSession.
> >>>> createProducer(WMQSession.java:1077) ~[na:na]
> >>>>   at com.ibm.msg.client.jms.internal.JmsSessionImpl.
> >>>> createProducer(JmsSessionImpl.java:1498) ~[na:na]
> >>>>   at com.ibm.mq.jms.MQSession.createProducer(MQSession.java:661)
>
> >>>> ~[na:na]
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> If you reply to this em

Re: Artemis 2.0: JMS seems to create an address/queue on jmsSession.createProducer() calls

[andytaylor]

It does adhere to the JMS spec, the destinations are just created
dynamically not explicitly because of the call.NB mos vendors do this

For the second exception, this is because you send to an address not a
queue, so it tries to create a new queue under the address q1 which fails
because it already exists under address address.foo

On 31 March 2017 at 13:05, titou10 [via ActiveMQ] <
ml-node+s2283324n4724421...@n4.nabble.com> wrote:

> OK...
>
> I'm not sure that setting the server in this mode respects the JMS
> specs...maybe it may be considered as a JMS extension?
>
> And what about the ActiveMQQueueExistsException[errorType=QUEUE_EXISTS
> message=AMQ119019: Queue already exists q1]exception for the
> second case ?
>
>
> Le 31/03/2017 à 07:51, andytaylor a écrit :
>
> > This happens if you have auto create for queues/topics configured on the
> > address settings, you can turn this off if you desire
> >
> > On 31 March 2017 at 12:17, titou10 [via ActiveMQ] <
> > [hidden email] <http:///user/SendEmail.jtp?type=node&node=4724421&i=0>>
> wrote:
> >
> >> FYI, same code to an IBM MQ server fails as expected with an
> >> "UNKNOWN_OBJECT_NAME" on the createProducer() method
> >>
> >> com.ibm.mq.MQException: JMSCMQ0001: IBM MQ call failed with compcode
> '2'
> >> ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME').
> >>  at com.ibm.msg.client.wmq.common.internal.Reason.
> >> createException(Reason.java:203) ~[na:na]
> >>  at com.ibm.msg.client.wmq.internal.WMQMessageProducer.
> >> checkJmqiCallSuccess(WMQMessageProducer.java:1248) ~[na:na]
> >>  at com.ibm.msg.client.wmq.internal.WMQMessageProducer.
> >> checkJmqiCallSuccess(WMQMessageProducer.java:1205) ~[na:na]
> >>  at com.ibm.msg.client.wmq.internal.WMQMessageProducer.
> >> access$800(WMQMessageProducer.java:75) ~[na:na]
> >>  at com.ibm.msg.client.wmq.internal.WMQMessageProducer$
> >> SpiIdentifiedProducerShadow.initialise(WMQMessageProducer.java:801)
> >> ~[na:na]
> >>  at com.ibm.msg.client.wmq.internal.WMQMessageProducer.<
> >> init>(WMQMessageProducer.java:1181) ~[na:na]
> >>  at com.ibm.msg.client.wmq.internal.WMQSession.
> >> createProducer(WMQSession.java:1077) ~[na:na]
> >>  at com.ibm.msg.client.jms.internal.JmsSessionImpl.
> >> createProducer(JmsSessionImpl.java:1498) ~[na:na]
> >>  at com.ibm.mq.jms.MQSession.createProducer(MQSession.java:661)
>
> >> ~[na:na]
> >>
> >>
> >>
> >> --
> >> If you reply to this email, your message will be added to the
> discussion
> >> below:
> >> http://activemq.2283324.n4.nabble.com/Artemis-2-0-JMS-
> >> seems-to-create-an-address-queue-on-jmsSession-createProducer-calls-
> >> tp4724415p4724416.html
> >> To start a new topic under ActiveMQ - User, email
> >> [hidden email] <http:///user/SendEmail.jtp?type=node&node=4724421&i=1>
> >> To unsubscribe from ActiveMQ - User, click here
> >> <
> >> .
> >> NAML
> >> <http://activemq.2283324.n4.nabble.com/template/
> NamlServlet.jtp?macro=macro_viewer&id=instant_html%
> 21nabble%3Aemail.naml&base=nabble.naml.namespaces.
> BasicNamespace-nabble.view.web.template.NabbleNamespace-
> nabble.view.web.template.NodeNamespace&breadcrumbs=
> notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> >>
> >
> >
> >
> > --
> > View this message in context: http://activemq.2283324.n4.
> nabble.com/Artemis-2-0-JMS-seems-to-create-an-address-queue-on-jmsSession-
> createProducer-calls-tp4724415p4724418.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/Artemis-2-0-JMS-
> seems-to-create-an-address-queue-on-jmsSession-createProducer-calls-
> tp4724415p4724421.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2341805&code=YW5keS50YXlsczY3QGdtYWlsLmNvbXwyMzQxODA1fC05MDE1NDk1MzM=>
> .
> NAML
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Artemis-2-0-JMS-seems-to-create-an-address-queue-on-jmsSession-createProducer-calls-tp4724415p4724422.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Do address-settings merge?

[andytaylor]

Its done in order, so the second entry will inherit from any previous entry
that matches or be over riden

On 31 March 2017 at 08:17, jelmer [via ActiveMQ] <
ml-node+s2283324n4724411...@n4.nabble.com> wrote:

> Hi all,
>
> We as team are planning to use active mq artemis 1.5.3 in a production
> environment. While preparing our configuration, we stumbled along some
> questions, that was not answered in the documentation. The questions are:
> Do address-settings merge when multiple matchers match. EG would the
> following queue with as name "jms.queue.queueName"  also get the settings
> that match "#"?
>
> Would the settings for the matcher "#" overwrite the settings for matcher
> "jms.queue.queueName" or is this order dependent?
>
> Kind regards,
> Jelmer v. Amen
>
> Example configuration:
>
>   
>  
>5000
>  
>
>  
> jms.queue.DLQ
> jms.queue.ExpiryQueue
> 10 history-day-limit>
> 1
> 0
> 10485760
> 500
> 1000
> PAGE
>  
>   
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/Do-address-
> settings-merge-tp4724411.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Do-address-settings-merge-tp4724411p4724419.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Artemis 2.0: JMS seems to create an address/queue on jmsSession.createProducer() calls

[andytaylor]

This happens if you have auto create for queues/topics configured on the
address settings, you can turn this off if you desire

On 31 March 2017 at 12:17, titou10 [via ActiveMQ] <
ml-node+s2283324n4724416...@n4.nabble.com> wrote:

> FYI, same code to an IBM MQ server fails as expected with an
> "UNKNOWN_OBJECT_NAME" on the createProducer() method
>
> com.ibm.mq.MQException: JMSCMQ0001: IBM MQ call failed with compcode '2'
> ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME').
> at com.ibm.msg.client.wmq.common.internal.Reason.
> createException(Reason.java:203) ~[na:na]
> at com.ibm.msg.client.wmq.internal.WMQMessageProducer.
> checkJmqiCallSuccess(WMQMessageProducer.java:1248) ~[na:na]
> at com.ibm.msg.client.wmq.internal.WMQMessageProducer.
> checkJmqiCallSuccess(WMQMessageProducer.java:1205) ~[na:na]
> at com.ibm.msg.client.wmq.internal.WMQMessageProducer.
> access$800(WMQMessageProducer.java:75) ~[na:na]
> at com.ibm.msg.client.wmq.internal.WMQMessageProducer$
> SpiIdentifiedProducerShadow.initialise(WMQMessageProducer.java:801)
> ~[na:na]
> at com.ibm.msg.client.wmq.internal.WMQMessageProducer.<
> init>(WMQMessageProducer.java:1181) ~[na:na]
> at com.ibm.msg.client.wmq.internal.WMQSession.
> createProducer(WMQSession.java:1077) ~[na:na]
> at com.ibm.msg.client.jms.internal.JmsSessionImpl.
> createProducer(JmsSessionImpl.java:1498) ~[na:na]
> at com.ibm.mq.jms.MQSession.createProducer(MQSession.java:661)
> ~[na:na]
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/Artemis-2-0-JMS-
> seems-to-create-an-address-queue-on-jmsSession-createProducer-calls-
> tp4724415p4724416.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Artemis-2-0-JMS-seems-to-create-an-address-queue-on-jmsSession-createProducer-calls-tp4724415p4724418.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

[andytaylor]

Can you make sue your messages are persistent. If they are try turning
scaledown off and see if there are any messages in the journal when the
back up comes live. If you are still having problems send me you're
configuration and I will have a look tomorrow

Andy

On 1 December 2016 at 17:07, grishezz [via ActiveMQ] <
ml-node+s2283324n4719679...@n4.nabble.com> wrote:

> You can see the entire logs, as well as the configuration I used in the
> first post in this thread, I am also copying the relevant parts here:
>
> server0:
> =
> 19:02:06,104 INFO  [org.apache.activemq.artemis.core.server] AMQ221109:
> Apache ActiveMQ Artemis Backup Server version 1.5.0 [null] started, waiting
> live to fail before it gets active
> 19:02:06,920 INFO  [org.apache.activemq.artemis.core.server] AMQ221024:
> Backup server 
> ActiveMQServerImpl::serverUUID=63157c62-b58c-11e6-ace0-b8a720524153
> is synchronized with live-server.
> 19:02:06,929 INFO  [org.apache.activemq.artemis.core.server] AMQ221031:
> backup announced
>
> server1:
> =
> 19:02:07,076 INFO  [org.apache.activemq.artemis.core.server] AMQ221109:
> Apache ActiveMQ Artemis Backup Server version 1.5.0 [null] started, waiting
> live to fail before it gets active
> 19:02:08,015 INFO  [org.apache.activemq.artemis.core.server] AMQ221024:
> Backup server 
> ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153
> is synchronized with live-server.
> 19:02:08,022 INFO  [org.apache.activemq.artemis.core.server] AMQ221031:
> backup announced
> ...
> 19:04:51,883 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
> Connection failure has been detected: AMQ119015: The connection was
> disconnected because of server shutdown [code=DISCONNECTED]
> 19:04:51,885 WARN  [org.apache.activemq.artemis.core.server] AMQ222095:
> Connection failed with failedOver=false
> 19:04:51,954 WARN  [org.apache.activemq.artemis.core.server] AMQ222095:
> Connection failed with failedOver=false
> 19:04:51,961 INFO  [org.apache.activemq.artemis.core.server] AMQ221029:
> stopped bridge sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153
> 19:04:51,982 INFO  [org.apache.activemq.artemis.core.server] AMQ221037:
> ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153 to
> become 'live'
> 19:04:51,983 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
> Connection failure has been detected: AMQ119015: The connection was
> disconnected because of server shutdown [code=DISCONNECTED]
> ...
> 19:04:52,127 INFO  [org.apache.activemq.artemis.core.server] Scaled down
> 0 messages total.
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539p4719679.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719683.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

[andytaylor]

couple of questions

1. do you see logs in each broker saying that a backup server has been
started and announced?
2. when you kill the server1 do you see logs in server2 saying that failure
has been detected?



On 1 December 2016 at 14:51, grishezz [via ActiveMQ] <
ml-node+s2283324n4719668...@n4.nabble.com> wrote:

> I did. This example is for shared-storage. My scenario is not fit for
> shared-storage.
>
> Honestly, I am beginning to doubt if it even works at all (perhaps a bug
> was introduced into the network-based replication mechanism at some
> point?). Are there any live systems actually using it with either 1.4 or
> 1.5?
>
> I would love to see a working example of the scenario I described above in
> an integration test for example...
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539p4719668.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719674.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

[andytaylor]

take a look at
https://github.com/apache/activemq-artemis/tree/master/examples/features/ha/colocated-failover-scale-down

On 30 November 2016 at 08:53, grishezz [via ActiveMQ] <
ml-node+s2283324n4719600...@n4.nabble.com> wrote:

> Well, I see data files are indeed created under the server1 colocated
> backup. And the configuration above includes a  clause. Other
> than that, I am not sure what does it mean to "make sure" - can I look at
> some information/properties via the jmx interface?
>
> As you can see in the attached logs, it says:
> 19:04:52,127 INFO  [org.apache.activemq.artemis.core.server] Scaled down
> 0 messages total.
>
> But why these 100 messages are not scaled down, I do not know.
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539p4719600.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719601.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

[andytaylor]

you need to make sure that a backup is created colocated with server1 and
that it scales down.

On 29 November 2016 at 22:09, Justin Bertram-2 [via ActiveMQ] <
ml-node+s2283324n471959...@n4.nabble.com> wrote:

> Sorry for the confusion.  The  option is only
> available for shared-storage.  The fail-over semantics for replication
> don't use that parameter.  Carry on.
>
>
> Justin
>
> - Original Message -
> From: "grishezz" <[hidden email]
> >
> To: [hidden email] 
> Sent: Tuesday, November 29, 2016 4:01:55 PM
> Subject: Re: H/A colocated replication environment not working as expected
>
> I only saw the  option available for shared-storage.
> Can I somehow turn it on for replicated-colocated topology?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/H-A-colocated-replication-environment-not-working-as-expected-
> tp4719539p4719590.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539p4719591.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719594.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

[andytaylor]

server0 is backed up by the backup server that is colocated with server1,
not server1 itself. Server2 can either be configured to start as an actual
live or scaledown to the live server, if the latter is configured you
should see the message in server1, if not they will be in the backup
started on server1 when it starts

On 29 November 2016 at 14:18, grishezz [via ActiveMQ] <
ml-node+s2283324n471954...@n4.nabble.com> wrote:

> Right. But now I kill server0 (with all 100 messages) before any messages
> were consumed. My expectation is for these messages to "migrate" to the
> other live server (server1), so that they could be consumed from there.
>
> I am saying "migrate", but really at this moment server0 is already dead,
> so what I thought is supposed to happen is for server1 to detect the
> failure of server0 and thus "restore" those 100 messages it was holding as
> a backup and make them available for consumption. Am I mistaken in this
> expectation?
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539p4719546.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719550.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

[andytaylor]

Then I would expect to see 100 messages at the broker you sent to and none
on the other live broker

On 29 November 2016 at 12:34, grishezz [via ActiveMQ] <
ml-node+s2283324n4719543...@n4.nabble.com> wrote:

> In this scenario message load balancing is disabled.
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539p4719543.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719544.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

[andytaylor]

Im not 100% sure of your topology, however leaving backups out of it I
would expect to see 50 messages on server0 and 50 on server1 if you have
load balancing enabled.

On 29 November 2016 at 09:26, grishezz [via ActiveMQ] <
ml-node+s2283324n4719539...@n4.nabble.com> wrote:

> Hello,
>
> I am trying to set-up the following environment and have ran into
> difficulties:
>
> H/A cluster of 2 servers: server0 & server1 replication=colocated
> master/slave, and message-load-balancing=OFF.
>
> Running the following scenario:
>
> 1) start server0
> 2) start server1
> 3) start consumer0 (connected to server0)
> 4) start consumer1 (connected to server1)
> 5) start producer0 (connected to server0)
> 6) producer0 sends 100 messages to exampleQueue
> 7) consumer0 is blocked on the first message read using debugger
> 8) kill server0
>
> Now, I expected these 100 messages that were not yet acknowledged to
> become available on server1 (as server0 backup is supposed to be there).
> However client1 is receiving no messages (and I can't see them via the jmx
> console either - though here I wasn't sure if they should actually move to
> the live exampleQueue on server1).
>
> Below are the 2 logs and a configuration of one of the servers (the other
> is an exact mirror image). I wonder if the "Connection failed with
> failedOver=false" message might have something to do with the scenario not
> working as expected. I have tried many different config permutations and
> have gone through the documentation several times... I hope I am just
> missing some minor detail.
>
> Help would be greatly appreciated!
>
> 
> server0 log:
> 
> 19:01:58,344 WARN  [org.apache.activemq.artemis.core.server] AMQ222018:
> AIO was not located on this platform, it will fall back to using pure Java
> NIO. If your platform is Linux, install LibAIO to enable the AIO journal
> 19:01:58,399 WARN  [org.apache.activemq.artemis.core.server] AMQ222018:
> AIO was not located on this platform, it will fall back to using pure Java
> NIO. If your platform is Linux, install LibAIO to enable the AIO journal
> 19:01:58,441 INFO  [org.apache.activemq.artemis.integration.bootstrap]
> AMQ101000: Starting ActiveMQ Artemis Server
> 19:02:00,364 INFO  [org.apache.activemq.artemis.core.server] AMQ221000:
> live Message Broker is starting with configuration Broker Configuration
> (clustered=true,journalDirectory=C:\dev_temp\
> apache-artemis-1.5.0\examples\features\ha\mark-poc\target\
> server0\data/server0/data/messaging/journal,bindingsDirectory=C:\dev_temp\
> apache-artemis-1.5.0\examples\features\ha\mark-poc\target\
> server0\data/server0/data/messaging/bindings,
> largeMessagesDirectory=C:\dev_temp\apache-artemis-1.5.0\
> examples\features\ha\mark-poc\target\server0\data/server0/
> data/messaging/largemessages,pagingDirectory=C:\dev_temp\
> apache-artemis-1.5.0\examples\features\ha\mark-poc\target\
> server0\data/server0/data/messaging/paging)
> 19:02:00,391 INFO  [org.apache.activemq.artemis.core.server] AMQ221013:
> Using NIO Journal
> 19:02:00,420 WARN  [org.apache.activemq.artemis.core.server] AMQ222007:
> Security risk! Apache ActiveMQ Artemis is running with the default cluster
> admin user and default password. Please see the cluster chapter in the
> ActiveMQ Artemis User Guide for instructions on how to change this.
> 19:02:00,457 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-server]. Adding protocol support for: CORE
> 19:02:00,459 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-amqp-protocol]. Adding protocol support
> for: AMQP
> 19:02:00,461 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-hornetq-protocol]. Adding protocol support
> for: HORNETQ
> 19:02:00,463 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-mqtt-protocol]. Adding protocol support
> for: MQTT
> 19:02:00,464 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-openwire-protocol]. Adding protocol support
> for: OPENWIRE
> 19:02:00,465 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-stomp-protocol]. Adding protocol support
> for: STOMP
> 19:02:00,737 INFO  [org.apache.activemq.artemis.core.server] AMQ221003:
> Deploying queue jms.queue.exampleQueue
> 19:02:00,766 WARN  [org.apache.activemq.artemis.core.server] AMQ222165:
> No Dead Letter Address configured for queue jms.queue.exampleQueue in
> AddressSettings
> 19:02:00,767 WARN  [org.apache.activemq.artemis.core.server] AMQ222166:
> No Expiry Address configured for queue jms.queue.exampleQueue in
> AddressSettings
> 19:02:00,998 INFO  [org.apache.activemq.artemis.core.server] AMQ221020:
> Started Acceptor at localhost:61616 for protocols
> [CORE,MQTT,AMQP,HORNETQ,STOMP,OPENWIRE]
> 19:02:00,999 INFO  [org.apache.activemq.artemis.core.server] AMQ221007:
> Serv

Re: Slow failover from primary to backup server

[andytaylor]

Ive raised a PR with some fixes in, see
https://github.com/apache/activemq-artemis/pull/901. This should make the
failover quicker in some scenarios. You can also make some configuration
changes like so:

Configure the cluster connection to time out quickly


2500
5000

And also configure the connectors used  in the cluster to have a quicker
connect timeout,

tcp://backup1:61616?connect-timeout-millis=2000

I'm stillinvestigating making more improvements around this area, including.

1. Allowing the qourum size in different ways, statically configured, the
max cluster size and the current cluster size.
2. Allow the master to vote for a quorum if replication fails and shutdown
if it cant get a majority (configurable)

If anyone else has any scenarios I would be happy to try and include them
as part of this work.

Andy

On 25 November 2016 at 21:59, JasonHs [via ActiveMQ] <
ml-node+s2283324n4719501...@n4.nabble.com> wrote:

> Thanks for confirming this Andy, look forward to the new release/update.
>
> Jason
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/Slow-failover-from-
> primary-to-backup-server-tp4719474p4719501.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Slow-failover-from-primary-to-backup-server-tp4719474p4719537.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Slow failover from primary to backup server

[andytaylor]

coincidentally I have been looking at replication and noticed some issue
like you have mentioned. Ive raised a Jira and will be looking to improve
this over the next couple of weeks,
https://issues.apache.org/jira/browse/ARTEMIS-866. Feel free to add any
scenarios that you are having difficulties and I willmake sure they are
addresses.

Andy

On 24 November 2016 at 23:00, JasonHs [via ActiveMQ] <
ml-node+s2283324n4719485...@n4.nabble.com> wrote:

> Thanks Tim.
>
> I have since adjusted the connection TTL time cluster setting, and the
> failover seems to be faster now.
>
> However, as part of the failover testing, I'm still seeing at split brain
> scenario, where I manually block the 61616 port on the master server, and
> wait until backup becomes 'live', and then I unblock the port on the master
> server, and now I have 2 'live' servers.
>
> I have tested this with 3 servers, and still the same result.
>
> Cheers
> Jason
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/Slow-failover-from-
> primary-to-backup-server-tp4719474p4719485.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Slow-failover-from-primary-to-backup-server-tp4719474p4719494.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Artemis Connection retry during initial connection

[andytaylor]

try cf.setInitialConnectAttempts(3)


On 19/03/16 00:32, abhijith [via ActiveMQ] wrote:
> Hi,
>
> I am trying to test initial connection factory retry attempts if
> connection is unsuccessful.  To try this I purposefully did not enable
> SSL where as my server is setup for TLS communication.
>
> Please find below my code
>
>   ActiveMQConnectionFactory cf =
> ActiveMQJMSClient.createConnectionFactoryWithHA(JMSFactoryType.CF,
> server1, server2);
>  cf.setRetryInterval(1000);
>  cf.setReconnectAttempts(3);
>  cf.setRetryIntervalMultiplier(1.0);
>
> When I run connection factory keeps on trying to connect even after 3
> attempts. I am not sure why this keeps trying.  Is there any other flag
> I am missing here?  I was also looking at some documentation or example
> on initial retry attempts.  Any help is greatly appreciated.  Thanks
>
>
> 15:46:09.200 [Thread-10 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Started Netty Connector version
> 4.0.32.Final
> 15:46:09.200 [Thread-10 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Remote destination:
> artemis01-dev.myserver.com:61616
> 15:46:09.306 [Thread-10 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Reconnection successful
> 15:46:09.495 [Thread-11 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Trying reconnection attempt 0/5
> 15:46:09.496 [Thread-11 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Trying to connect with
> connector =
> org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnectorFactory@701b206f,
> parameters = {port=61616, host=artemis01-dev.myserver.com} connector = null
> 15:46:09.496 [Thread-11 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Started Netty Connector version
> 4.0.32.Final
> 15:46:09.496 [Thread-11 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Remote destination:
> artemis01-dev.myserver.com:61616
> 15:46:09.602 [Thread-11 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Reconnection successful
> 15:46:09.796 [Thread-12 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Trying reconnection attempt 0/5
> 15:46:09.796 [Thread-12 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Trying to connect with
> connector =
> org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnectorFactory@701b206f,
> parameters = {port=61616, host=artemis01-dev.myserver.com} connector = null
> 15:46:09.796 [Thread-12 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Started Netty Connector version
> 4.0.32.Final
> 15:46:09.796 [Thread-12 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Remote destination:
> artemis01-dev.myserver.com:61616
> 15:46:09.893 [Thread-12 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Reconnection successful
> 15:46:10.084 [Thread-13 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Trying reconnection attempt 0/5
> 15:46:10.084 [Thread-13 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Trying to connect with
> connector =
> org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnectorFactory@701b206f,
> parameters = {port=61616, host=artemis01-dev.myserver.com} connector = null
> 15:46:10.084 [Thread-13 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Started Netty Connector version
> 4.0.32.Final
> 15:46:10.084 [Thread-13 (ActiveMQ-client-global-threads-1238683479)]
> DEBUG o.a.activemq.artemis.core.client - Remote destination:
> artemis01-dev.myserver.com:61616
>
>
>
> 
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/Artemis-Connection-retry-during-initial-connection-tp4709695.html
>
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> .
> NAML
> 
>





--
View this message in cont

Re: Standalone ActiveMQ address settings

[andytaylor]

If by AMQ you mean Artemis and its standalone then yes the address 
settings should go in the broker.xml file
On 09/02/16 03:40, mhemple [via ActiveMQ] wrote:
> Hi all,
>
> I'm new to activeMQ so I apologize for the basic question.  I am running
> an HA cluster of standalone AMQ brokers connected to a webapp running on
> jboss.  I'm trying to figure out where to set the address settings (see
> example below).  I've tried placing the settings config in
> standalone.xml and also activemq.xml.  This guide
> (https://activemq.apache.org/artemis/docs/1.0.0/queue-attributes.html)
> says it goes in broker.xml, but I don't have a file by that name.  Any
> help will be much appreciated.  Thanks.
>
> Wildfly 8.2
> AMQ 5.13
>
> 
> 
>jms.queue.deadLetterQueue
>3
>5000
>jms.queue.expiryQueue
>true
>10
>2
>0
>true
>PAGE
>-1
>NOTIFY
>5
>true
>true
> 
> 
>
> 
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/Standalone-ActiveMQ-address-settings-tp4707269.html
>
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> .
> NAML
> 
>





--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Standalone-ActiveMQ-address-settings-tp4707269p4707280.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Artemis - all messages go to "Delivering" after a client crash

[andytaylor]

yes it should, Openwire is a work in progress and we're filling gaps in 
its functionality. Could you raise a Jira?

On 14/10/15 13:47, slew77 [via ActiveMQ] wrote:
> Hi,
>
> If I modify the example project: protocols/openwire/message-listener and
> change the session to CLIENT_ACKNOWLEDGE and update onMessage to call
> message.acknowledge(). If I terminate the process before it has
> acknowledged the messages, then I get similar behaviour. The messages
> remain marked as being delivered and aren't released until the broker is
> restarted. There is one slight difference, as in this test follow up
> messages aren't being marked as "delivered", so it's only the messages
> that were being processed when the crash occurred that are stuck.
>
> This is using the broker that is part of the example project with no
> changes.
>
> Should the broker detect this type of crash and allow the messages that
> didn't get processed to be redelivered?
>
> Thanks,
> Steve.
>
> 
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/Artemis-all-messages-go-to-Delivering-after-a-client-crash-tp4702940p4702944.html
>
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> .
> NAML
> 
>





--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Artemis-all-messages-go-to-Delivering-after-a-client-crash-tp4702940p4702946.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Anyone have Artemis working with Apache TomEE?

[andytaylor]

or

connectorClassName="org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnectorFactory"
connectionParameters="server-id=0"

if you have a invm acceptor

On 05/10/15 22:22, Clebert Suconic [via ActiveMQ] wrote:
> I have been putting connectionURI everywhere I could, and it seems
> this is specifically missing that part:
>
>
> For now, you will have to specify:
>
> connectionParameters="host=127.0.0.1;port=5446"
> connectorClassName="org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnectorFactory"
>
>
>
> If you provide me with anything to get to where you are, I could
> change the Spec to accept a parameter with an URI, so you could use
> "tcp://HOST:Port", what should be much simpler.
>
>
> On Mon, Oct 5, 2015 at 4:44 PM, jonathan_at_svg
> <[hidden email] > wrote:
>
>  >
>  > Nice! Thanks I looked all over the javadoc and somehow missed that.
>  >
>  > Ok, the resource adapter needs configuration. Is that done via the
>  > connectionParameters property? If so, is there any docs on what goes
> into
>  > that field?
>  >
>  > Currently on boot I'm throwing this stack trace:
>  >
>  > Caused by: java.lang.IllegalArgumentException: must provide either
>  > TransportType or DiscoveryGroupAddress and DiscoveryGroupPort for
>  > ResourceAdapter Connection Factory
>  > at
>  >
> org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.createActiveMQConnectionFactory(ActiveMQResourceAdapter.java:1707)
>
>  > at
>  >
> org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.setup(ActiveMQResourceAdapter.java:1552)
>
>  > at
>  >
> org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.start(ActiveMQResourceAdapter.java:245)
>
>  > at
>  >
> org.apache.openejb.assembler.classic.Assembler.doCreateResource(Assembler.java:2629)
>
>  > at
>  >
> org.apache.openejb.assembler.classic.Assembler.createResource(Assembler.java:2442)
>
>  > at
>  >
> org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:527)
>
>  > at
> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:439)
>  > ... 17 more
>  >
>  >
>  >
>  >
>  > --
>  > View this message in context:
> http://activemq.2283324.n4.nabble.com/Anyone-have-Artemis-working-with-Apache-TomEE-tp4702611p4702631.html
>  > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
>
>
> --
> Clebert Suconic
>
>
> 
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/Anyone-have-Artemis-working-with-Apache-TomEE-tp4702611p4702632.html
>
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805...@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> .
> NAML
> 
>





--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Anyone-have-Artemis-working-with-Apache-TomEE-tp4702611p4702647.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.