Download Activemq 5.16.5
Elvisa Schimke
NOTE: Working directories get created relative to the current directory. To create the working directories in the proper place, ActiveMQ Classic must be launched from its home/installation directory.
If you are building ActiveMQ Classic 4.x under Windows using Cygwin there is a path name length limitation. If the path name length is exceeded, you may see build errors. To correct this, move the ActiveMQ Classic source directory higher in the file system tree, e.g., /cygdrive/c/d/sm.
This procedure explains how to download and install the source distribution on a Unix system. This procedure assumes the Unix machine has a browser. Please see the previous #Unix Binary Installation section for details on how to install ActiveMQ Classic without a browser.
Feel free to use any other applicable IDE. Please refer to the plugin reference for more details.
NOTE: Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ Classic must be launched from its home/installation directory.
The ActiveMQ Classic broker should now run. You can configure the broker by specifying an Xml Configuration file as a parameter to the activemq command. An alternative is to use the Broker Configuration URI to configure things on the command line in a concise format (though the configuration options are not as extensive as if you use Java or XML code). You can also
Apache, ActiveMQ, Apache ActiveMQ, the Apache feather logo, and the Apache ActiveMQ project logo are trademarks of The Apache Software Foundation. Copyright 2024, The Apache Software Foundation. Licensed under Apache License 2.0.
I have a camel route which reads off activemq and updates an RPC SOAP interface. This interface is locked down to one call per user - you have to pass in the username/password per call which is then checked server side, this is a 3rd party interface.
Obviously, our queues have multiple consumers setup thus i've implemented some locking to stop multiple calls per user to the soap interface. A colleague suggested the idea of the activemq consumer telling the soap interface who it was, and from that we could then retrieve a username/password from config and make the call. i.e.:
exchange.getFromEndpoint().getMyUniqueId() returns Consumer1 and so on. Thus we get the Consumer1 username/password, make the SOAP call and then carry on. This i think would stop the Consumer1 username/password being in use multiple times.
I noticed on the web console ( :8161/admin/queueConsumers.jsp?JMSDestination=ROUTE) that theres a session id. I think i might be able to use this...just need to figure out how to get it from my camel route.
I think this might fit my situation, i'll go down this route and see if it works. It was the managing of the groups i didnt want to do. i.e.: the producer has to cycle through each "group" and set it on the outbond message.
Hello,
We recently upgraded to 8.4 without any major issue. After upgrading, I enabled Messaging from global settings without changing anything(default values). Once I shut down tomcat and restarted it, SailPoint is not loading. I am looking at the logs and I see that the error is being thrown from ActiveMQ. On the set up for ActiveMQ I see these properties on IIQ.properties:
messageServiceFactory.type=activemq
activeMQMessageServiceManager.brokerUri=tcp://localhost:61616?transport.trace=true&transport.soTimeout=10000
activeMQMessageServiceManager.activemqLocker=org.apache.activemq.store.jdbc.LeaseDatabaseLocker
I have tried localhost:61616?, (tomcatserverMachine):61616, as well and still cannot load sailpoint.
Should I be entering the identityiq database machine ? or should I be entering Access History database machine? they are all seperate for us.
Can someone help me bring SailPoint up? Is there something wrong I am doing on IIQ.properties?
Also how should I be setting up ActiveMQ properly to use Access History?
Hey @chriskk , Did you have to install ActiveMQ in tomcat before any of this to take place? I was researching and found that ActiveMQ needs to be installed as a war deployment for tomcat. Not sure how iiq is leveraging activeMQ but does this step need to be done before enabling messaging?
ActiveMQ is included in IIQ and is started when it is enabled.
And no, its not necessary to install manually. But yes, its still an option to install ActiveMQ separately and configure it as external (not embedded).
I do have same issue with containers. One container is coming up and the iiq application is working fine, but on other containers, the iiq failing.
Could you please suggest on how to overcome the issue.
While both versions of ActiveMQ provide metrics via JMX, ActiveMQ Classic also exposes metrics on XML pages within the Web Console. See our documentation for a list of metrics the Agent collects from each of these two data sources.
By default, our integration collects the most important key metrics mentioned in Part 1, but you can also configure the Agent to collect other metrics from JMX, depending on your setup and priorities.
Restart the Agent to apply any configuration changes, then execute the status command to confirm your changes. Look for the activemq section in the status output, as shown below. activemq instance_name : activemq-localhost-1099 message : metric_count : 93 service_check_count : 0 status : OK
Now your Agent is collecting metrics from the ActiveMQ Classic Web Console and forwarding them to your Datadog account. If you have more than one ActiveMQ host to monitor, repeat the Agent installation and configuration steps on all your hosts. You can also use a configuration management tool like Ansible or Chef to automate the deployment and configuration of the Datadog Agent.
Modify activemq.d/conf.yaml to add a log configuration like the one shown below. This example configures the Agent to also forward audit logs, which you can optionally collect from Classic and Artemis. Replace and with the full path to your log files. You can use the service tag to aggregate logs, metrics, and traces from different technologies throughout your stack, so you should replace with a value that suits your use case:
Note that this configuration applies a source value of activemq to the logs, which will automatically trigger the appropriate log pipeline to process them. The pipeline applies parsing rules that extract log facets and attributes that give you powerful ways to search and filter your logs in Datadog.
You can add custom tags to your log configuration to give you even more dimensions you can use to aggregate and analyze your logs. The example below extends the conf.yaml file from above to assign a value of checkout to the service tag and apply custom tags to the ActiveMQ logs and the audit logs:
Alerts keep you informed of potential issues in your ActiveMQ infrastructure. You can use tags in your alert definitions to create more focused and actionable alerts. Using our custom product tag from the example in the previous section, the screenshot below illustrates how you could set up an alert that will trigger if the QueueSize metric on an ActiveMQ Classic destination rises above 10,000 only on queues tagged with product:a.
To get started quickly using Datadog alerts, you can enable the recommended monitors for ActiveMQ. And you can integrate your Datadog account with PagerDuty, Slack, and many other notification and collaboration services to make these alerts visible to your team.
Note: This check also supports ActiveMQ Artemis (future ActiveMQ version 6) and reports metrics under the activemq.artemis namespace. See metadata.csv for a list of metrics provided by this integration.
activemq.can_connect
Returns CRITICAL if the Agent is unable to connect to and collect metrics from the monitored ActiveMQ instance, WARNING if no metrics are collected, and OK otherwise.
Statuses: ok, critical, warning
Note: The ActiveMQ XML integration can potentially emit custom metrics, which may impact your billing. By default, there is a limit of 350 metrics. If you require additional metrics, contact Datadog support.
View a data-driven visualization of the physical servers, virtualmachines, AWS instances, and other resources in your environment thatare visible to Infrastructure Monitoring. For information aboutnavigators, see Use navigators in Splunk Infrastructure Monitoring.
instancePrefix is specified in a referenced MBean block,the prefix specified in the Connection block will appear at thebeginning of the plugin instance and the prefix specified inthe MBean block will be appended to it.
specific service monitor such as cassandra, kafka, or activemq,they come pre-loaded with a set of mappings, and any that youadd in this option will be merged with those. To learn more, see the Collectd documentation .
In host-based subscription plans, default metrics are those metricsincluded in host-based subscriptions in Splunk Observability Cloud, such ashost, container, or bundled metrics. Custom metrics are not providedby default and might be subject to charges. SeeMetric categories for more information.
Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.
c80f0f1006