Hello together,
i am following the official guide on setting up a reverse proxy with apache2 for tomcat.
when I try to add the following two connectors (in /conf/server.xml):
<!-- Apache Proxy Connector with values for scheme, proxyName and proxyPort --><Connector acceptCount="100" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="8080" protocol="HTTP/1.1" redirectPort="8443" useBodyEncodingForURI="true" scheme="https" proxyName="jira.myserver.net" proxyPort="443"/>
<!-- Standard HTTP Connector -->
<Connector acceptCount="100" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="8081" protocol="HTTP/1.1" redirectPort="8443" useBodyEncodingForURI="true"/>
I get an OutOfMemory Error in Java. I also tried already, to size up the JVM_MINIMUM_MEMORY and the JVM_MAXIMUM_MEMORY from min 512m up to max 8192m , but it did not work out (in /bin/setenv.sh).
If I use the default http connector in the server.xml, jira starts up and works.
My aim is to use https://jira.myserver.net:8080 to redirect it to https://jira.myserver.net:80. I already have a configured apache2 server, which uses signed SSL certs.
I hope you guys can help me out soon.
Kind regards,
Waldemar
Hi Waldemar,
Is this for a Jira 4.x.x version? The current guides I think you are referring to are custom tailored to much more recent versions of Jira. If you are using a version 4 of Jira, it's possible the steps to do this different for this much older version of Jira.
But in regards to your outofmemory errors, I would be interested to learn more about how you start Jira. The setenv.sh should be the correct place to set this, provided this is a linux/unix system. For Windows environments there can be a different way to set this if the system is starting with a windows service. These are explained in https://confluence.atlassian.com/adminjiraserver/setting-properties-and-options-on-startup-938847831.html
Could you share with us the exact values you have in the JVM_SUPPORT_RECOMMENDED_ARGS= section? I have found that sometimes having extra whitespaces in this section can cause unexpected behavior.
Also to confirm this is set correctly, it would help to take a look at the $JIRAINSTALL/logs/catalina.out. This file is created by the tomcat process as it attempts to start Jira. It also should have a section called JIRA Starting which you can then look to see if your JVM arguments are actually being picked up from your setting file correctly or not.
Please let me know.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.