Apache configuration issue "ERR

[Laurent Bierge]

Hi,

I've managed to get an apache configuration that suit me, but i still have a big issue that disturb me.

Here's my apache configuration:

I have 4 virtualHost like this. 2 for jira and 2 for confluence.

Jira can be contacted through port 443 et 8443 et same for confluence. With this configuration, when jira is KO, i can reach confluence and have a maintenance page for jira and vice versa.

What bother me is that when i restart jira. Jira slow down at the lasts step at "init add-ons".

When jira is in this transient state i have a wierd issue on both Jira and Confluence. When i tried to go to "DomainName.com" i got "ERR_Connection_Reset" :

I don't get why i have this error while joining both jira and confluence (at most, i should be unable to reach jira but i shouldn't have problem to reach confluence). It must come from my apache but i don't know where to look.

Any idea ?

Regards,

Laurent

[Daniel Eads]

Hi Laurent,

I applaud your thoroughness in trying to get a solid reverse proxy configuration. Because you shouldn't (hopefully!) be restarting the applications often during business hours, most users won't be running in to this.

Since there's no explicitly defined timeout for the ProxyPass directive, Apache should be defaulting to 60 seconds. Depending on the hardware and how many plugins you've got on Confluence/Jira, it's possible they take longer to start up than this. nginx would throw a timeout error if that happened - I'm less intimately familiar with Apache but would hope it is verbose enough to throw a timeout error.

Is it possible to get the output of your Apache logs when Jira/Confluence are starting up and you see this error in the browser?

Thanks,
Daniel

[Laurent Bierge]

Hi Daniel,

Thank you for your answer !

Well the only logs that are a bit significative are in ssl_access.log.

The period during 14:26:18 and 14:26:58 seems to be to period with "ERR_CONNECTION RESET". (well, actually i made this post because when i restarted Jira on my prod environment, this issue lasted more than 15 minutes, i'm also researching why it was that long)

Laurent