The MBean object name for the queue is:
/org.apache.activemq.artemis:broker="artemis-server",component=addresses,address="Step-Event"/.
After recreating the object name with:
/ObjectName objName =
ObjectNameBuilder.create(ActiveMQDefaultConfiguration.getDefaultJmxDomain(),
"artemis-serve").get
The call to
org.apache.activemq.artemis.api.core.management.ObjectNameBuilder#getQueueObjectName
is creating this MBean object name:
org.apache.activemq.artemis:broker="localhost",component=
addresses,address="Step-Event",subcomponent=queues,routing-
type="anycast",queue="Step-Event"
Can you us
Thanks Justin. I don't know how I missed that example earlier. It is very
clear now after going through it. having said that, Now if I run the code
below, I get /InstanceNotFoundException/ during serverControl.createDivert
method invocation.
/public class App {
private static final String
Thanks Justin!
I just looked at the maven definitions of the artemis project and found:
1.8
1.8
Hence I assumed they are using Java 8 language Features. I will try it later
this week and let you know if it compiles.
I will try camel case instead of kebab case (nice name :) for the connection
par
The "connectionParameters" in your RA config should use camel case rather
than dashes. For example "ssl-enabled" should be "sslEnabled", etc. That
will probably fix your SSL issue.
I wouldn't expect the admin object to work as I don't believe the Artemis
RA supports admin objects.
The best way
As far as I remember the ping is part of the AMQP spec. (It follows a
different name I don’t remember now) So it shouldn’t matter what library
you used unless there is a bug with your client.
On Mon, Nov 27, 2017 at 6:55 AM Fuhrmann, Hauke <
fuhrmann.ha...@scheidt-bachmann-st.de> wrote:
> Hi ther
Any opinions about the last question if it's possible to build the Artemis
Resource Adapter for Java 7 based clients like EAPs < 6.3.3?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi all,
I found an resolve my problem, so I shared the solution!
The goal is load again the server when we add a private key inside the
keystore.
I used the OSGI mechanism on the update configuration file.
This event stop the server and start again with new config file and so new
all keys inside
Hi there,
from this documentation [1] I understand that Artemis has smart watchdog-ping
mechanisms to detect failure either on server side or client side.
Whenever some ping is not received in some configurable interval, the
connection is considered lost and action can be taken.
The question i
