Installing Jira to a new mssql instance

[Scott Langlois]

I am installing a complete new copy of Jira due to MS licensing we need it to be on one of our production databases.  We have created a second instance on the database for Jira to use.   The Config wizard does not allow for the specification of and Instance even the the JDBC driver allows for it and you can edit the config afterwards to point to it.  I tried editing the config with the extra options I need but it will not connect has anyone made this work?  If you have please enlighten me on what I am doing wrong.

[Andy Heinzer]

Hi Scott,

Thanks for all this info.  It certainly looks like the Microsoft official database driver is recommending the use of the explicit port number for optimum performance.  But I understand that you don't always have control over those other systems to be able to make that kind of change.

So I was thinking we might have another way to approach this.  So Jira started bundling that official MS database driver in Jira 7.5 and higher version.  But before that we actually bundled the opensource JTDS driver with Jira.   I would be interested to see if perhaps you can use that database driver instead of the official one to try to connect Jira to this database in this case.   It might not be officially supported by Atlassian, but I have a strong inclination to believe this could work for you.  Try these steps.

1. Make sure Jira is stopped
2. Download the opensource jTDS driver from sourceforge: https://sourceforge.net/projects/jtds/files/ The version we bundled last was the 1.3.1 IIRC
3. Go into the $JIRAINSTALL/lib/ folder
4. Remove the mssql-jdbc-x.x.x.x.jar file (you can move it to a temp directory outside that install folder)
5. Copy in the downloaded jtds .jar file to this directory
6. You will also need to edit the dbconfig.xml again, because the jtds driver has a slightly different syntax than the official one does both for driver-class and url elements in xml.  I would expect your file to look like this:
   

   <jira-database-config>
   <name>defaultDS</name>
   <delegator-name>default</delegator-name>
   <database-type>mssql</database-type>
   <schema-name>jiraschema</schema-name>
   <jdbc-datasource>
     <url>jdbc:jtds:sqlserver://<YOUR_SERVER_FQDN>/<YOUR_DB_NAME>;instance=<YOUR_INSTANCE_NAME></url>
     <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
     <username>jiradbuser</username>
     <password>password</password>
     <pool-min-size>20</pool-min-size>
     <pool-max-size>20</pool-max-size>
     <pool-max-wait>30000</pool-max-wait>
     <pool-max-idle>20</pool-max-idle>
     <pool-remove-abandoned>true</pool-remove-abandoned>
     <pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>
    
     <validation-query>select 1</validation-query>
     <min-evictable-idle-time-millis>60000</min-evictable-idle-time-millis>
     <time-between-eviction-runs-millis>300000</time-between-eviction-runs-millis>
    
     <pool-test-while-idle>true</pool-test-while-idle>
   </jdbc-datasource>
   </jira-database-config>

7. Save that file.
8. Start Jira.

I think this could work.  Please let me know the results.

Andy

[Andy Heinzer]

Hi Scott,

Could you let us know what version of Jira you're using here? And what version of MS SQL server you are trying to connect to here?

I ask because starting with Jira 7.5 and higher, Atlassian switch what jdbc database driver we bundle for connecting to MS SQL servers, and in doing so the syntax used to connect to these databases is slight different between the old jtds driver and the newer official Microsoft driver.

In addition to that, I'd be interested to take a look at your $JIRAHOME/dbconfig.xml file.  Often times the problem is in the details of the syntax here.  Of course please obscure your password in this file before posting it here.

Cheers,

Andy

[Scott Langlois]

Hi Andrew,

This is a brand new install, the intent is to do an export of our current instance of Jira which is running on mysql and move to an instance on our enterprise instance of mssql.  As it is ground up install then migrate there is not much to any of it at the moment.  I tried using the instructions for setting up the sql server but it just does not like connecting to the instance.

using the IP of the server to connect  192.168.2.20

the instance is called ToolsDB1

the database is called Jira

it uses the default port for sql server. 

At this point I can reinstall the latest version of jira and rerun the configuration as we have been unable to get this instance connected.

Thanks,

Scott

[Andy Heinzer]

Scott,

There are a couple different way to try to approach this. 

1) Try editing the dbconfig.xml manually and see if this helps

<jira-database-config>
<name>defaultDS</name>
<delegator-name>default</delegator-name>
<database-type>mssql</database-type>
<schema-name>jiraschema</schema-name>
<jdbc-datasource>
<url>jdbc:sqlserver://192.168.2.20=ToolsDB1;portNumber=1433;databaseName=Jira</url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
<username>jiradbuser</username>
<password>password</password>
<pool-min-size>20</pool-min-size>
<pool-max-size>20</pool-max-size>
<pool-max-wait>30000</pool-max-wait>
<pool-max-idle>20</pool-max-idle>
<pool-remove-abandoned>true</pool-remove-abandoned>
<pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>

<validation-query>select 1</validation-query>
<min-evictable-idle-time-millis>60000</min-evictable-idle-time-millis>
<time-between-eviction-runs-millis>300000</time-between-eviction-runs-millis>

<pool-test-while-idle>true</pool-test-while-idle>
<pool-test-on-borrow>false</pool-test-on-borrow>
</jdbc-datasource>
</jira-database-config>

Save that file and restart Jira.  If the database is empty I'd expect Jira to still run the initial setup wizard where you get to create the admin accounts and so on.

If that doesn't work, I'd be interested to see what happens in the $JIRAINSTALL/logs/catalina.out file when Jira tries to start.  It tends to give us detailed errors that might explain the problem in more detail here.

2) An alternative approach would be to trying to use the JIRA Configuration tool to set this configuration up.

This utility has a 'test connection' feature you can try out before Jira tries to start up and use your settings to see if your settings can successfully connect to your database.

[Scott Langlois]

Sorry it took a bit to get back to you, 

The solution above did not work.

Going into the configuration tool I was able to set the instance by entering in 

192.168.2.20\ToolsDB1 

but I had to leave the port empty as this is what Microsoft says to do for the JDBC driver.

 https://docs.microsoft.com/en-us/sql/connect/jdbc/building-the-connection-url?view=sql-server-2017

Specifically in the purple box it says if you enter the port it will ignore the named instance.

Using this logic and hitting the test button I was able to get successfully connected to the database instance.  But now Jira will not start.  

Oh and the setup wizard requires the port so it will never work.  port should be optional as well based on the Microsoft Doc above.

[Andy Heinzer]

Hi Scott,

Thanks for posting that link.  In this case, I think the way I would prefer to resolve this would be to set a defined port for that specific instance from the SQL side.  Since the Microsoft documentation explains:

For optimal connection performance, you should set the portNumber when you connect to a named instance.

Doing it this way can really help us to make sure there are not constant lookups that need to happen everytime Jira has to connect to that database.  This is something you can do via the SQL Server Configuration Manager.  Details on how you can configure this are in Configure a Server to Listen on a Specific TCP Port.

However perhaps there is some reason you cannot do this.  In which case, I'd be interested to see what the $JIRAINSTALL/logs/catalina.out file looks like when Jira attempts to start up configured without a port number defined, but with the instance name in the jdbc url string.  Perhaps the entries in the log there can help us to better understand this limitation.

[Scott Langlois]

28-May-2019 10:49:31.908 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.35
28-May-2019 10:49:31.908 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Nov 3 2018 17:39:20 UTC
28-May-2019 10:49:31.908 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.35.0
28-May-2019 10:49:31.908 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows Server 2016
28-May-2019 10:49:31.908 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 10.0
28-May-2019 10:49:31.908 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
28-May-2019 10:49:31.908 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: C:\Program Files\Atlassian\JIRA\jre
28-May-2019 10:49:31.908 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_181-b13
28-May-2019 10:49:31.908 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
28-May-2019 10:49:31.908 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:\Program Files\Atlassian\JIRA
28-May-2019 10:49:31.908 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:\Program Files\Atlassian\JIRA
28-May-2019 10:49:31.908 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
28-May-2019 10:49:31.908 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.standalone=JIRA
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.decodeparameters=true
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-OmitStackTraceInFastThrow
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDetails
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDateStamps
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCTimeStamps
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCCause
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseGCLogFileRotation
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:NumberOfGCLogFiles=5
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:GCLogFileSize=20M
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xloggc:C:\Program Files\Atlassian\JIRA\logs\atlassian-jira-gc-%t.log
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:InitialCodeCacheSize=32m
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:ReservedCodeCacheSize=512m
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\Program Files\Atlassian\JIRA
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\Program Files\Atlassian\JIRA
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=C:\Program Files\Atlassian\JIRA\endorsed
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\Program Files\Atlassian\JIRA\temp
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\Program Files\Atlassian\JIRA\conf\logging.properties
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: exit
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: abort
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms384m
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx2048m
28-May-2019 10:49:31.923 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [C:\Program Files\Atlassian\JIRA\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\WindowsApps;.]
28-May-2019 10:49:32.095 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-80"]
28-May-2019 10:49:32.111 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 681 ms
28-May-2019 10:49:32.126 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
28-May-2019 10:49:32.126 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.35
28-May-2019 10:49:40.080 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-80"]
28-May-2019 10:49:40.095 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
28-May-2019 10:49:40.111 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 7995 ms
28-May-2019 10:49:46.542 WARNING [main] org.apache.catalina.core.StandardServer.await StandardServer.await: Invalid command '' received
28-May-2019 11:26:17.529 INFO [Thread-75] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-80"]
28-May-2019 11:26:17.547 INFO [Thread-75] org.apache.catalina.core.StandardService.stopInternal Stopping service [Catalina]
28-May-2019 11:26:36.589 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] registered the JDBC driver [org.h2.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
28-May-2019 11:26:36.589 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [JonasBatch] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:502)
org.objectweb.jonas_timer.TimerManager.batch(TimerManager.java:193)
org.objectweb.jonas_timer.Batch.run(TimerManager.java:65)
28-May-2019 11:26:36.589 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [JonasClock] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.lang.Thread.sleep(Native Method)
org.objectweb.jonas_timer.TimerManager.clock(TimerManager.java:142)
org.objectweb.jonas_timer.Clock.run(TimerManager.java:46)
28-May-2019 11:26:36.589 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.605 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@56584803]) and a value of type [com.atlassian.jira.tenancy.JiraTenantImpl] (value [JiraTenantImpl{id='fakeTenantId'}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
28-May-2019 11:26:36.620 INFO [Thread-75] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-80"]

[Scott Langlois]

Good Afternoon,

You are correct do to location of server and firewall rules only port 1433 is allowed on the inbound transactions.  I agree it would make my life easier if I could force the issue but it has not worked out that way so far, though I am still trying.  Above is the catalina file.