We have just started troubshooting Confluence periodically being unresponsive. Most of the time we restart the service and things are good for a few days. Today a tech ran Netstat before we restarted and found this http://sdrv.ms/1bmVlkG Our local copy of Confluene seems to be trying to connect to Atlassian and about 10 of those connection have a status of CLOSE_WAIT.
Questions:
1. Is it normal for a download copy of Confluence to be trying to connect to Atlassian?
2. Could these connections be causing Confluence to be unresponsive?
3. Should we consider changing the windows timeout for such "Close_Wait" connections?
We´re also have these CLOSE_WAIT´s to pillar03, and we´re monitoring our Confluence Server, and it could be very annoying to have such messages during the night.
because of an apache in front of out confluence we also receive CLOSE_WAIT´s from apache2 service and the java service
netstat -anp| grep CLOSE_WAIT |awk '{print $NF}' | sort | uniq -c
12 19582/java
9 19647/apache2
8 19648/apache2
7 19947/apache2
is it possible to reduce this without changing our monitoring template which will be used for many other servers/services.
Hello there,
Pillar03 is our mirror, which after some seconds it gets redirect to atlassian.com. It could be stuck there, because it can't move forward as the next atlassian's website.
I don't believe that Confluence being unresponsive would be due that Confluence is trying to reach out the outside world.
cheers,
wz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.