Using ActiveMQ > Getting Started

Introduction

This document describes how to install and configure ActiveMQ 5.x for both Unix and Windows’ platforms.

Document Organization

The Getting Started Guide for ActiveMQ 5.x document contains the following sections:

  • Installation Procedure for Windows
  • Installation Procedure for Unix
  • Starting ActiveMQ
  • Testing the Installation

ONNX Runtime is built and tested with CUDA 10.2 and cuDNN 8.0.3 using Visual Studio 2019 version 16.7. ONNX Runtime can also be built with CUDA versions from 10.1 up to 11.0, and cuDNN versions from 7.6 up to 8.0. The path to the CUDA installation must be provided via the CUDAPATH environment variable, or the -cudahome parameter.

  1. Jan 19, 2021 Java manual download page. Get the latest version of the Java Runtime Environment (JRE) for Windows, Mac, Solaris, and Linux.
  2. JAVAHOME should point to jdk directory and not to jre directory. Also JAVAHOME should point to the home jdk directory and not to jdk/bin directory. Assuming that you have JDK installed in your program files directory then you need to set the JAVAHOME like this: JAVAHOME='C: Program Files Java jdkxxx' xxx is the jdk version.
  3. Jan 19, 2021% brew search java Formulae app-engine-java java javacc jslint4java pdftk-java google-java-format java11 javarepl libreadline-java 2.3 The Java 8 is available at the openjdk@8 formula. The openjdk is the same as the java formula, and it always contains the latest JDK GA version; the openjdk@11 is the same as the java11 formula, containing.

Pre-Installation Requirements

Java Runtime For Mac Os X

Hardware:

  • ~ 60 MB of free disk space for the ActiveMQ 5.x binary distribution.
    (you need additional disk space for storing persistent messages to disk)
  • ~ 300 MB of free disk space for the ActiveMQ 5.x source or developer’s distributions.

`Operating Systems:**

  • Windows: Windows XP SP2, Windows 2000, Windows Vista, Windows 7.
  • Unix: Ubuntu Linux, Powerdog Linux, MacOS, AIX, HP-UX, Solaris, or any Unix platform that supports Java.

Environment:

  • Java Runtime Environment (JRE)JRE 1.7 (1.6 for version <=5.10.0)
    (a JDK is required if you plan to recompile source code)
  • The JAVA_HOME environment variable must be set to the directory where the JRE is installed
    (Unix: the binary “java” has to be resolvable by the PATH variable; execute “which java” to verify)
  • Maven 3.0.0 build system
    (only if you plan to recompile source code)
  • JARs that will be used must be added to the classpath.
    (only if you plan to recompile source code)

Installation Procedure for Windows

Java Runtime Macos Big Sur

This section of the Getting Started Guide explains how to install binary and source distributions of ActiveMQ on a Windows system.

Windows Binary Installation

This procedure explains how to download and install the binary distribution on a Windows system.

  1. Download the latest release
    (see Download -> “The latest stable release” -> “apache-activemq-x.x.x-bin.zip”)
  2. Extract the files from the ZIP file into a directory of your choice.
  3. Proceed to the #Starting ActiveMQ section of this document.
  4. Following start-up, go to the #Testing the Installation section of this document.

Windows Source Installation

This procedure explains how to download and install the source distribution on a Windows system. City racing gametn hindi.

  1. Download the latest release
    (see Download -> “The latest stable release” -> “apache-activemq-x.x.x-source-release.zip”)
  2. Extract ActiveMQ from the ZIP file into a directory of your choice.
  3. The recommended method of building ActiveMQ is the following:

    where [activemq_install_dir] is the directory in which ActiveMQ was installed.

  4. If you prefer to use an IDE, then you can auto-generate the IDE’s project file using maven plugins:

    or

    Feel free to use any other applicable IDE. Please refer to the plugin reference for more details.

  5. Start ActiveMQ from the target directory, for example:

    NOTE: Working directories get created relative to the current directory. To create the working directories in the proper place, ActiveMQ must be launched from its home/installation directory.

  6. Proceed to the #Testing the Installation section.

    Warning

    If you are building ActiveMQ 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 source directory higher in the file system tree, e.g., /cygdrive/c/d/sm.

Windows Developer’s Release

This procedure explains how to download and install the latest developer’s snapshot.

  1. Open the release archive: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/
    (open one of the SNAPSHOT directories)
  2. Select the version of ActiveMQ to download (if necessary, scroll down to see the ActiveMQ snapshots).
  3. Extract the files from the ZIP file into a directory of your choice.
  4. If a binary snapshot was downloaded, proceed to the #Starting ActiveMQ section of this document.
    If a source snapshot was downloaded, perform step 6 and step 7 of the #Windows Source Installation procedure.
  5. Following start-up, proceed to the #Testing the Installation section.

Installation Procedure for Unix

Unix Binary Installation

This procedure explains how to download and install the binary distribution on a Unix system.
NOTE: There are several alternative ways to perform this type of installation.

  1. Download the activemq zipped tarball file to the Unix machine, using either a browser or a tool, i.e., wget, scp, ftp, etc. for example:
    (see Download -> “The latest stable release”)
  2. Extract the files from the zipped tarball into a directory of your choice. For example:
  3. Proceed to the #Starting ActiveMQ section of this document.

  4. Following start-up, go to the #Testing the Installation section.

Using Homebrew installer on OSX

If you use OSX as your platform, you can use Homebrew package manager to easily install Apache ActiveMQ.

  1. After installing Homebrew package manager successfully, just run

    You can expect the following output:

Java Runtime Os X Versions

ActiveMQ will be installed in /usr/local/Cellar/apache-activemq/x.x.x/ directory (where x.x.x denotes the actual version being installed).

Now you can proceed to #Starting ActiveMQ and #Testing the Installation sections.

Unix Source Installation

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 without a browser.

  1. Download the latest source release
    (see Download -> “The latest stable release” -> “activemq-parent-x.x.x-source-release.zip”)
  2. Extract the files from the ZIP file into a directory of your choice. For example:
  3. Build ActiveMQ using Maven:
    The preferred method of building ActiveMQ is the following:

    If Maven crashes with a java.lang.OutOfMemoryError, you you need to do this first (assuming a Bourne-like shell):

    If you prefer to use an IDE then you can auto-generate the IDE’s project file using maven plugins:

    or

    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 must be launched from its home/installation directory.

  4. Proceed to the #Starting ActiveMQ section of this document.
  5. Proceed to #Testing the Installation section.

Unix Developer’s Release

This procedure explains how to download and install the latest developer’s snapshot.

  1. Open the release archive: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/
    (open one of the SNAPSHOT directories)
  2. Select the version of ActiveMQ to download (you may have to scroll down to see the ActiveMQ snapshots).
    The filename will be similar to: activemq-x.x.x-tar.gz.
  3. Extract the files from the gzip file into a directory of your choice. For example:
    For a binary developer’s snapshot:

    For a source developer’s snapshot:

  4. If a binary snapshot was downloaded, to make it executable, the ActiveMQ script may need its permissions changed:
  5. For a binary snapshot, proceed to the #Starting ActiveMQ section of this document.
  6. If a source snapshot was downloaded perform steps 6 - 8 of the #Unix Source Installation procedure.
  7. Proceed to the #Testing the Installation section.

Starting ActiveMQ

There now follows instructions on how to run the ActiveMQ Message Broker.

On Windows:

From a console window, change to the installation directory and run ActiveMQ:

where [activemq_install_dir] is the directory in which ActiveMQ was installed, e.g., c:Program FilesActiveMQ-5.x.
Then type:

`NOTE:** Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.

On Unix:

From a command shell, change to the installation directory and run ActiveMQ as a foregroud process:

From a command shell, change to the installation directory and run ActiveMQ as a daemon process:

More help

For other ways of running the broker see Here. For example you can run an embedded broker inside your JMS Connection to avoid starting a separate process.

Testing the Installation

Using the administrative interface

Java Runtime Osx Catalina

  • Open the administrative interface
    • URL: http://127.0.0.1:8161/admin/
    • Login: admin
    • Passwort: admin
  • Navigate to “Queues”
  • Add a queue name and click create
  • Send test message by klicking on “Send to”

Logfile and console output

If ActiveMQ is up and running without problems, the Window’s console window or the Unix command shell will display information similar to the following log line (see stdout output or “[activemq_install_dir]/data/activemq.log”):

Listen port

ActiveMQ’s default port is 61616. From another window run netstat and search for port 61616.

From a Windows console, type:

Java runtime os x high sierra

OR

From a Unix command shell, type:

Java runtime os x 10.10

Monitoring ActiveMQ

You can monitor ActiveMQ using the Web Console by pointing your browser at http://localhost:8161/admin.

From ActiveMQ 5.8 onwards the web apps is secured out of the box.
The default username and password is admin/admin. You can configure this in the conf/jetty-real.properties file.

Or you can use the JMX support to view the running state of ActiveMQ.

For more information see the file docs/WebConsole-README.txt in the distribution.

Stopping ActiveMQ

For both Windows and Unix installations, terminate ActiveMQ by typing “CTRL-C” in the console or command shell in which it is running.

If ActiveMQ was started in the background on Unix, the process can be killed, with the following:

Configuring ActiveMQ

The ActiveMQ 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

Also see Configuring Transports to see how you can configure the various connection, transport and broker options using the connection URL in the ActiveMQConnectionFactory.

See the Initial Configuration for details of which jars you need to add to your classpath to start using ActiveMQ in your Java code

If you want to use JNDI to connect to your JMS provider then please view the JNDI Support. If you are a Spring user you should read about Spring Support

After the installation, ActiveMQ is running with a basic configuration. For details on configuring options, please see refer to the Configuration section.

Additional Resources

If you are new to using ActiveMQ, running the Web Samples or the Examples is a good next step to learn more about ActiveMQ.

The Commercial Providers listed on the Support page may also have additional documentation, examples, tutorials, etc… that can help you get started.

The following are the system requirements for installing the JDK and the JRE on macOS:

  • Any Intel-based computer running macOS.

  • Administrator privileges.

    You cannot install Java for a single user. Installing the JDK and JRE on macOS is performed on a systemwide basis for all users. Administrator privileges are required to install the JDK and JRE on macOS.

  • When you install the JDK, it also installs the JRE. However, the system will not replace the current JRE with a lower version.

    To determine the current JRE version installed on your system, see Determining the JRE Version Installed on macOS. To install an earlier version of the JRE, you must first uninstall the current version. See Uninstalling the JRE on macOS.

  • When you install the JRE, you can install only one JRE on your system at a time. The system will not install a JRE that has an earlier version than the current version.

    To determine the current JRE version installed on your system, see Determining the JRE Version Installed on macOS. To install an earlier version of the JRE, you must first uninstall the current version. See Uninstalling the JRE on macOS.

    Note:

    Installing a JRE from Oracle will not update java -version symlinks or add java to your path. To do this, you must install the JDK.