You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Jo De Troy <jo...@gmail.com> on 2022/05/31 11:32:41 UTC
artemis client killed
Hello,
I'm running ActiveMQ using the operator on Openshift.
I have a broker running in 1 namespace and an 'activemq-client' pod with
the artemis cli runing in another namespace. When I try to connect from the
activemq-client to the broker the client quickly comes back with a 'killed'
message. When I do the same from the broker pod I do get a connection. Has
anyone experienced the same? Any idea what might be causing this and how I
could try to investigate this issue?
In the logs I'm seeing
2022-05-30 15:41:18,829 WARN [org.apache.activemq.artemis.core.server]
AMQ222107: Cleared up resources for session
f2343dd7-e02e-11ec-a6b9-0a580a820dd7 2022-05-30 15:41:18,829 WARN
[org.apache.activemq.artemis.core.server] AMQ222061: Client connection
failed, clearing up resources for session
f2631608-e02e-11ec-a6b9-0a580a820dd7 2022-05-30 15:41:18,829 WARN
[org.apache.activemq.artemis.core.server] AMQ222107: Cleared up resources
for session f2631608-e02e-11ec-a6b9-0a580a820dd7 2022-05-30 15:41:40,128
WARN [org.apache.activemq.artemis.core.server] AMQ222061: Client connection
failed, clearing up resources for session
ff2561e9-e02e-11ec-a6b9-0a580a820dd7
Best Regards,
Jo
Re: artemis client killed
Posted by Justin Bertram <jb...@apache.org>.
Typically one would see these WARN messages (i.e. AMQ222107 & AMQ222061)
when a client connected and then exited the application without properly
closing the connection. The broker monitors client connections to see if
they are still active and closes dead connections so they don't build up
and consume resources. You can read more about this in the documentation
[1].
However, as far as I'm aware the CLI tools shipped with ActiveMQ Artemis
clean up all their resources properly so either the commands are being
killed before they have a chance to clean up their resources or perhaps
there's something in your environment that's killing the connection for
some reason.
Justin
[1]
https://activemq.apache.org/components/artemis/documentation/latest/connection-ttl.html
On Tue, May 31, 2022 at 6:33 AM Jo De Troy <jo...@gmail.com> wrote:
> Hello,
>
> I'm running ActiveMQ using the operator on Openshift.
> I have a broker running in 1 namespace and an 'activemq-client' pod with
> the artemis cli runing in another namespace. When I try to connect from the
> activemq-client to the broker the client quickly comes back with a 'killed'
> message. When I do the same from the broker pod I do get a connection. Has
> anyone experienced the same? Any idea what might be causing this and how I
> could try to investigate this issue?
> In the logs I'm seeing
> 2022-05-30 15:41:18,829 WARN [org.apache.activemq.artemis.core.server]
> AMQ222107: Cleared up resources for session
> f2343dd7-e02e-11ec-a6b9-0a580a820dd7 2022-05-30 15:41:18,829 WARN
> [org.apache.activemq.artemis.core.server] AMQ222061: Client connection
> failed, clearing up resources for session
> f2631608-e02e-11ec-a6b9-0a580a820dd7 2022-05-30 15:41:18,829 WARN
> [org.apache.activemq.artemis.core.server] AMQ222107: Cleared up resources
> for session f2631608-e02e-11ec-a6b9-0a580a820dd7 2022-05-30 15:41:40,128
> WARN [org.apache.activemq.artemis.core.server] AMQ222061: Client connection
> failed, clearing up resources for session
> ff2561e9-e02e-11ec-a6b9-0a580a820dd7
> Best Regards,
> Jo
>