NO-JIRA fix warnings from w3c/link-checker in docs
also update URLs and `s/http/https` in docs wherever possible
This commit is contained in:
Jiri Danek
parent
f331a3f659
commit
472e429540
|
|
@ -17,7 +17,7 @@ To build the ActiveMQ Artemis ASYNCIO native libraries, please follow the instru
|
|||
|
||||
## Documentation
|
||||
|
||||
Our documentation is always in sync with our releases at the [Apache ActiveMQ Artemis](http://activemq.apache.org/artemis/docs.html) website.
|
||||
Our documentation is always in sync with our releases at the [Apache ActiveMQ Artemis](https://activemq.apache.org/artemis/docs.html) website.
|
||||
|
||||
Or you can also look at the current master version on [github](https://github.com/apache/activemq-artemis/blob/master/docs/user-manual/en/SUMMARY.md).
|
||||
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ Otherwise snapshots will be created at 1.4.1 and forgotten. (Unless we ever rele
|
|||
|
||||
For more information look at the prepare plugin:
|
||||
|
||||
- http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#pushChanges
|
||||
- https://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#pushChanges
|
||||
|
||||
If you set `pushChanges=false` then you will have to push the changes manually. The first command is to push the commits
|
||||
which are for changing the `<version>` in the pom.xml files, and the second push is for the tag, e.g.:
|
||||
|
|
|
|||
|
|
@ -122,7 +122,7 @@ public class TransportConstants {
|
|||
* @see <a
|
||||
* href="http://design.jboss.org/jbossorg/branding/Javadocs/doc/api/org/jboss/netty/channel/socket/SocketChannelConfig.html#setTcpNoDelay%28boolean%29">
|
||||
* Netty note on this option</a>
|
||||
* @see <a href="http://docs.oracle.com/javase/6/docs/technotes/guides/net/socketOpt.html">Oracle
|
||||
* @see <a href="http://docs.oracle.com/javase/8/docs/technotes/guides/net/socketOpt.html">Oracle
|
||||
* doc on tcpNoDelay</a>
|
||||
*/
|
||||
public static final String TCP_NODELAY_PROPNAME = "tcpNoDelay";
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ After you installed brew you can install npm by:
|
|||
|
||||
brew install npm
|
||||
|
||||
[brew]: <http://brew.sh>
|
||||
[brew]: <https://brew.sh>
|
||||
|
||||
To build the full release with documentation, Javadocs, and the full web site:
|
||||
|
||||
|
|
|
|||
|
|
@ -5,14 +5,14 @@ contributors are encouraged (but not required) to use a mirror on GitHub for col
|
|||
functionality. Follow the steps below to get set up with GitHub, etc.
|
||||
|
||||
If you do not wish to use GitHub for whatever reason you can follow the overall process outlined in the "Typical
|
||||
development cycle" section below but instead attach [a patch file](http://git-scm.com/docs/git-format-patch) to the
|
||||
development cycle" section below but instead attach [a patch file](https://git-scm.com/docs/git-format-patch) to the
|
||||
related JIRA or an email to the [dev list](http://activemq.apache.org/mailing-lists.html).
|
||||
|
||||
## Initial Steps
|
||||
|
||||
1. Create a GitHub account if you don't have one already
|
||||
|
||||
http://github.com
|
||||
https://github.com
|
||||
|
||||
1. Fork the apache-artemis repository into your account
|
||||
|
||||
|
|
@ -159,7 +159,7 @@ related JIRA or an email to the [dev list](http://activemq.apache.org/mailing-li
|
|||
|
||||
Due to incompatibilities between some open source licenses and the Apache v2.0 license (that this project is licensed under)
|
||||
care must be taken when adding new dependencies to the project. The Apache Software Foundation 3rd party licensing
|
||||
policy has more information here: http://www.apache.org/legal/3party.html
|
||||
policy has more information here: https://www.apache.org/legal/3party.html
|
||||
|
||||
To keep track of all licenses in ActiveMQ Artemis, new dependencies must be added in either the top level pom.xml or in test/pom.xml
|
||||
(depending on whether this is a test only dependency or if it is used in the main code base). The dependency should be
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ copy them _after importing all your projects_:
|
|||
done
|
||||
|
||||
Do not use the [maven-eclipse-plugin](https://maven.apache.org/plugins/maven-eclipse-plugin/) to copy the files as it
|
||||
conflicts with [m2e](http://eclipse.org/m2e/).
|
||||
conflicts with [m2e](https://eclipse.org/m2e/).
|
||||
|
||||
## IDEA
|
||||
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ After you add the JDK to the IDE, add also the vm.jar specific to your platform
|
|||
(e.g: JAVA_HOME/jre/lib/amd64/default/jclSC180/vm.jar
|
||||
```
|
||||
|
||||
There's a [SOF Question](http://stackoverflow.com/questions/27906481/can-intellij-14-be-used-to-work-with-ibm-jdk-1-7/32852361#32852361) about this that could be useful in case you are running into this issue.
|
||||
There's a [SOF Question](https://stackoverflow.com/questions/27906481/can-intellij-14-be-used-to-work-with-ibm-jdk-1-7/32852361#32852361) about this that could be useful in case you are running into this issue.
|
||||
|
||||
### Style Templates and Inspection Settings for Idea
|
||||
|
||||
|
|
@ -70,7 +70,7 @@ blue arrow.
|
|||
We recommend using Eclipse Kepler (4.3), due to the built-in support for Maven and Git. Note that there are still some
|
||||
Maven plugins used by sub-projects (e.g. documentation) which are not supported even in Eclipse Kepler (4.3).
|
||||
|
||||
Eclipse [m2e](http://eclipse.org/m2e/) is already included in "Eclipse IDE for Java Developers", or it can be installed
|
||||
Eclipse [m2e](https://eclipse.org/m2e/) is already included in "Eclipse IDE for Java Developers", or it can be installed
|
||||
from [Eclipse Kepler release repository](http://download.eclipse.org/releases/kepler).
|
||||
|
||||
### Git setup
|
||||
|
|
@ -86,7 +86,7 @@ For proper schema validation you can add the Artemis schemas to your Eclipse XML
|
|||
* Repeat the above steps and add src/main/resources/schema/artemis-configuration.xsd
|
||||
|
||||
### Checkstyle setup
|
||||
You can import the Artemis Checkstyle template into eclipse to do Checkstyle validation. As a prerequisite you need to make sure the Checkstyle plugin is installed into Eclipse which you can get form the Eclipse Marketplace. You also will need to configure Sevntu-Checkstyle. See http://sevntu-checkstyle.github.io/sevntu.checkstyle/ for instructions. Then to configure the template:
|
||||
You can import the Artemis Checkstyle template into eclipse to do Checkstyle validation. As a prerequisite you need to make sure the Checkstyle plugin is installed into Eclipse which you can get form the Eclipse Marketplace. You also will need to configure Sevntu-Checkstyle. See https://sevntu-checkstyle.github.io/sevntu.checkstyle/ for instructions. Then to configure the template:
|
||||
|
||||
* Open: Window -> Preferences -> Checkstyle
|
||||
* Select New -> "Project Relative Configuration" in the "Type" dropdown
|
||||
|
|
@ -95,7 +95,7 @@ You can import the Artemis Checkstyle template into eclipse to do Checkstyle val
|
|||
|
||||
### Annotation Pre-Processing
|
||||
|
||||
ActiveMQ Artemis uses [JBoss Logging](https://community.jboss.org/wiki/JBossLoggingTooling) and that requires source
|
||||
ActiveMQ Artemis uses [JBoss Logging](https://developer.jboss.org/wiki/JBossLoggingTooling) and that requires source
|
||||
code generation from Java annotations. In order for it to 'just work' in Eclipse you need to install the
|
||||
_Maven Integration for Eclipse JDT Annotation Processor Toolkit_ [m2e-apt](https://github.com/jbosstools/m2e-apt). See
|
||||
this [JBoss blog post](https://community.jboss.org/en/tools/blog/2012/05/20/annotation-processing-support-in-m2e-or-m2e-apt-100-is-out)
|
||||
|
|
@ -116,7 +116,7 @@ Eclipse Indigo (3.7) has out-of-the-box support for it.
|
|||
As of this writing, Eclipse Kepler (4.3) still lacks support for Maven's javacc plugin. The available [m2e connector for
|
||||
javacc-maven-plugin](https://github.com/objectledge/maven-extensions) requires a downgrade of Maven components to be
|
||||
installed. manual installation instructions (as of this writing you need to use the development update site). See
|
||||
[this post](http://dev.eclipse.org/mhonarc/lists/m2e-users/msg02725.html) for how to do this with Eclipse Juno (4.2).
|
||||
[this post](https://dev.eclipse.org/mhonarc/lists/m2e-users/msg02725.html) for how to do this with Eclipse Juno (4.2).
|
||||
|
||||
The current recommended solution for Eclipse Kepler is to mark `javacc-maven-plugin` as ignored by Eclipse, run Maven
|
||||
from the command line and then modify the project `activemq-core-client` adding the folder
|
||||
|
|
@ -126,6 +126,6 @@ from the command line and then modify the project `activemq-core-client` adding
|
|||
|
||||
Importing all ActiveMQ Artemis subprojects will create _too many_ projects in Eclipse, cluttering your _Package Explorer_
|
||||
and _Project Explorer_ views. One way to address that is to use
|
||||
[Eclipse's Working Sets](http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Fconcepts%2Fcworkset.htm)
|
||||
[Eclipse's Working Sets](https://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Fconcepts%2Fcworkset.htm)
|
||||
feature. A good introduction to it can be found at a
|
||||
[Dzone article on Eclipse Working Sets](http://eclipse.dzone.com/articles/categorise-projects-package).
|
||||
[Dzone article on Eclipse Working Sets](https://dzone.com/articles/categorise-projects-package).
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ There are numerous methods in `org.apache.activemq.artemis.tests.util.ActiveMQTe
|
|||
methods are named like create*Config(..). Each one creates a slightly different configuration but there is a lot of
|
||||
overlap between them.
|
||||
|
||||
In any case, `org.apache.activemq.artemis.core.config.Configuration` is a [_fluent_](http://en.wikipedia.org/wiki/Fluent_interface)
|
||||
In any case, `org.apache.activemq.artemis.core.config.Configuration` is a [_fluent_](https://en.wikipedia.org/wiki/Fluent_interface)
|
||||
interface so it's easy to customize however you need.
|
||||
|
||||
### Look at other test-cases
|
||||
|
|
|
|||
|
|
@ -59,14 +59,14 @@ around normal Apache ActiveMQ Artemis connections to clients and to other server
|
|||
cluster connections. This being the case we need a way of establishing
|
||||
the initial first connection. This can be done using dynamic discovery
|
||||
techniques like
|
||||
[UDP](http://en.wikipedia.org/wiki/User_Datagram_Protocol) and
|
||||
[UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol) and
|
||||
[JGroups](http://www.jgroups.org/), or by providing a list of initial
|
||||
connectors.
|
||||
|
||||
### Dynamic Discovery
|
||||
|
||||
Server discovery uses
|
||||
[UDP](http://en.wikipedia.org/wiki/User_Datagram_Protocol) multicast or
|
||||
[UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol) multicast or
|
||||
[JGroups](http://www.jgroups.org/) to broadcast server connection
|
||||
settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -102,7 +102,7 @@ Name | Description
|
|||
[persist-id-cache](duplicate-detection.md "Configuring the Duplicate ID Cache") | true means that ID's are persisted to the journal. Default=true
|
||||
[queues](address-model.md "Predefined Queues") | [a list of queue to be created](#queue-type)
|
||||
[remoting-incoming-interceptors](intercepting-operations.md "Intercepting Operations") | A list of interceptor
|
||||
[resolveProtocols]() | Use [ServiceLoader](http://docs.oracle.com/javase/tutorial/ext/basics/spi.html) to load protocol modules. Default=true
|
||||
[resolveProtocols]() | Use [ServiceLoader](https://docs.oracle.com/javase/tutorial/ext/basics/spi.html) to load protocol modules. Default=true
|
||||
[scheduled-thread-pool-max-size](thread-pooling.md#server-scheduled-thread-pool "Server Scheduled Thread Pool")| Maximum number of threads to use for the scheduled thread pool. Default=5
|
||||
[security-enabled](security.md "Security") | true means that security is enabled. Default=true
|
||||
[security-invalidation-interval](security.md "Security") | how long (in ms) to wait before invalidating the security cache. Default=10000
|
||||
|
|
@ -157,8 +157,8 @@ Name | Description
|
|||
[filter](core-bridges.md "Core Bridges") | optional core filter expression
|
||||
[transformer-class-name](core-bridges.md "Core Bridges") | optional name of transformer class
|
||||
[min-large-message-size](core-bridges.md "Core Bridges") | Limit before message is considered large. default 100KB
|
||||
[check-period](connection-ttl.md "Detecting Dead Connections") | [TTL](http://en.wikipedia.org/wiki/Time_to_live "Time to Live") check period for the bridge. -1 means disabled. default 30000 (ms)
|
||||
[connection-ttl](connection-ttl.md "Detecting Dead Connections") | [TTL](http://en.wikipedia.org/wiki/Time_to_live "Time to Live") for the Bridge. This should be greater than the ping period. default 60000 (ms)
|
||||
[check-period](connection-ttl.md "Detecting Dead Connections") | [TTL](https://en.wikipedia.org/wiki/Time_to_live "Time to Live") check period for the bridge. -1 means disabled. default 30000 (ms)
|
||||
[connection-ttl](connection-ttl.md "Detecting Dead Connections") | [TTL](https://en.wikipedia.org/wiki/Time_to_live "Time to Live") for the Bridge. This should be greater than the ping period. default 60000 (ms)
|
||||
[retry-interval](core-bridges.md "Core Bridges") | period (in ms) between successive retries. default 2000
|
||||
[retry-interval-multiplier](core-bridges.md "Core Bridges") | multiplier to apply to successive retry intervals. default 1
|
||||
[max-retry-interval](core-bridges.md "Core Bridges") | Limit to the retry-interval growth. default 2000
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ Each acceptor defines a way in which connections can be made to the
|
|||
Apache ActiveMQ Artemis server.
|
||||
|
||||
In the above example we're defining an acceptor that uses
|
||||
[Netty](http://netty.io/) to listen for connections at port
|
||||
[Netty](https://netty.io/) to listen for connections at port
|
||||
`61617`.
|
||||
|
||||
The `acceptor` element contains a `URL` that defines the kind of Acceptor
|
||||
|
|
@ -97,7 +97,7 @@ Connection jmsConnection = connectionFactory.createConnection();
|
|||
## Configuring the Netty transport
|
||||
|
||||
Out of the box, Apache ActiveMQ Artemis currently uses
|
||||
[Netty](http://netty.io/), a high performance low level
|
||||
[Netty](https://netty.io/), a high performance low level
|
||||
network library.
|
||||
|
||||
Our Netty transport can be configured in several different ways; to use
|
||||
|
|
@ -164,9 +164,9 @@ Netty for simple TCP:
|
|||
default value for this property is `61616`.
|
||||
|
||||
- `tcpNoDelay`. If this is `true` then [Nagle's
|
||||
algorithm](http://en.wikipedia.org/wiki/Nagle%27s_algorithm) will be
|
||||
algorithm](https://en.wikipedia.org/wiki/Nagle%27s_algorithm) will be
|
||||
disabled. This is a [Java (client) socket
|
||||
option](http://docs.oracle.com/javase/7/docs/technotes/guides/net/socketOpt.html).
|
||||
option](https://docs.oracle.com/javase/8/docs/technotes/guides/net/socketOpt.html).
|
||||
The default value for this property is `true`.
|
||||
|
||||
- `tcpSendBufferSize`. This parameter determines the size of the
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ SQL 92 expression syntax.
|
|||
It is the same as the syntax used for JMS selectors, but the predefined
|
||||
identifiers are different. For documentation on JMS selector syntax
|
||||
please the JMS javadoc for
|
||||
[javax.jms.Message](http://docs.oracle.com/javaee/6/api/javax/jms/Message.html).
|
||||
[javax.jms.Message](https://docs.oracle.com/javaee/7/api/javax/jms/Message.html).
|
||||
|
||||
Filter expressions are used in several places in Apache ActiveMQ Artemis
|
||||
|
||||
|
|
|
|||
|
|
@ -111,7 +111,7 @@ by the parameters passed to its constructor.
|
|||
destination
|
||||
|
||||
The selector expression must follow the [JMS selector
|
||||
syntax](http://docs.oracle.com/javaee/6/api/javax/jms/Message.html)
|
||||
syntax](https://docs.oracle.com/javaee/7/api/javax/jms/Message.html)
|
||||
|
||||
- Failure Retry Interval
|
||||
|
||||
|
|
@ -295,7 +295,7 @@ connection and the second the read timeout for the socket.
|
|||
> using RMI. If you want to control the timeouts for the RMI connections
|
||||
> then this can be done via system properties. JBoss uses Sun's RMI and
|
||||
> the properties can be found
|
||||
> [here](http://docs.oracle.com/javase/6/docs/technotes/guides/rmi/sunrmiproperties.html).
|
||||
> [here](https://docs.oracle.com/javase/8/docs/technotes/guides/rmi/sunrmiproperties.html).
|
||||
> The default connection timeout is 10 seconds and the default read
|
||||
> timeout is 18 seconds.
|
||||
|
||||
|
|
|
|||
|
|
@ -85,5 +85,5 @@ Or on Debian systems:
|
|||
In the source distribution or git clone, in the `artemis-native` directory, execute the shell
|
||||
script `compile-native.sh`. This script will invoke the proper commands to perform the native build.
|
||||
|
||||
If you want more information refer to the [cmake web pages](http://cmake.org).
|
||||
If you want more information refer to the [cmake web pages](https://cmake.org).
|
||||
|
||||
|
|
|
|||
|
|
@ -448,7 +448,7 @@ You can also configure the connector using the following:
|
|||
> Remote connections using the default JVM Agent not enabled by default as Artemis exposes the mBean Server via its own configuration.
|
||||
> This is so Artemis can leverage the JAAS authentication layer via JMX. If you want to expose this then you will need to
|
||||
> disable both the connector and the authorisation by removing them from the `management.xml` configuration.
|
||||
> Please refer to [Java Management guide](http://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html)
|
||||
> Please refer to [Java Management guide](https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html)
|
||||
> to configure the server for remote management (system properties must be set in `artemis.profile`).
|
||||
|
||||
By default, Apache ActiveMQ Artemis server uses the JMX domain "org.apache.activemq.artemis".
|
||||
|
|
@ -466,10 +466,10 @@ and MBean proxies to manage Apache ActiveMQ Artemis.
|
|||
|
||||
### Exposing JMX using Jolokia
|
||||
|
||||
The default Broker configuration ships with the [Jolokia](http://www.jolokia.org)
|
||||
The default Broker configuration ships with the [Jolokia](https://jolokia.org)
|
||||
HTTP agent deployed as a Web Application. Jolokia is a remote
|
||||
JMX-over-HTTP bridge that exposes MBeans. For a full guide as
|
||||
to how to use it refer to [Jolokia Documentation](http://www.jolokia.org/documentation.html),
|
||||
to how to use it refer to [Jolokia Documentation](https://jolokia.org/documentation.html),
|
||||
however a simple example to query the broker's version would
|
||||
be to use a browser and go to the URL [http://username:password@localhost:8161/console/jolokia/read/org.apache.activemq.artemis:broker="0.0.0.0"/Version]().
|
||||
|
||||
|
|
@ -511,7 +511,7 @@ management message's reply-to address (specified by
|
|||
|
||||
A `ClientConsumer` can be used to consume the management reply and
|
||||
retrieve the result of the operation (if any) stored in the reply's
|
||||
body. For portability, results are returned as a [JSON](http://json.org)
|
||||
body. For portability, results are returned as a [JSON](https://json.org)
|
||||
String rather than Java Serialization (the
|
||||
`org.apache.activemq.artemis.api.core.management.ManagementHelper` can be used
|
||||
to convert the JSON string to Java objects).
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
Apache ActiveMQ Artemis is an asynchronous messaging system, an example of [Message
|
||||
Oriented
|
||||
Middleware](http://en.wikipedia.org/wiki/Message_oriented_middleware) ,
|
||||
Middleware](https://en.wikipedia.org/wiki/Message-oriented_middleware) ,
|
||||
we'll just call them messaging systems in the remainder of this book.
|
||||
|
||||
We'll first present a brief overview of what kind of things messaging
|
||||
|
|
@ -19,7 +19,7 @@ together, whilst typically providing reliability, transactions and many
|
|||
other features.
|
||||
|
||||
Unlike systems based on a [Remote Procedure
|
||||
Call](http://en.wikipedia.org/wiki/Remote_procedure_call) (RPC) pattern,
|
||||
Call](https://en.wikipedia.org/wiki/Remote_procedure_call) (RPC) pattern,
|
||||
messaging systems primarily use an asynchronous message passing pattern
|
||||
with no tight relationship between requests and responses. Most
|
||||
messaging systems also support a request-response mode but this is not a
|
||||
|
|
@ -43,7 +43,7 @@ flexible, loosely coupled systems.
|
|||
Often, large enterprises use a messaging system to implement a message
|
||||
bus which loosely couples heterogeneous systems together. Message buses
|
||||
often form the core of an [Enterprise Service
|
||||
Bus](http://en.wikipedia.org/wiki/Enterprise_service_bus). (ESB). Using
|
||||
Bus](https://en.wikipedia.org/wiki/Enterprise_service_bus). (ESB). Using
|
||||
a message bus to de-couple disparate systems can allow the system to
|
||||
grow and adapt more easily. It also allows more flexibility to add new
|
||||
systems or retire old ones since they don't have brittle dependencies on
|
||||
|
|
@ -52,9 +52,9 @@ each other.
|
|||
## Messaging styles
|
||||
|
||||
Messaging systems normally support two main styles of asynchronous
|
||||
messaging: [message queue](http://en.wikipedia.org/wiki/Message_queue)
|
||||
messaging: [message queue](https://en.wikipedia.org/wiki/Message_queue)
|
||||
messaging (also known as *point-to-point messaging*) and [publish
|
||||
subscribe](http://en.wikipedia.org/wiki/Publish_subscribe) messaging.
|
||||
subscribe](https://en.wikipedia.org/wiki/Publish_subscribe) messaging.
|
||||
We'll summarise them briefly here:
|
||||
|
||||
### The Message Queue Pattern
|
||||
|
|
@ -95,7 +95,7 @@ database with the order details. Once it's done that it acknowledges the
|
|||
message to tell the server that the order has been processed and can be
|
||||
forgotten about. Often the send to the warehouse system, update in
|
||||
database and acknowledgement will be completed in a single transaction
|
||||
to ensure [ACID](http://en.wikipedia.org/wiki/ACID) properties.
|
||||
to ensure [ACID](https://en.wikipedia.org/wiki/ACID) properties.
|
||||
|
||||
### The Publish-Subscribe Pattern
|
||||
|
||||
|
|
@ -169,7 +169,7 @@ Let's take a brief look at these:
|
|||
|
||||
### Java Message Service (JMS)
|
||||
|
||||
[JMS](http://en.wikipedia.org/wiki/Java_Message_Service) is part of
|
||||
[JMS](https://en.wikipedia.org/wiki/Java_Message_Service) is part of
|
||||
Oracle's Java EE specification. It's a Java API that encapsulates both message
|
||||
queue and publish-subscribe messaging patterns. JMS is a lowest common
|
||||
denominator specification - i.e. it was created to encapsulate common
|
||||
|
|
@ -200,7 +200,7 @@ the JMS API.
|
|||
|
||||
### RESTful API
|
||||
|
||||
[REST](http://en.wikipedia.org/wiki/Representational_State_Transfer)
|
||||
[REST](https://en.wikipedia.org/wiki/Representational_State_Transfer)
|
||||
approaches to messaging are showing a lot interest recently.
|
||||
|
||||
It seems plausible that API standards for cloud computing may converge
|
||||
|
|
@ -220,7 +220,7 @@ Please see [Rest Interface](rest.md) for using Apache ActiveMQ Artemis's RESTful
|
|||
|
||||
### AMQP
|
||||
|
||||
[AMQP](http://en.wikipedia.org/wiki/AMQP) is a specification for
|
||||
[AMQP](https://en.wikipedia.org/wiki/AMQP) is a specification for
|
||||
interoperable messaging. It also defines a wire format, so any AMQP
|
||||
client can work with any messaging system that supports AMQP. AMQP
|
||||
clients are available in many different programming languages.
|
||||
|
|
@ -231,14 +231,14 @@ specification. Any client that supports the 1.0 specification will be
|
|||
able to interact with Apache ActiveMQ Artemis.
|
||||
|
||||
### MQTT
|
||||
[MQTT](http://mqtt.org/) is a lightweight connectivity protocol. It is designed
|
||||
[MQTT](https://mqtt.org/) is a lightweight connectivity protocol. It is designed
|
||||
to run in environments where device and networks are constrained. Out of the box
|
||||
Apache ActiveMQ Artemis supports version MQTT 3.1.1. Any client supporting this
|
||||
version of the protocol will work against Apache ActiveMQ Artemis.
|
||||
|
||||
### STOMP
|
||||
|
||||
[Stomp](http://stomp.github.io/) is a very simple text protocol for
|
||||
[Stomp](https://stomp.github.io/) is a very simple text protocol for
|
||||
interoperating with messaging systems. It defines a wire format, so
|
||||
theoretically any Stomp client can work with any messaging system that
|
||||
supports Stomp. Stomp clients are available in many different
|
||||
|
|
|
|||
|
|
@ -45,7 +45,7 @@ The majority of the journal is written in Java, however we abstract out
|
|||
the interaction with the actual file system to allow different pluggable
|
||||
implementations. Apache ActiveMQ Artemis ships with two implementations:
|
||||
|
||||
- Java [NIO](http://en.wikipedia.org/wiki/New_I/O).
|
||||
- Java [NIO](https://en.wikipedia.org/wiki/New_I/O).
|
||||
|
||||
The first implementation uses standard Java NIO to interface with
|
||||
the file system. This provides extremely good performance and runs
|
||||
|
|
@ -77,7 +77,7 @@ implementations. Apache ActiveMQ Artemis ships with two implementations:
|
|||
|
||||
- [Memory mapped](https://en.wikipedia.org/wiki/Memory-mapped_file).
|
||||
|
||||
The third implementation uses a file-backed [READ_WRITE](https://docs.oracle.com/javase/6/docs/api/java/nio/channels/FileChannel.MapMode.html#READ_WRITE)
|
||||
The third implementation uses a file-backed [READ_WRITE](https://docs.oracle.com/javase/8/docs/api/java/nio/channels/FileChannel.MapMode.html#READ_WRITE)
|
||||
memory mapping against the OS page cache to interface with the file system.
|
||||
|
||||
This provides extremely good performance (especially under strictly process failure durability requirements),
|
||||
|
|
@ -85,8 +85,8 @@ implementations. Apache ActiveMQ Artemis ships with two implementations:
|
|||
on any platform where there's a Java 4+ runtime.
|
||||
|
||||
Under power failure durability requirements it will perform at least on par with the NIO journal with the only
|
||||
exception of Linux OS with kernel less or equals 2.6, in which the [*msync*](https://docs.oracle.com/javase/6/docs/api/java/nio/MappedByteBuffer.html#force%28%29)) implementation necessary to ensure
|
||||
durable writes was different (and slower) from the [*fsync*](https://docs.oracle.com/javase/6/docs/api/java/nio/channels/FileChannel.html#force%28boolean%29) used is case of NIO journal.
|
||||
exception of Linux OS with kernel less or equals 2.6, in which the [*msync*](https://docs.oracle.com/javase/8/docs/api/java/nio/MappedByteBuffer.html#force%28%29)) implementation necessary to ensure
|
||||
durable writes was different (and slower) from the [*fsync*](https://docs.oracle.com/javase/8/docs/api/java/nio/channels/FileChannel.html#force%28boolean%29) used is case of NIO journal.
|
||||
|
||||
It benefits by the configuration of OS [huge pages](https://en.wikipedia.org/wiki/Page_%28computer_memory%29),
|
||||
in particular when is used a big number of journal files and sizing them as multiple of the OS page size in bytes.
|
||||
|
|
|
|||
|
|
@ -221,7 +221,7 @@ also active by default on the generic acceptor defined on port 61616 (where all
|
|||
of the box configuration.
|
||||
|
||||
The best source of information on the MQTT protocol is in the specification. The MQTT v3.1.1 specification can
|
||||
be downloaded from the OASIS website here: http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html
|
||||
be downloaded from the OASIS website here: https://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html
|
||||
|
||||
Some note worthy features of MQTT are explained below:
|
||||
|
||||
|
|
@ -305,7 +305,7 @@ There are 2 types of wild card in MQTT:
|
|||
|
||||
## Stomp
|
||||
|
||||
[Stomp](http://stomp.github.com/) is a text-orientated wire protocol
|
||||
[Stomp](https://stomp.github.io/) is a text-orientated wire protocol
|
||||
that allows Stomp clients to communicate with Stomp Brokers. Apache ActiveMQ Artemis
|
||||
now supports Stomp 1.0, 1.1 and 1.2.
|
||||
|
||||
|
|
@ -570,7 +570,7 @@ sending it to stomp clients. The default value of
|
|||
### Stomp Over Web Sockets
|
||||
|
||||
Apache ActiveMQ Artemis also support Stomp over [Web
|
||||
Sockets](http://dev.w3.org/html5/websockets/). Modern web browser which
|
||||
Sockets](https://html.spec.whatwg.org/multipage/web-sockets.html). Modern web browser which
|
||||
support Web Sockets can send and receive Stomp messages from Apache ActiveMQ Artemis.
|
||||
|
||||
Stomp over Web Sockets is supported via the normal Stomp acceptor:
|
||||
|
|
@ -583,7 +583,7 @@ then connect to `ws://<server>:61614` using a Web Socket to send
|
|||
and receive Stomp messages.
|
||||
|
||||
A companion JavaScript library to ease client-side development is
|
||||
available from [GitHub](http://github.com/jmesnil/stomp-websocket)
|
||||
available from [GitHub](https://github.com/jmesnil/stomp-websocket)
|
||||
(please see its [documentation](http://jmesnil.net/stomp-websocket/doc/)
|
||||
for a complete description).
|
||||
|
||||
|
|
|
|||
|
|
@ -233,7 +233,7 @@ Let's give an explanation of each config option.
|
|||
- `use-link-headers`. By default, all links (URLs) are published using
|
||||
custom headers. You can instead have the Apache ActiveMQ Artemis REST
|
||||
implementation publish links using the [Link Header
|
||||
specification](http://tools.ietf.org/html/draft-nottingham-http-link-header-10)
|
||||
specification](https://tools.ietf.org/html/draft-nottingham-http-link-header-10)
|
||||
instead if you desire.
|
||||
|
||||
- `default-durable-send`. Whether a posted message should be persisted
|
||||
|
|
|
|||
|
|
@ -289,7 +289,7 @@ In short, the file defines:
|
|||
- the implementation class for the login module (e.g. `org.apache.activemq.artemis.spi.core.security.jaas.PropertiesLoginModule`)
|
||||
|
||||
- a flag which indicates whether the success of the login module is `required`, `requisite`, `sufficient`, or `optional`
|
||||
(see more details on these flags in the [JavaDoc](http://docs.oracle.com/javase/8/docs/api/javax/security/auth/login/Configuration.html)
|
||||
(see more details on these flags in the [JavaDoc](https://docs.oracle.com/javase/8/docs/api/javax/security/auth/login/Configuration.html)
|
||||
|
||||
- a list of configuration options specific to the login module implementation
|
||||
|
||||
|
|
@ -486,7 +486,7 @@ managed using the X.500 system. It is implemented by `org.apache.activemq.artemi
|
|||
|
||||
After substitution, the string is interpreted as an LDAP search filter, where the LDAP search filter syntax is
|
||||
defined by the IETF standard, RFC 2254. A short introduction to the search filter syntax is available from Oracle's
|
||||
JNDI tutorial, [Search Filters](http://download.oracle.com/javase/jndi/tutorial/basics/directory/filter.html).
|
||||
JNDI tutorial, [Search Filters](https://docs.oracle.com/javase/jndi/tutorial/basics/directory/filter.html).
|
||||
|
||||
For example, if this option is set to `(uid={0})` and the received username is `jdoe`, the search filter becomes
|
||||
`(uid=jdoe)` after string substitution. If the resulting search filter is applied to the subtree selected by the
|
||||
|
|
@ -728,7 +728,7 @@ that the Kerberos Peer Principal does not exist as an Apache ActiveMQ Artemis us
|
|||
|
||||
#### TLS Kerberos Cipher Suites
|
||||
|
||||
The legacy [rfc2712](http://www.ietf.org/rfc/rfc2712.txt) defines TLS Kerberos cipher suites that can be used by TLS to negotiate
|
||||
The legacy [rfc2712](https://www.ietf.org/rfc/rfc2712.txt) defines TLS Kerberos cipher suites that can be used by TLS to negotiate
|
||||
Kerberos authentication. The cypher suites offered by rfc2712 are dated and insecure and rfc2712 has been superseded by
|
||||
SASL GSSAPI. However, for clients that don't support SASL (core client), using TLS can provide Kerberos authentication
|
||||
over an *unsecure* channel.
|
||||
|
|
|
|||
|
|
@ -60,7 +60,7 @@ lead to dead-lock situations if the upper bound is chosen to be too low.
|
|||
The default value for `thread-pool-max-size` is `30`.
|
||||
|
||||
See the [J2SE
|
||||
javadoc](http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/ThreadPoolExecutor.htm)
|
||||
javadoc](https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ThreadPoolExecutor.html)
|
||||
for more information on unbounded (cached), and bounded (fixed) thread
|
||||
pools.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ You can use *any* AMQP 1.0 compatible clients.
|
|||
|
||||
A short list includes:
|
||||
|
||||
- qpid clients at the [qpid project](http://qpid.apache.org/download.html)
|
||||
- qpid clients at the [qpid project](https://qpid.apache.org/download.html)
|
||||
- [.NET Clients](https://blogs.apache.org/activemq/entry/using-net-libraries-with-activemq)
|
||||
- [Javascript NodeJS](https://github.com/noodlefrenzy/node-amqp10)
|
||||
- [Java Script RHEA](https://github.com/grs/rhea)
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ be more comfortable using JMS.
|
|||
|
||||
JMS is a very popular API standard for messaging, and most messaging
|
||||
systems provide a JMS API. If you are completely new to JMS we suggest
|
||||
you follow the [Oracle JMS tutorial](http://docs.oracle.com/javaee/7/tutorial/partmessaging.htm) -
|
||||
you follow the [Oracle JMS tutorial](https://docs.oracle.com/javaee/7/tutorial/partmessaging.htm) -
|
||||
a full JMS tutorial is out of scope for this guide.
|
||||
|
||||
Apache ActiveMQ Artemis also ships with a wide range of examples, many of which
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
Apache ActiveMQ Artemis uses a specific syntax for representing wildcards in security
|
||||
settings, address settings and when creating consumers.
|
||||
|
||||
The syntax is similar to that used by [AMQP](http://www.amqp.org).
|
||||
The syntax is similar to that used by [AMQP](https://www.amqp.org).
|
||||
|
||||
An Apache ActiveMQ Artemis wildcard expression contains words delimited by the character
|
||||
'`.`' (full stop).
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
To run the example, simply type **mvn verify** from this directory, or **mvn -PnoServer verify** if you want to start and create the broker manually.
|
||||
|
||||
This example shows you how to use a JMS [QueueBrowser](http://java.sun.com/javaee/5/docs/api/javax/jms/QueueBrowser.html) with ActiveMQ Artemis.
|
||||
This example shows you how to use a JMS [QueueBrowser](https://docs.oracle.com/javaee/7/api/javax/jms/QueueBrowser.html) with ActiveMQ Artemis.
|
||||
|
||||
Queues are a standard part of JMS, please consult the JMS 1.1 specification for full details.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
To run the example, simply type **mvn verify** from this directory, or **mvn -PnoServer verify** if you want to start and create the broker manually.
|
||||
|
||||
This example shows how to kick off a client connected to ActiveMQ using [JMX](http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/)
|
||||
This example shows how to kick off a client connected to ActiveMQ using [JMX](http://www.oracle.com/technetwork/java/javase/tech/javamanagement-140525.html)
|
||||
|
||||
The example will connect to ActiveMQ Artemis. Using JMX, we will list the remote addresses connected to the broker and close the corresponding connections. The client will be kicked off from ActiveMQ Artemis receiving an exception that its JMS connection was interrupted.
|
||||
|
||||
|
|
@ -17,6 +17,6 @@ To access this MBeanServer remotely, the Java Virtual machine must be started wi
|
|||
-Dcom.sun.management.jmxremote.ssl=false
|
||||
-Dcom.sun.management.jmxremote.authenticate=false
|
||||
|
||||
These properties are explained in the Java [management guide](http://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdenl) (please note that for this example, we will disable user authentication for simplicity).
|
||||
These properties are explained in the Java [management guide](https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdenl) (please note that for this example, we will disable user authentication for simplicity).
|
||||
|
||||
With these properties, ActiveMQ Artemis broker will be manageable remotely using standard JMX URL on port `3000`.
|
||||
|
|
@ -6,7 +6,7 @@ To run the example, simply type:
|
|||
|
||||
from this directory, or add **-PnoServer** if you want to start and create the broker manually.
|
||||
|
||||
This example shows how to manage ActiveMQ Artemis using [JMX using SSL](http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/)
|
||||
This example shows how to manage ActiveMQ Artemis using [JMX using SSL](http://www.oracle.com/technetwork/java/javase/tech/javamanagement-140525.html)
|
||||
|
||||
## Example configuration
|
||||
|
||||
|
|
@ -20,4 +20,4 @@ With these properties, ActiveMQ Artemis broker will be manageable remotely using
|
|||
|
||||
## More information
|
||||
|
||||
* [Java management guide](http://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html)
|
||||
* [Java management guide](https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html)
|
||||
|
|
@ -2,8 +2,8 @@
|
|||
|
||||
To run the example, simply type **mvn verify** from this directory, or **mvn -PnoServer verify** if you want to start and create the broker manually.
|
||||
|
||||
This example shows how to manage ActiveMQ Artemis using [JMX](http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/)
|
||||
This example shows how to manage ActiveMQ Artemis using [JMX](http://www.oracle.com/technetwork/java/javase/tech/javamanagement-140525.html)
|
||||
|
||||
## More information
|
||||
|
||||
* [Java management guide](http://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html)
|
||||
* [Java management guide](https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html)
|
||||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
To run the example, simply type **mvn verify** from this directory, or **mvn -PnoServer verify** if you want to start and create the broker manually.
|
||||
|
||||
This example shows you how to use a [QueueRequestor](http://java.sun.com/javaee/5/docs/api/javax/jms/QueueRequestor.html) with ActiveMQ Artemis.
|
||||
This example shows you how to use a [QueueRequestor](https://docs.oracle.com/javaee/7/api/javax/jms/QueueRequestor.html) with ActiveMQ Artemis.
|
||||
|
||||
JMS is mainly used to send messages asynchronously so that the producer of a message is not waiting for the result of the message consumption. However, there are cases where it is necessary to have a synchronous behavior: the code sending a message requires a reply for this message before continuing its execution.
|
||||
A QueueRequestor facilitates this use case by providing a simple request/reply abstraction on top of JMS.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ my-broker/bin/artemis run
|
|||
```
|
||||
##Download and Install JMeter's latest release:
|
||||
|
||||
http://jmeter.apache.org/download_jmeter.cgi
|
||||
https://jmeter.apache.org/download_jmeter.cgi
|
||||
|
||||
##Copy artemis-jms-client dependencies under $JMETER_HOME/lib folder:
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ For more information on configuring protocol transports see the "Configuring Tra
|
|||
|
||||
## MQTT Clients
|
||||
|
||||
There are a number of MQTT client implementations for various languages. The Paho project: http://www.eclipse.org/paho/ offers a number of clients for languages such as C, Python, JavaScript and .Net and is also a great resource for all things MQTT. This example is actually based on the Fuse MQTT java client and was chosen as it is Apache 2.0 licensed and available to download from maven central. The specific client used in the example is not of importance and is used simply to demonstrate the features of MQTT as provided by Apache Artemis.
|
||||
There are a number of MQTT client implementations for various languages. The Paho project: https://www.eclipse.org/paho/ offers a number of clients for languages such as C, Python, JavaScript and .Net and is also a great resource for all things MQTT. This example is actually based on the Fuse MQTT java client and was chosen as it is Apache 2.0 licensed and available to download from maven central. The specific client used in the example is not of importance and is used simply to demonstrate the features of MQTT as provided by Apache Artemis.
|
||||
|
||||
If you'd like to use the client demonstrated in this example, simple add the following dependency to your pom.xml
|
||||
|
||||
|
|
|
|||
|
|
@ -541,7 +541,7 @@ public class CoreClientOverOneWaySSLTest extends ActiveMQTestBase {
|
|||
* to look through the cipher suites until we find one that's suitable for us.
|
||||
* If the JVM running this test is version 7 from Oracle then this cipher suite will will almost certainly require
|
||||
* TLSv1.2 (which is not enabled on the client by default).
|
||||
* See http://docs.oracle.com/javase/7/docs/technotes/guides/security/SunProviders.html#SunJSSEProvider for the
|
||||
* See http://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html#SunJSSEProvider for the
|
||||
* preferred cipher suites.
|
||||
*/
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue