# Closing connections idle longer than 30000 MILLISECONDS

**URL:** <https://community.sonatype.com/t/closing-connections-idle-longer-than-30000-milliseconds/4722>\
**Category:** Sonatype Nexus Repository\
**Created:** [August 6, 2020, 9:21am UTC](https://community.sonatype.com/t/closing-connections-idle-longer-than-30000-milliseconds/4722 "2020-08-06T09:21:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![antonio.fernandes](https://avatars.discourse-cdn.com/v4/letter/a/d78d45/32.png) [@antonio.fernandes](https://community.sonatype.com/u/antonio.fernandes)\
**Post date:** [August 6, 2020, 9:21am UTC](https://community.sonatype.com/t/closing-connections-idle-longer-than-30000-milliseconds/4722/1 "2020-08-06T09:21:28Z")

</div>

Hello,

We have a Sonatype Nexus Repository Manager OSS 3.23.0-03 installed and every 5 seconds the following messages are written on the nexus.log

We already put the log level on DEBUG Level but we can find any justification for this message:

2020-08-06 10:13:43,371+0100 DEBUG [nexus-httpclient-eviction-thread] \*SYSTEM org.sonatype.nexus.internal.httpclient.SharedHttpClientConnectionManager - Closing expired connections  
2020-08-06 10:13:43,371+0100 DEBUG [nexus-httpclient-eviction-thread] \*SYSTEM org.sonatype.nexus.internal.httpclient.SharedHttpClientConnectionManager - Closing connections idle longer than 30000 MILLISECONDS

On the admin console appears a message saying: “Server disconnected: There is a problem communicating with the server”.

Anybody had a similar issue, can give any clue of what might cause this issue, or where these timeouts are defined?

Best regards,  
Ant

---

<div class="post-metadata">

**Author:** ![mpiggott](https://avatars.discourse-cdn.com/v4/letter/m/f0a364/32.png) [@mpiggott](https://community.sonatype.com/u/mpiggott)\
**Post date:** [August 7, 2020, 2:54pm UTC](https://community.sonatype.com/t/closing-connections-idle-longer-than-30000-milliseconds/4722/2 "2020-08-07T14:54:59Z")

</div>

Likely a proxy or reverse proxy is interferring with the connection. There are some example configurations in the help documentation - [https://help.sonatype.com/repomanager3/installation/run-behind-a-reverse-proxy](https://help.sonatype.com/repomanager3/installation/run-behind-a-reverse-proxy)