Skip to content

[ENHANCEMENT] Remove benign verbose logs upon shutdown#2356

Merged
Arsnael merged 2 commits into
apache:masterfrom
chibenwa:rabbit-silent-shutdown
Jul 22, 2024
Merged

[ENHANCEMENT] Remove benign verbose logs upon shutdown#2356
Arsnael merged 2 commits into
apache:masterfrom
chibenwa:rabbit-silent-shutdown

Conversation

@chibenwa
Copy link
Copy Markdown
Contributor

reactor.core.Exceptions$ErrorCallbackNotImplemented: com.rabbitmq.client.ShutdownSignalException: clean connection shutdown; protocol method: #method<connection.close>(reply-code=200, reply-text=OK, class-id=0, method-id=0)
Caused by: com.rabbitmq.client.ShutdownSignalException: clean connection shutdown; protocol method: #method<connection.close>(reply-code=200, reply-text=OK, class-id=0, method-id=0)
	at com.rabbitmq.utility.ValueOrException.getValue(ValueOrException.java:66)
	Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException: 
Assembly trace from producer [reactor.core.publisher.MonoRunnable] :
	reactor.core.publisher.Mono.fromRunnable(Mono.java:702)
	org.apache.james.backends.rabbitmq.ReactorRabbitMQChannelPool.lambda$new$2(ReactorRabbitMQChannelPool.java:694)
Error has been observed at the following site(s):
	*__Mono.fromRunnable ⇢ at org.apache.james.backends.rabbitmq.ReactorRabbitMQChannelPool.lambda$new$2(ReactorRabbitMQChannelPool.java:694)
	|_         Mono.then ⇢ at org.apache.james.backends.rabbitmq.ReactorRabbitMQChannelPool.lambda$new$2(ReactorRabbitMQChannelPool.java:699)
	|_  Mono.subscribeOn ⇢ at org.apache.james.backends.rabbitmq.ReactorRabbitMQChannelPool.lambda$new$2(ReactorRabbitMQChannelPool.java:700)
	|_    Mono.doFinally ⇢ at reactor.pool.AbstractPool.destroyPoolable(AbstractPool.java:181)
	*___________Mono.and ⇢ at reactor.pool.SimpleDequePool.lambda$disposeLater$2(SimpleDequePool.java:208)
	*_________Mono.defer ⇢ at reactor.pool.SimpleDequePool.disposeLater(SimpleDequePool.java:179)
Original Stack Trace:
		at com.rabbitmq.utility.ValueOrException.getValue(ValueOrException.java:66)
		at com.rabbitmq.utility.BlockingValueOrException.uninterruptibleGetValue(BlockingValueOrException.java:36)
		at com.rabbitmq.client.impl.AMQChannel$BlockingRpcContinuation.getReply(AMQChannel.java:552)
		at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:635)
		at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:557)
		at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:550)
		at com.rabbitmq.client.impl.recovery.AutorecoveringChannel.lambda$close$0(AutorecoveringChannel.java:74)
		at com.rabbitmq.client.impl.recovery.AutorecoveringChannel.executeAndClean(AutorecoveringChannel.java:102)
		at com.rabbitmq.client.impl.recovery.AutorecoveringChannel.close(AutorecoveringChannel.java:74)
		at org.apache.james.backends.rabbitmq.ReactorRabbitMQChannelPool$SelectOnceChannel.close(ReactorRabbitMQChannelPool.java:109)
		at org.apache.james.backends.rabbitmq.ReactorRabbitMQChannelPool.lambda$new$1(ReactorRabbitMQChannelPool.java:696)
		at com.github.fge.lambdas.runnable.RunnableChainer.doRun(RunnableChainer.java:18)
		at com.github.fge.lambdas.runnable.ThrowingRunnable.run(ThrowingRunnable.java:16)
		at reactor.core.publisher.MonoRunnable.subscribe(MonoRunnable.java:49)
		at reactor.core.publisher.Mono.subscribe(Mono.java:4568)
		at reactor.core.publisher.MonoSubscribeOn$SubscribeOnSubscriber.run(MonoSubscribeOn.java:126)
		at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:84)
		at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:37)
		at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
		at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
		at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
		at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
		at java.base/java.lang.Thread.run(Unknown Source)

@chibenwa chibenwa self-assigned this Jul 18, 2024
@Arsnael Arsnael merged commit 2674b2d into apache:master Jul 22, 2024
samiulsami pushed a commit to opnpulse/james-project that referenced this pull request Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants