[ARTEMIS-3349] Documentation Task for Artemis Transports

• Type: Task
• Status: Resolved
• Priority: Minor
• Resolution: Cannot Reproduce
• Affects Version/s: 2.17.0
• Component/s: Broker, Configuration

Environment

Red Hat Enterprise Linux Server release 7.9

Linux<hostname>.10.0-1160.11.1.el7.x86_64 #1 SMP Mon Nov 30 13:05:31 EST 2020 x86_64 x86_64 x86_64 GNU/Linux

• Assignee: Unassigned
• Reporter: Tony Dunbar
• Created: 15/Jun/21 12:02
• Updated: 04/Jul/21 19:42
• Resolved: 04/Jul/21 19:42

Description

I am fairly new to Apache Artemis, and attempted the install to test a stomp client.  I am not sure if this is a initial configuration issue or a documentation issue.  I followed the install instructions, to the letter, from the Artemis documentation.  The initial configuration of the etc/broker.xml during the installation will fail if the netty dependency is not satisfied upon server startup.  I attempted the installation on a newly created VM.  The only way I could get the server to accept messages was to change the useEpoll setting in the etc/broker.xml from true to false.  This allows the initial installation to use the built in NIO transport.  After turning on DEBUG logging and a lot of research, I was eventually able to download and copy the dependent netty jars to the <artemis instance>/lib directory.  Then changed the useEpoll setting in the etc/broker.xml from false to true.  Restarted the artemis service and now the netty transport was being used successfully.  The dependent netty jars are:

netty-transport-4.x.Final.jar

netty-buffer-4.x.Final.jar

netty-common-4.x.Final.jar

netty-resolver-4.x.Final.jar  

In my humble opinion, your installation of Artemis assumes the host machine will already have Netty transport installed, perhaps from some other application install.  You should either package the netty dependencies in the <artemis instance>/lib directory or default the useEpoll settings to false.  

Thanks

Tony