044d6101e9
If an application wants to use a special key/truststore for Artemis but have the remainder of the application use the default Java store, the org.apache.activemq.ssl.keyStore needs to take precedence over Java's javax.net.ssl.keyStore. However, the current implementation takes the first non-null value from System.getProperty(JAVAX_KEYSTORE_PATH_PROP_NAME), System.getProperty(ACTIVEMQ_KEYSTORE_PATH_PROP_NAME), keyStorePath So if the default Java property is set, no override is possible. Swap the order of the JAVAX_... and ACTIVEMQ_... property names so that the ActiveMQ ones come first (as a component-specific overrides), the standard Java ones comes second, and finally a local attribute value (through Stream.of(...).firstFirst()). (In our case the application uses the default Java truststore location at $JAVA_HOME/lib/security/jssecacerts, and only supplies its password in javax.net.ssl.trustStorePassword, and then uses a dedicated truststore for Artemis. Defining both org.apache.activemq.ssl.trustStore and org.apache.activemq.ssl.trustStorePassword now makes Artemis use the dedicated truststore (javax.net.ssl.trustStore is not set as we use the default location, so the second choice org.apache.activemq.ssl.trustStore applies), but with the Java default truststore password (first choice javax.net.ssl.trustStorePassword applies instead of the second choice because it is set for the default truststore). Obviously, this does not work unless both passwords are identical!) |
||
|---|---|---|
| .github/workflows | ||
| .mvn/wrapper | ||
| .settings | ||
| artemis-boot | ||
| artemis-cdi-client | ||
| artemis-cli | ||
| artemis-commons | ||
| artemis-core-client | ||
| artemis-core-client-all | ||
| artemis-core-client-osgi | ||
| artemis-distribution | ||
| artemis-docker | ||
| artemis-dto | ||
| artemis-features | ||
| artemis-hawtio | ||
| artemis-jdbc-store | ||
| artemis-jms-client | ||
| artemis-jms-client-all | ||
| artemis-jms-client-osgi | ||
| artemis-jms-server | ||
| artemis-journal | ||
| artemis-junit | ||
| artemis-maven-plugin | ||
| artemis-protocols | ||
| artemis-ra | ||
| artemis-rest | ||
| artemis-selector | ||
| artemis-server | ||
| artemis-server-osgi | ||
| artemis-service-extensions | ||
| artemis-tools | ||
| artemis-web | ||
| artemis-website | ||
| docs | ||
| etc | ||
| examples | ||
| integration/activemq-spring-integration | ||
| scripts | ||
| tests | ||
| .RELEASING.md.swo | ||
| .asf.yaml | ||
| .gitignore | ||
| .project | ||
| .travis.yml | ||
| LICENSE | ||
| NOTICE | ||
| README.md | ||
| RELEASING.md | ||
| artemis_doap.rdf | ||
| mvnw | ||
| mvnw.cmd | ||
| pom.xml | ||
README.md
ActiveMQ Artemis
This file describes some minimum 'stuff one needs to know' to get started coding in this project.
Source
For details about the modifying the code, building the project, running tests, IDE integration, etc. see our Hacking Guide.
Build Status
Build Status: 
Building the ASYNC IO library
ActiveMQ Artemis provides two journal persistence types, NIO (which uses the Java NIO libraries), and ASYNCIO which interacts with the linux kernel libaio library. The ASYNCIO journal type should be used where possible as it is far superior in terms of performance.
ActiveMQ Artemis does not ship with the Artemis Native ASYNCIO library in the source distribution. These need to be built prior to running "mvn install", to ensure that the ASYNCIO journal type is available in the resulting build. Don't worry if you don't want to use ASYNCIO or your system does not support libaio, ActiveMQ Artemis will check at runtime to see if the required libraries and system dependencies are available, if not it will default to using NIO.
To build the ActiveMQ Artemis ASYNCIO native libraries, please follow the instructions in the artemis-native/README.
Documentation
Our documentation is always in sync with our releases at the Apache ActiveMQ Artemis website.
Or you can also look at the current master version on github.
Examples
To run an example firstly make sure you have run
$ mvn -Prelease install
If the project version has already been released then this is unnecessary.
Each individual example can be run using this command from its corresponding directory:
$ mvn verify
If you wish to run groups of examples then use this command from a parent directory (e.g. examples/features/standard):
$ mvn -Pexamples verify
Recreating the examples
If you are trying to copy the examples somewhere else and modifying them. Consider asking Maven to explicitly list all the dependencies:
# if trying to modify the 'topic' example:
cd examples/jms/topic && mvn dependency:list
Open Web Application Security Project (OWASP) Report
If you wish to generate the report for CCV dependencies, you may run it with the -Powasp profile
$ mvn -Powasp verify
The output will be under ./target/dependency-check-report.html for each sub-module.