You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Christopher Pisz <ch...@gmail.com> on 2022/02/18 19:05:56 UTC
Client drop messages in log
I've got ActiveMq instance with several clients connecting from a C++
application. I am using the STOMP protocol over Websockets. However, I am
not sure this is even related to the STOMP protocol or those clients,
because if I understand correctly, clients send a CONNECT frame and the
server responds with a CONNECTED frame, so the server would not be waiting
on anything from the client to complain about in the log.
I wonder how I can find out what client this is, where the 60,000 came
from, and what "data" the server is waiting to receive.
Here is what I am seeing in the log:
2022-02-18 13:20:19,426 WARN [org.apache.activemq.artemis.core.server]
AMQ222067: Connection failure has been detected: AMQ229014: Did not receive
data from /0:0:0:0:0:0:0:1%0:40816 within the 60,000ms connection TTL. The
connection will now be closed. [code=CONNECTION_TIMEDOUT]
2022-02-18 13:20:19,427 WARN [org.apache.activemq.artemis.core.server]
AMQ222061: Client connection failed, clearing up resources for session
49cd5085-90e7-11ec-81e3-0871906bcec5
2022-02-18 13:20:19,430 WARN [org.apache.activemq.artemis.core.server]
AMQ222107: Cleared up resources for session
49cd5085-90e7-11ec-81e3-0871906bcec5
2022-02-18 13:21:49,432 WARN
[org.apache.activemq.artemis.core.protocol.stomp] AMQ332069: Sent ERROR
frame to STOMP client /0:0:0:0:0:0:0:1%0:40822: AMQ229014: Did not receive
data from /0:0:0:0:0:0:0:1%0:40822 within the 60,000ms connection TTL. The
connection will now be closed.
Thanks,
Christopher Pisz
Re: Client drop messages in log
Posted by Christopher Pisz <ch...@gmail.com>.
That's what I needed. Thanks!
On Fri, Feb 18, 2022 at 3:51 PM Justin Bertram <jb...@apache.org> wrote:
> I don't have time to respond at length so I'll just share two relevant
> resources that should answer most (if not all) of your questions:
>
> -
>
> https://activemq.apache.org/components/artemis/documentation/latest/stomp.html#stomp-heart-beating-and-connection-ttl
> - https://stomp.github.io/stomp-specification-1.2.html#Heart-beating
>
>
> Justin
>
> On Fri, Feb 18, 2022 at 2:27 PM Christopher Pisz <
> christopherpisz@gmail.com>
> wrote:
>
> > I found
> >
> >
> https://activemq.apache.org/components/artemis/documentation/latest/connection-ttl.html
> >
> > and specifically this:
> > "The client will automatically send "ping" packets periodically to
> prevent
> > the server from closing it down."
> >
> > I assume by "client" they mean a java client supplied by a library. Of
> > course, I am left without a clue as to what to do when implementing my
> own
> > client in C++ to speak to ActiveMq over STOMP and Websockets. The doc
> > doesn't really go into detail about what this "ping" looks like, which
> > network layer it is on, or what form the response should take.
> >
> > Both the STOMP and Websocket protocols already have a heartbeat built in.
> > Perhaps there is a way for me to say "Don't use this at all!" from my
> > clients? Is it a header of some kind I would send on the CONNECT frame?
> >
> >
> >
> >
> >
> >
> > On Fri, Feb 18, 2022 at 2:05 PM Christopher Pisz <
> > christopherpisz@gmail.com>
> > wrote:
> >
> > > I've got ActiveMq instance with several clients connecting from a C++
> > > application. I am using the STOMP protocol over Websockets. However, I
> am
> > > not sure this is even related to the STOMP protocol or those clients,
> > > because if I understand correctly, clients send a CONNECT frame and the
> > > server responds with a CONNECTED frame, so the server would not be
> > waiting
> > > on anything from the client to complain about in the log.
> > >
> > > I wonder how I can find out what client this is, where the 60,000 came
> > > from, and what "data" the server is waiting to receive.
> > >
> > > Here is what I am seeing in the log:
> > > 2022-02-18 13:20:19,426 WARN [org.apache.activemq.artemis.core.server]
> > > AMQ222067: Connection failure has been detected: AMQ229014: Did not
> > receive
> > > data from /0:0:0:0:0:0:0:1%0:40816 within the 60,000ms connection TTL.
> > The
> > > connection will now be closed. [code=CONNECTION_TIMEDOUT]
> > > 2022-02-18 13:20:19,427 WARN [org.apache.activemq.artemis.core.server]
> > > AMQ222061: Client connection failed, clearing up resources for session
> > > 49cd5085-90e7-11ec-81e3-0871906bcec5
> > > 2022-02-18 13:20:19,430 WARN [org.apache.activemq.artemis.core.server]
> > > AMQ222107: Cleared up resources for session
> > > 49cd5085-90e7-11ec-81e3-0871906bcec5
> > > 2022-02-18 13:21:49,432 WARN
> > > [org.apache.activemq.artemis.core.protocol.stomp] AMQ332069: Sent
> ERROR
> > > frame to STOMP client /0:0:0:0:0:0:0:1%0:40822: AMQ229014: Did not
> > receive
> > > data from /0:0:0:0:0:0:0:1%0:40822 within the 60,000ms connection TTL.
> > The
> > > connection will now be closed.
> > >
> > > Thanks,
> > > Christopher Pisz
> > >
> >
>
Re: Client drop messages in log
Posted by Justin Bertram <jb...@apache.org>.
I don't have time to respond at length so I'll just share two relevant
resources that should answer most (if not all) of your questions:
-
https://activemq.apache.org/components/artemis/documentation/latest/stomp.html#stomp-heart-beating-and-connection-ttl
- https://stomp.github.io/stomp-specification-1.2.html#Heart-beating
Justin
On Fri, Feb 18, 2022 at 2:27 PM Christopher Pisz <ch...@gmail.com>
wrote:
> I found
>
> https://activemq.apache.org/components/artemis/documentation/latest/connection-ttl.html
>
> and specifically this:
> "The client will automatically send "ping" packets periodically to prevent
> the server from closing it down."
>
> I assume by "client" they mean a java client supplied by a library. Of
> course, I am left without a clue as to what to do when implementing my own
> client in C++ to speak to ActiveMq over STOMP and Websockets. The doc
> doesn't really go into detail about what this "ping" looks like, which
> network layer it is on, or what form the response should take.
>
> Both the STOMP and Websocket protocols already have a heartbeat built in.
> Perhaps there is a way for me to say "Don't use this at all!" from my
> clients? Is it a header of some kind I would send on the CONNECT frame?
>
>
>
>
>
>
> On Fri, Feb 18, 2022 at 2:05 PM Christopher Pisz <
> christopherpisz@gmail.com>
> wrote:
>
> > I've got ActiveMq instance with several clients connecting from a C++
> > application. I am using the STOMP protocol over Websockets. However, I am
> > not sure this is even related to the STOMP protocol or those clients,
> > because if I understand correctly, clients send a CONNECT frame and the
> > server responds with a CONNECTED frame, so the server would not be
> waiting
> > on anything from the client to complain about in the log.
> >
> > I wonder how I can find out what client this is, where the 60,000 came
> > from, and what "data" the server is waiting to receive.
> >
> > Here is what I am seeing in the log:
> > 2022-02-18 13:20:19,426 WARN [org.apache.activemq.artemis.core.server]
> > AMQ222067: Connection failure has been detected: AMQ229014: Did not
> receive
> > data from /0:0:0:0:0:0:0:1%0:40816 within the 60,000ms connection TTL.
> The
> > connection will now be closed. [code=CONNECTION_TIMEDOUT]
> > 2022-02-18 13:20:19,427 WARN [org.apache.activemq.artemis.core.server]
> > AMQ222061: Client connection failed, clearing up resources for session
> > 49cd5085-90e7-11ec-81e3-0871906bcec5
> > 2022-02-18 13:20:19,430 WARN [org.apache.activemq.artemis.core.server]
> > AMQ222107: Cleared up resources for session
> > 49cd5085-90e7-11ec-81e3-0871906bcec5
> > 2022-02-18 13:21:49,432 WARN
> > [org.apache.activemq.artemis.core.protocol.stomp] AMQ332069: Sent ERROR
> > frame to STOMP client /0:0:0:0:0:0:0:1%0:40822: AMQ229014: Did not
> receive
> > data from /0:0:0:0:0:0:0:1%0:40822 within the 60,000ms connection TTL.
> The
> > connection will now be closed.
> >
> > Thanks,
> > Christopher Pisz
> >
>
Re: Client drop messages in log
Posted by Christopher Pisz <ch...@gmail.com>.
I found
https://activemq.apache.org/components/artemis/documentation/latest/connection-ttl.html
and specifically this:
"The client will automatically send "ping" packets periodically to prevent
the server from closing it down."
I assume by "client" they mean a java client supplied by a library. Of
course, I am left without a clue as to what to do when implementing my own
client in C++ to speak to ActiveMq over STOMP and Websockets. The doc
doesn't really go into detail about what this "ping" looks like, which
network layer it is on, or what form the response should take.
Both the STOMP and Websocket protocols already have a heartbeat built in.
Perhaps there is a way for me to say "Don't use this at all!" from my
clients? Is it a header of some kind I would send on the CONNECT frame?
On Fri, Feb 18, 2022 at 2:05 PM Christopher Pisz <ch...@gmail.com>
wrote:
> I've got ActiveMq instance with several clients connecting from a C++
> application. I am using the STOMP protocol over Websockets. However, I am
> not sure this is even related to the STOMP protocol or those clients,
> because if I understand correctly, clients send a CONNECT frame and the
> server responds with a CONNECTED frame, so the server would not be waiting
> on anything from the client to complain about in the log.
>
> I wonder how I can find out what client this is, where the 60,000 came
> from, and what "data" the server is waiting to receive.
>
> Here is what I am seeing in the log:
> 2022-02-18 13:20:19,426 WARN [org.apache.activemq.artemis.core.server]
> AMQ222067: Connection failure has been detected: AMQ229014: Did not receive
> data from /0:0:0:0:0:0:0:1%0:40816 within the 60,000ms connection TTL. The
> connection will now be closed. [code=CONNECTION_TIMEDOUT]
> 2022-02-18 13:20:19,427 WARN [org.apache.activemq.artemis.core.server]
> AMQ222061: Client connection failed, clearing up resources for session
> 49cd5085-90e7-11ec-81e3-0871906bcec5
> 2022-02-18 13:20:19,430 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> 49cd5085-90e7-11ec-81e3-0871906bcec5
> 2022-02-18 13:21:49,432 WARN
> [org.apache.activemq.artemis.core.protocol.stomp] AMQ332069: Sent ERROR
> frame to STOMP client /0:0:0:0:0:0:0:1%0:40822: AMQ229014: Did not receive
> data from /0:0:0:0:0:0:0:1%0:40822 within the 60,000ms connection TTL. The
> connection will now be closed.
>
> Thanks,
> Christopher Pisz
>