> Also, have you confirmed that Artemis is actually listening on the port
you're trying to use?
The log he pasted indicates that the broker is indeed listening on 61616:
INFO [org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL
Acceptor at 0.0.0.0:61616 for protocols
One way to test if it's a firewall issue is to try to open a raw TCP socket
to the port and see if you can establish a TCP connection and pass data. It
doesn't need to be compliant with the higher-level protocols (HTTP, STOMP),
it just needs to confirm that bytes are successfully passed. If bytes
Given that the broker is up and running fine on the remote machine I would
say there's some kind of environmental or network issue preventing
communication from your local machine and the remote machine on port 61616.
Perhaps a firewall is blocking that port.
Justin
On Fri, Aug 7, 2020 at 4:18
Log looks good to me:
2020-08-07 15:22:40,666 INFO
[org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting
ActiveMQ Artemis Server
2020-08-07 15:22:40,713 INFO [org.apache.activemq.artemis.core.server]
AMQ221000: live Message Broker is starting with configuration Broker
Did you check artemis.log to ensure the broker actually started up without
errors?
Also, did you run the "artemis producer" command on the remote machine to
make sure the broker is actually working?
Justin
On Fri, Aug 7, 2020 at 2:33 PM Christopher Pisz
wrote:
> From Remote Machine:
> cd
>From Remote Machine:
cd /var/lib
sudo su
/opt/apache-artemis-2.14.0/bin/artemis create testbroker
Creating ActiveMQ Artemis instance at: /var/lib/testbroker
--user: is a mandatory property!
Please provide the default username:
user
--password: is mandatory with this configuration:
Please
Given that you have an instance of ActiveMQ Artemis on the same machine as
the STOMP client I recommend you do something like this:
> cd /bin
> ./artemis producer --url tcp://remote-machine:61616 --user yourUser
--password yourPassword
Let me know if that works.
Justin
On Fri, Aug 7, 2020
I just followed the instructions on
https://activemq.apache.org/components/artemis/documentation/2.0.0/using-server.html
The broker is the default. Nothing is edited.
"
cd /var/lib
${ARTEMIS_HOME}/bin/artemis create mybroker
/var/lib/mybroker/bin/artemis run
On Fri, Aug 7, 2020 at 2:45 PM
On 8/7/20 2:40 PM, Christopher Pisz wrote:
What I need:
To determine if I can connect to activemq using stomp over websockets from
a remote machine, with a client I wrote.
What I did:
I wrote my own stomp over websockets client in C++ and built it for
CentOS7, on my home computer.
I installed
What I need:
To determine if I can connect to activemq using stomp over websockets from
a remote machine, with a client I wrote.
What I did:
I wrote my own stomp over websockets client in C++ and built it for
CentOS7, on my home computer.
I installed an ActiveMQ on a remote machine through ssh.
I
You're not really explaining what you need.
You say you need "a built client that connects with a different protocol."
What exactly do you mean by "built"? Does it have to be a binary? If so,
what platform does the binary need to be built for? If it doesn't have to
be a binary would a python or
On 8/7/20 2:08 PM, Christopher Pisz wrote:
Yes, I did a Google search.
It yields code examples or javascript libs. I need a built client that
connects with a different protocol, so I can quickly test that the server
will allow clients to connect at all.
You can try the ActiveMQ JMS client
Yes, I did a Google search.
It yields code examples or javascript libs. I need a built client that
connects with a different protocol, so I can quickly test that the server
will allow clients to connect at all.
On Fri, Aug 7, 2020 at 2:05 PM Justin Bertram wrote:
> There are lots of STOMP
There are lots of STOMP clients for various platforms written in various
programming languages many of which do not use websockets. What exactly do
you need? Did you try doing an Internet search?
Justin
On Fri, Aug 7, 2020 at 1:00 PM Christopher Pisz
wrote:
> So I installed ActiveMQ on a
So I installed ActiveMQ on a remote machine this morning.
Created the default broker.
Attempted to connect with the client I wrote using websockets.
Connection is refused.
I then tried running the examples/protocols/stomp/stomp-websockets example
Attempted to connect with the client I write using
In general I would expect the consumers to receive messages and eventually
clear enough space for the producer to continue sending messages. Can you
provide steps to easily reproduce what you're seeing? The details you've
provided aren't really enough to comment on what the issue might be.
Hi,
I did a test in which I was producing messages without consuming them on an
artemis (with paging enabled) in order to anticipate what could happen in the
worst scenario with persistent messages.
When I reach the max-disk-usage of 45% on a dedicated disk, the producers are
blocked as
Thanks everyone. I think this is what I would need to convince the team to
really get out of this. I appreciate the time you put into this and guiding
me appropriately.
Thanks again.
On Fri, Aug 7, 2020 at 10:24 AM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> In terms of
Derp. I am a Linux noob.
I had to sudo su
On Fri, Aug 7, 2020, 10:29 Justin Bertram wrote:
> The first thing to note is that the documentation is versioned and released
> with the broker. You're using the documentation for Artemis 2.0.0 even
> though your binary is for 2.14.0. Since 2.14.0 is
The first thing to note is that the documentation is versioned and released
with the broker. You're using the documentation for Artemis 2.0.0 even
though your binary is for 2.14.0. Since 2.14.0 is the latest release you
can find its documentation here [1] which is always where you can find the
In terms of exporting I am not sure. I personally have never looked at
LevelDB. In terms of the error itself it seems like some of the files got
corrupt so not sure if it's possible to recover. If you want to export the
data you would probably need to write your own export tool to parse the
LevelDB support was removed in large part due to the absence of developers
willing to maintain the code and volunteers willing to provide support for
it on this mailing list. In the 5+ years I've been involved in this mailing
list, I don't recall ever seeing a LevelDB question answered (and I've
So, I got a machine from my higher ups at work that I can ssh into and try
to set up activemq.
I followed the instructions on
https://activemq.apache.org/components/artemis/documentation/2.0.0/using-server.html
by
entering:
>cd /var/lib
>~/apache-artemis-2.14.0/bin/artemis create testbroker
The
Hi there,
We are facing an issue like consumer presenting issues to send ACK and rolling
back transition, and then client is not receiving more messages, and queue
growing.
javax.jms.JMSException: COMMIT FAILED: Transaction marked rollback only
xaErrorCode:100
at
Any ideas? Or, is there a way to export these messages so that I can
recreate the broker data directory and import them?
On Fri, Aug 7, 2020 at 6:39 AM Ramesh Venkitaswaran
wrote:
> Understood, that LevelDB is deprecated, and we are trying to get this team
> to move to Artemis. However we still
Fair enough. :)
Thanks for following up, Robbie. A thorough job as always.
Justin
On Fri, Aug 7, 2020 at 4:17 AM Robbie Gemmell
wrote:
> JIRAs have still been getting updated with PR opening/comment/closing,
> just maybe not in entirely the same way as old. The PR comment syncing
> changed
Understood, that LevelDB is deprecated, and we are trying to get this team
to move to Artemis. However we still need this broker to run while the
migration is going on.
On Fri, Aug 7, 2020 at 5:48 AM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> LevelDB support has been
LevelDB support has been deprecated for many years now and is going to be
removed in the next version of ActiveMQ (5.17.0) so I would suggest trying
to migrate over to KahaDB.
On Fri, Aug 7, 2020 at 4:08 AM Ramesh Venkitaswaran
wrote:
> Hello
> We have a 3 node activemq 5.15 cluster with
JIRAs have still been getting updated with PR opening/comment/closing,
just maybe not in entirely the same way as old. The PR comment syncing
changed to being added as JIRA work-log items by default a long long
time ago, and remained that way unless you asked for them to instead
be commented
Hello
We have a 3 node activemq 5.15 cluster with zookeeper using Level DB. It's
a very old system. However last night we started to get these errors and
the broker did not come up. Any ideas on how to fix this would be
appreciated. I can provide further log messages as needed, if sufficient
30 matches
Mail list logo
