Migrate JIRA 6.3.1 from Windows 2003 to Windows 2012

[Jason Stapley]

Hello Atlassian Community!

I am attempting a test migration of JIRA 6.3.1 from Windows 2003 to Windows 2012

The Windows 2003 installation was installed on the C drive the Windows 2012 server will be on a E drive I have reconfigured the following files to take into account the fact Jira is on the E drive and pointing to another SQL server

E:\Program Files\Atlassian\Application Data\JIRA\dbconfig.xml

E:\Program Files\Atlassian\JIRA\atlassian-jira\WEB-INF\classes\jira-application.properties

E:\Program Files (x86)\Atlassian\JIRA\bin\setenv.bat

CATALINA_HOME=E:\Program Files\Atlassian\JIRA

Using 64bit Java 7.0

Enable 64bit tcnative

Rename  E:\Program Files\Atlassian\JIRA\bin\apr\tcnative-1.dll to E:\Program Files\Atlassian\JIRA\bin\apr\tcnative-1.dll.x32

 rename E:\Program Files\Atlassian\JIRA\bin\apr\tcnative-1.dll.x64 to E:\Program Files\Atlassian\JIRA\bin\apr\tcnative-1.dll

Enable 64bit Tomcat

Rename E:\Program Files\Atlassian\JIRA\bin\tomcat7.exe to E:\Program Files\Atlassian\JIRA\bin\tomcat7.exe.x32

Rename E:\Program Files\Atlassian\JIRA\bin\tomcat7.exe.x64 to E:\Program Files\Atlassian\JIRA\bin\tomcat7.exe

Check for lock file

E:\Program Files\Atlassian\Application Data\JIRA

E:\Program Files\Atlassian\JIRA\bin\service install

Ensure Jira is using the correct JRE by checking the output of service install

E:\Program Files\Atlassian\JIRA\bin>service install

Installing the service 'JIRA020512152402' ...

Using CATALINA_HOME:    "E:\Program Files\Atlassian\JIRA"

Using CATALINA_BASE:    "E:\Program Files\Atlassian\JIRA"

Ignoring JAVA_HOME:        ""

Using JRE_HOME:         "C:\Program Files\Java\jdk1.7.0_80\jre"

Using JVM:              "C:\Program Files\Java\jdk1.7.0_80\jre\bin\server\jvm.dl

Set memory allocation in setenv.bat The server have 8gb

E:\Program Files (x86)\Atlassian\JIRA\bin\setenv.bat

Set memory allocation to

set JVM_MINIMUM_MEMORY=512m

set JVM_MAXIMUM_MEMORY=1024m

set JVM_REQUIRED_ARGS=-Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -XX:MaxPermSize=2048M -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled

This is error exception we are getting in E:\Program Files\Atlassian\Application Data\JIRA\log\ 

It looks like its running out of memory even tho it has more memory than the original server. 

Could this have something to do with 32bit to 64bit migration?

Any ideas?

2018-02-15 17:03:30,813 localhost-startStop-1 INFO [atlassian.jira.startup.JiraStartupLogger]

****************
JIRA starting...
****************

2018-02-15 17:03:30,985 localhost-startStop-1 INFO [atlassian.jira.startup.JiraStartupLogger]

___ Environment _____________________________

JIRA Build : 6.3.1#6329-sha1:7df76f1f758b4c5e4d2f2d8aa6679c1ae74a2e4e
Build Date : Tue Jul 15 00:00:00 BST 2014
JIRA Installation Type : Standalone
Application Server : Apache Tomcat/7.0.47 - Servlet API 3.0
Java Version : 1.7.0_80 - Oracle Corporation
Current Working Directory : E:\Program Files\Atlassian\JIRA\bin
Maximum Allowable Memory : 683MB
Total Memory : 372MB
Free Memory : 235MB
Used Memory : 137MB
Memory Pool: Code Cache : Code Cache: init = 2555904(2496K) used = 2300416(2246K) committed = 2555904(2496K) max = 50331648(49152K)
Memory Pool: PS Eden Space : PS Eden Space: init = 67633152(66048K) used = 26044224(25433K) committed = 131596288(128512K) max = 141557760(138240K)
Memory Pool: PS Survivor Space : PS Survivor Space: init = 11010048(10752K) used = 11802856(11526K) committed = 63438848(61952K) max = 63438848(61952K)
Memory Pool: PS Old Gen : PS Old Gen: init = 179306496(175104K) used = 106062072(103576K) committed = 195559424(190976K) max = 536870912(524288K)
Memory Pool: PS Perm Gen : PS Perm Gen: init = 22020096(21504K) used = 18308944(17879K) committed = 26214400(25600K) max = 85983232(83968K)
JVM Input Arguments : -Dcatalina.base=E:\Program Files\Atlassian\JIRA -Dcatalina.home=E:\Program Files\Atlassian\JIRA -Djava.endorsed.dirs=E:\Program Files\Atlassian\JIRA\endorsed -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -Djava.io.tmpdir=E:\Program Files\Atlassian\JIRA\temp -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=E:\Program Files\Atlassian\JIRA\conf\logging.properties exit -Xms256m -Xmx768m
Java Compatibility Information : JIRA version = 6.3.1, Java Version = 1.7.0_80

___ Java System Properties ________________

atlassian.standalone : JIRA
awt.toolkit : sun.awt.windows.WToolkit
catalina.base : E:\Program Files\Atlassian\JIRA
catalina.home : E:\Program Files\Atlassian\JIRA
catalina.useNaming : true
common.loader : ${catalina.base}/lib,
${catalina.base}/lib/*.jar,
${catalina.home}/lib,
${catalina.home}/lib/*.jar
file.encoding : Cp1252
file.encoding.pkg : sun.io
java.awt.graphicsenv : sun.awt.Win32GraphicsEnvironment
java.awt.headless : true
java.awt.printerjob : sun.awt.windows.WPrinterJob
java.class.version : 51.0
java.home : C:\Program Files\Java\jdk1.7.0_80\jre
java.io.tmpdir : E:\Program Files\Atlassian\JIRA\temp
java.naming.factory.initial : org.apache.naming.java.javaURLContextFactory
java.naming.factory.url.pkgs : org.apache.naming
java.runtime.name : Java(TM) SE Runtime Environment
java.runtime.version : 1.7.0_80-b15
java.specification.name : Java Platform API Specification
java.specification.vendor : Oracle Corporation
java.specification.version : 1.7
java.util.logging.config.file : E:\Program Files\Atlassian\JIRA\conf\logging.properties
java.util.logging.manager : org.apache.juli.ClassLoaderLogManager
java.vendor : Oracle Corporation
java.vendor.url : http://java.oracle.com/
java.vendor.url.bug : http://bugreport.sun.com/bugreport/
java.version : 1.7.0_80
java.vm.info : mixed mode
java.vm.name : Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name : Java Virtual Machine Specification
java.vm.specification.vendor : Oracle Corporation
java.vm.specification.version : 1.7
java.vm.vendor : Oracle Corporation
java.vm.version : 24.80-b11
mail.mime.decodeparameters : true
org.apache.catalina.startup.ContextConfig.jarsToSkip :
org.apache.catalina.startup.TldConfig.jarsToSkip : tomcat7-websocket.jar
org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER : true
org.dom4j.factory : com.atlassian.core.xml.InterningDocumentFactory
os.arch : amd64
os.name : Windows Server 2012
os.version : 6.2
package.access : sun.,
org.apache.catalina.,
org.apache.coyote.,
org.apache.tomcat.,
org.apache.jasper.
package.definition : sun.,
java.,
org.apache.catalina.,
org.apache.coyote.,
org.apache.tomcat.,
org.apache.jasper.
server.loader :
shared.loader :
sun.arch.data.model : 64
sun.boot.library.path : C:\Program Files\Java\jdk1.7.0_80\jre\bin
sun.cpu.endian : little
sun.cpu.isalist : amd64
sun.desktop : windows
sun.io.unicode.encoding : UnicodeLittle
sun.jnu.encoding : Cp1252
sun.management.compiler : HotSpot 64-Bit Tiered Compilers
sun.os.patch.level :
tomcat.util.buf.StringCache.byte.enabled : true
tomcat.util.scan.DefaultJarScanner.jarsToSkip : bootstrap.jar,
commons-daemon.jar,
tomcat-juli.jar,
annotations-api.jar,
el-api.jar,
jsp-api.jar,
servlet-api.jar,
websocket-api.jar,
catalina.jar,
catalina-ant.jar,
catalina-ha.jar,
catalina-tribes.jar,
jasper.jar,
jasper-el.jar,
ecj-*.jar,
tomcat-api.jar,
tomcat-util.jar,
tomcat-coyote.jar,
tomcat-dbcp.jar,
tomcat-jni.jar,
tomcat-spdy.jar,
tomcat-i18n-en.jar,
tomcat-i18n-es.jar,
tomcat-i18n-fr.jar,
tomcat-i18n-ja.jar,
tomcat-juli-adapters.jar,
catalina-jmx-remote.jar,
catalina-ws.jar,
tomcat-jdbc.jar,
tools.jar,
commons-beanutils*.jar,
commons-codec*.jar,
commons-collections*.jar,
commons-dbcp*.jar,
commons-digester*.jar,
commons-fileupload*.jar,
commons-httpclient*.jar,
commons-io*.jar,
commons-lang*.jar,
commons-logging*.jar,
commons-math*.jar,
commons-pool*.jar,
jstl.jar,
geronimo-spec-jaxrpc*.jar,
wsdl4j*.jar,
ant.jar,
ant-junit*.jar,
aspectj*.jar,
jmx.jar,
h2*.jar,
hibernate*.jar,
httpclient*.jar,
jmx-tools.jar,
jta*.jar,
log4j.jar,
log4j-1*.jar,
mail*.jar,
slf4j*.jar,
xercesImpl.jar,
xmlParserAPIs.jar,
xml-apis.jar,
junit.jar,
junit-*.jar,
hamcrest*.jar,
org.hamcrest*.jar,
ant-launcher.jar
user.country : US
user.dir : E:\Program Files\Atlassian\JIRA\bin
user.home : C:\
user.language : en
user.name : DPG-LVM-JIRA02$
user.script :
user.timezone : Europe/London
user.variant :

2018-02-15 17:03:31,204 localhost-startStop-1 INFO [atlassian.jira.startup.JiraHomeStartupCheck] The jira.home directory 'E:\Program Files\Atlassian\Application Data\JIRA' is validated and locked for exclusive use by this instance.
2018-02-15 17:03:31,220 localhost-startStop-1 INFO [jira.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from E:\Program Files\Atlassian\Application Data\JIRA\dbconfig.xml
2018-02-15 17:03:31,345 localhost-startStop-1 INFO [atlassian.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2018-02-15 17:03:31,345 localhost-startStop-1 INFO [atlassian.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully.
2018-02-15 17:03:32,001 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Product Name is Microsoft SQL Server
2018-02-15 17:03:32,001 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Product Version is 14.00.1000
2018-02-15 17:03:32,001 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Driver Name is jTDS Type 4 JDBC Driver for MS SQL Server and Sybase
2018-02-15 17:03:32,001 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Driver Version is 1.3.1
2018-02-15 17:03:32,501 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Product Name is Microsoft SQL Server
2018-02-15 17:03:32,501 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Product Version is 14.00.1000

[plugin.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin com.atlassian.applinks.applinks-plugin
java.lang.OutOfMemoryError: PermGen space

[Timothy]

Some quick observations.

Ensure Jira is using the correct JRE by checking the output of service install

I believe that if you are running  Jira as a service, settings in setenv.bat does not take into effect. You will need to edit the service itself and modify the values there. The settings can either be in the service itself or in the registry.

• https://confluence.atlassian.com/adminjiraserver070/increasing-jira-application-memory-749383419.html#IncreasingJIRAapplicationmemory-Windowsservice

[Jason Stapley]

Many thanks that worked a treat :)