How to delete this WARNING

[Jack Tauson]

I have a spring boot app which is deployed on tomcat on RHEL server which is trying to connect to ActiveMQ and it keeps on throwing following error in tomcat logs. The main reasons I have noticed why this happened was because either ActiveMQ isn't running or listening over another port.

The main issue is how to get rid of this warning from tomcat? How can I kill this? Because of this warning, it won't let other deployed apps on the tomcat to run properly. So I had to ask my server team to reeboot the server to get rid of this warning. This option isn't feasible for me everytime I run into this issue.  Another weird thing I have noticed is that, whenever the following error occured, I deleted the application from tomcat webapps directory which was trying to connect to tcp://localhost:61616 and the tomcat live logs were still showing same error. So even though the application didn't exists in tomcat, this WARNING was still going on and preventing other apps from deploying.

My application.properties of springboot app has following configuration:

 

 spring.activemq.broker-url=failover://tcp://localhost:61616
    spring.activemq.user=admin
    spring.activemq.password=admin
    jms.queue.destination=MyQueueName

   

2020-06-11 12:07:56.269  WARN 18092 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 180 attempt(s) continuing to retry.
    2020-06-11 12:08:40.206  WARN 9914 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 90 attempt(s) continuing to retry.
    2020-06-11 12:12:20.441  WARN 15290 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 200 attempt(s) continuing to retry.
    2020-06-11 12:13:06.317  WARN 18092 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 190 attempt(s) continuing to retry.
    2020-06-11 12:13:50.257  WARN 9914 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 100 attempt(s) continuing to retry.
    2020-06-11 12:17:30.538  WARN 15290 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 210 attempt(s) continuing to retry.
    2020-06-11 12:18:16.362  WARN 18092 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 200 attempt(s) continuing to retry.
    2020-06-11 12:19:00.323  WARN 9914 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 110 attempt(s) continuing to retry.
    2020-06-11 12:22:40.584  WARN 15290 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 220 attempt(s) continuing to retry.
    2020-06-11 12:23:26.414  WARN 18092 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 210 attempt(s) continuing to retry.
    2020-06-11 12:24:10.371  WARN 9914 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 120 attempt(s) continuing to retry.
    2020-06-11 12:27:50.626  WARN 15290 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 230 attempt(s) continuing to retry.
    2020-06-11 12:28:36.462  WARN 18092 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 220 attempt(s) continuing to retry.
    2020-06-11 12:29:20.428  WARN 9914 --- [ActiveMQ Task-2] o.a.a.t.failover.FailoverTransport       : Failed to connect to [tcp://localhost:61616] after: 130 attempt(s) continuing to retry.

[Himai Minh]

I think you want want to disable console logging. Here is an example https://www.baeldung.com/spring-boot-disable-console-logging

[Jack Tauson]

Himai Minh wrote:I think you want want to disable console logging. Here is an example https://www.baeldung.com/spring-boot-disable-console-logging

Thanks. But I think that would disable 100 % of console logging. I was wondering about killing this WARNING specific to ActiveMQ. Because if such a thing happens I would like to see the logs that something failed and at the same time I need to have a way to kill this. Is it possible?

[Paul Clapham]

You can either hide those messages or you can fix whatever it is that causes the messages to appear. It may be that you can fine-tune the logging configuration to exclude those specific messages, but I don't know how to do that.

However you said

Because of this warning, it won't let other deployed apps on the tomcat to run properly.

So it doesn't sound like hiding the warning is what you want to do. Instead you want to fix the underlying problem.

But it seems to me that you already had a long thread about not being able to connect to ActiveMQ. Looks like that problem never did get solved. Maybe you should reply to that thread and carry on there.

[Tim Holloway]

Yeah. It's pretty plain that your app cannot connect to port 61616 on the local machine. While this could indicate a firewall problem, usually localhost has free connection abilities, so the #1 reason why you'd get this would be if there was no ActiveMQ server running and listening to the localhost port 61616.

Three possible reasons for this:

1. ActiveMQ is not running on the local machine
2. ActiveMQ is not configured to listen at address 127.0.0.1 (localhost). Many servers understand that a machine may have multiple network interfaces and can be configured to only listen to certain ones.
3. Whatever is listening on port 61616 isn't hearing the connection protocol it wishes to accept. A web equivalent would be if you made an HTTP request to an HTTPS connection port - stuff that would normally go to port 80 but you're sending it to port 443.

And, while the log seems to indicate total failure to connect, even if some connections were getting through, that many messages would indicate a very inefficient operation that needs fixing.

[Himai Minh]

Hi, you may find this stackoverflow thread helpful :https://stackoverflow.com/questions/30030086/activemq-unable-to-connect-to-a-public-queue
Do you need to add this property queueTCP = tcp://localhost:61616