[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364861#comment-17364861 ] Domenico Francesco Bruscino commented on ARTEMIS-3349: -- [~tdunbar] yes I would like to check the JVM log with the original state to get more details of the cause of this issue. Thanks > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > Attachments: artemisconfig.zip > > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364429#comment-17364429 ] Tony Dunbar commented on ARTEMIS-3349: -- Thanks Domenico...Sorry for the delay...I am tied up today, but will set this up and test at the end of today. I will respond with the results before tomorrow morning. BTW...I assume you want me to put the configuration back to its original state and test...useEpoll=true, no netty-* files in the instance lib dir, etc...? Tony On Wed, Jun 16, 2021 at 1:03 AM Domenico Francesco Bruscino (Jira) < -- Thanks, Tony > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > Attachments: artemisconfig.zip > > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364056#comment-17364056 ] Domenico Francesco Bruscino commented on ARTEMIS-3349: -- [~tdunbar] I agree with you and [~jbertram], this looks an environmental issue that is affecting the classloader. Can you share the JVM log from the console? * add `JAVA_ARGS="$JAVA_ARGS -verbose` to the `artemis.profile` file. * redirect the artemis console log to a file, ie `/var/lib/mqbroker01/bin/artemis run > verbose.log` > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > Attachments: artemisconfig.zip > > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363914#comment-17363914 ] Tony Dunbar commented on ARTEMIS-3349: -- Thanks Domenico, But the /var/lib/mqbroker01/lib was not created when the problem occurred and was only created to hold the private netty dependencies. I had no other files in the instance lib directory. Also, my user id has sudo privilages so I am able to act as root. I had performed the entire installation using my sudo privilages. Its as if your installed netty-all jar won't load from the installation lib directory. Like the classloader order has a problem when loading from the install lib. > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > Attachments: artemisconfig.zip > > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363903#comment-17363903 ] Domenico Francesco Bruscino commented on ARTEMIS-3349: -- [~tdunbar] if removing all files (not just netty jars) from `/var/lib/mqbroker01/lib/` folder and then copy the `netty-all-4.1.51.Final.jar` file from `/opt/apache-artemis-2.17.0/lib/` to `/var/lib/mqbroker01/lib/` worked it means your issue could be due to 2 possibilities: * in `/var/lib/mqbroker01/lib/` there was a jar not compatible with `netty-all-4.1.51.Final.jar` * the user you are using to execute artemis can't access `/opt/apache-artemis-2.17.0/lib/` > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > Attachments: artemisconfig.zip > > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363849#comment-17363849 ] Tony Dunbar commented on ARTEMIS-3349: -- Not sure if this is related, but my only other problem is the change to the variable in etc/artemis.profile for the ARTEMIS_DATA_DIR has no effect on where the messaging data is stored. I have specified an absolute path to a filesystem separate from the instance directory. Regardless, it is still storing the data under the instance/data directory. > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > Attachments: artemisconfig.zip > > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[
https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363818#comment-17363818
]
Justin Bertram commented on ARTEMIS-3349:
-
For what it's worth, the broker ships with _all_ the necessary runtime
dependencies, including Netty.
Also, the use of epoll is delegated to Netty and if epoll is not available when
{{useEpoll=true}} then there should just be a {{WARN}} in the log and the
broker should fallback safely to the normal NIO implementation. It should
accept messages in any case.
For good measure I read through the documentation you cited and followed it
myself from scratch and it worked fine although I did update it in a few places
to clarify some things.
The issue you're describing sounds _very_ strange and I surmise they are
environmental in nature (e.g. your softlink). I created a new instance of
2.17.0 from scratch and used your attached config (with a few changes to
{{artemis.profile}}) to start-up the broker and send and receive few messages
from a STOMP client. Everything worked fine.
> Documentation Task for Artemis Transports
> -
>
> Key: ARTEMIS-3349
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3349
> Project: ActiveMQ Artemis
> Issue Type: Task
> Components: Broker, Configuration
>Affects Versions: 2.17.0
> Environment: Red Hat Enterprise Linux Server release 7.9
> Linux.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
>Reporter: Tony Dunbar
>Priority: Minor
> Attachments: artemisconfig.zip
>
>
> 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 /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
> /lib directory or default the useEpoll settings to false.
> Thanks
> Tony
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363754#comment-17363754 ] Tony Dunbar commented on ARTEMIS-3349: -- Ok...that worked What does this mean? On Tue, Jun 15, 2021 at 11:17 AM Domenico Francesco Bruscino (Jira) < -- Thanks, Tony > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > Attachments: artemisconfig.zip > > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363704#comment-17363704 ] Domenico Francesco Bruscino commented on ARTEMIS-3349: -- [~tdunbar] can you try removing all files (not just netty jars) from `/var/lib/mqbroker01/lib/` folder and then copy the `netty-all-4.1.51.Final.jar` file from `/opt/apache-artemis-2.17.0/lib/` to `/var/lib/mqbroker01/lib/`? > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > Attachments: artemisconfig.zip > > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363656#comment-17363656 ] Tony Dunbar commented on ARTEMIS-3349: -- BTW...I have the env var $ARTEMIS_HOME set to /opt/artemis I have a softlink from artemis to /opt/apache-artemis-2.17.0/ Tony > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > Attachments: artemisconfig.zip > > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363653#comment-17363653 ] Tony Dunbar commented on ARTEMIS-3349: -- FYI...I did use the artemis command to create my broker. This was my exact command I executed from the /var/lib directory: [tdunbar var/lib] sudo /opt/artemis/artemis create mqbroker01 The contents of my etc directory is attached to this ticket. > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > Attachments: artemisconfig.zip > > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363641#comment-17363641 ] Tony Dunbar commented on ARTEMIS-3349: -- BTW...my specific version of the netty binaries I copied over was 4.1.66 Tony > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[
https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363639#comment-17363639
]
Domenico Francesco Bruscino commented on ARTEMIS-3349:
--
[~tdunbar] did you create your instance using the artemis tool, ie
`${ARTEMIS_HOME}/bin/artemis create mybroker`?
Can you share your etc folder?
> Documentation Task for Artemis Transports
> -
>
> Key: ARTEMIS-3349
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3349
> Project: ActiveMQ Artemis
> Issue Type: Task
> Components: Broker, Configuration
>Affects Versions: 2.17.0
> Environment: Red Hat Enterprise Linux Server release 7.9
> Linux.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
>Reporter: Tony Dunbar
>Priority: Minor
>
> 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 /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
> /lib directory or default the useEpoll settings to false.
> Thanks
> Tony
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363630#comment-17363630 ] Tony Dunbar commented on ARTEMIS-3349: -- So I see that netty-all is included in the /opt/artemis/lib directory. But for some reason my installation did not pickup that binary from the classpath. When I copied my netty binaries to the /lib directory, those got picked up by the instance. Something tells me something is missing from the installation steps. Tony On Tue, Jun 15, 2021 at 8:40 AM Robbie Gemmell (Jira) -- Thanks, Tony > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363627#comment-17363627 ] Tony Dunbar commented on ARTEMIS-3349: -- I used this document... https://activemq.apache.org/components/artemis/documentation/latest/using-server.html On Tue, Jun 15, 2021 at 8:40 AM Robbie Gemmell (Jira) -- Thanks, Tony > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3349) Documentation Task for Artemis Transports
[ https://issues.apache.org/jira/browse/ARTEMIS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363611#comment-17363611 ] Robbie Gemmell commented on ARTEMIS-3349: - It would help if you could point to which specific doc you followed to the letter, so someone could actually check it for issues. The broker uses Netty for the NIO transport as well, and the lib dir includes netty-all which bundles all of Netty including those modules you mentioned, so that shouldnt really have made a difference, making it doubly odd. > Documentation Task for Artemis Transports > - > > Key: ARTEMIS-3349 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3349 > Project: ActiveMQ Artemis > Issue Type: Task > Components: Broker, Configuration >Affects Versions: 2.17.0 > Environment: Red Hat Enterprise Linux Server release 7.9 > Linux.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 >Reporter: Tony Dunbar >Priority: Minor > > 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 /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 > /lib directory or default the useEpoll settings to false. > Thanks > Tony -- This message was sent by Atlassian Jira (v8.3.4#803005)
